Atlassian Forge

Catalog name forge. A remote MCP server carrying Atlassian’s own Forge documentation. No credential, no sign-in.

What it’s for

Forge is a platform with a strict manifest, a fixed set of extension points and a UI Kit of its own, and a model that has read a year-old tutorial will invent a module name that looks right and does not exist. This server is Atlassian’s own answer to that: the agent looks up the module list, reads the manifest rules before it edits manifest.yml, and asks about UI Kit components instead of approximating React.

It serves documentation only. There is no access to your site or your apps, which is why it needs no credential at all.

It pairs with the forge CLI from the Atlassian feature: this server explains what to build, the CLI deploys it.

Add it

At init, or to an existing workbench:

monoceros init acme --with-mcp-servers=forge

monoceros add-mcp-server acme forge

Then apply:

monoceros apply acme

That is all of it. The yml entry is one line and your env file stays untouched:

mcpServers:
  - name: forge

Where it runs

Remote (http), at https://mcp.atlassian.com/v1/forge/mcp. The request leaves the container, and it carries no credential of yours because there is none.

Verify it

monoceros check acme

MCP servers
  forge → Claude Code
      tools: forge-development-guide, forge-ui-kit-developer-guide, forge-backend-developer-guide, forge-app-manifest-guide, confluence-macro-developer-guide, jira-service-management-assets-guide, list-forge-modules, atlassian-design-tokens, search-forge-docs

Nine tools, and no sign-in line, because there is nothing to sign in to. If the list is missing, the container has no agent to register it with.

Remove it

monoceros remove-mcp-server acme forge