OpenApps

Atlassian Forge MCP server — tools & history

Atlassian Forge MCP server: observed open status, tool schemas, linked apps and version history.

Atlassian Forge

Endpoint: https://mcp.atlassian.com/v1/forge/mcp

Observed status: open. Checked: 2026-10-13T05:12:31+00:00.

Linked apps

  • Atlassian Forge

    Forge app builder skill bundle with Forge MCP integration for building, deploying, and troubleshooting Atlassian Forge apps.

  • Atlassian Forge Developer

    Forge app builder skill bundle with Forge MCP integration for building, deploying, and troubleshooting Atlassian Forge apps.

Observed tools

  • atlassian-design-tokens — Constructing Atlassian Design System token names for Forge apps: the grammar for each token family — color, elevation, spacing, radius, typography — the accepted enumerations, resolution rules, and how to choose and pair tokens. Token names apply to UI Kit and Custom UI alike; the surface-specific detail is UI Kit, where `xcss` and token-valued component props accept different sets. Read before emitting any token name; for a component's exact prop names use get-ui-kit-component-reference.
  • confluence-macro-developer-guide — The Confluence macro module end to end, in UI Kit and Custom UI: what makes a macro different from other modules, every macro property, the forms a configuration panel can take and how configuration values are stored and read, bodied macros, the context available at runtime, testing, and the mistakes agents commonly make. Read this only when building a Confluence macro, not for other Confluence modules.
  • diagnose-forge-error — Diagnose an HTTP error from an Atlassian REST call by matching apiEndpoint (and optional HTTP method) to the Atlassian OpenAPI spec. Returns the documented response description for the status code, OAuth2 scopes on the operation, and a short interpretation. Use when debugging 401/403/404/etc. from Forge or REST clients.
  • fetch-api-operation — Fetch the raw OpenAPI spec JSON for an Atlassian REST endpoint — the exact request/response schema, parameters, and security for a route. Pass the `route` (and ideally `method`) from a search-forge-docs result with kind="api". Returns the single operation when method is given, else the whole path item. Use after search-forge-docs when you need the precise schema/enums; for just the required scopes prefer get-api-required-scopes.
  • forge-app-manifest-guide — Authoring manifest.yml: every top-level section and the properties it takes — app, modules, resources, permissions and scopes, and the optional sections such as remotes, providers and environment variables — plus the wiring rules that connect a UI module to its resource and resolver, and the key naming and uniqueness rules. Read before adding or editing any manifest entry; every example is validated with forge lint, so prefer it over recalled syntax.
  • forge-backend-developer-guide — Building Forge app backends: wiring modules to backend code, the runtime limits that shape backend design and the async event patterns they force, storage, calling product and external APIs, resolvers, product event handlers, scheduled triggers, web triggers, error handling, source layout and testing. Read before writing resolvers, triggers, storage or API calls.
  • forge-development-guide — Forge platform fundamentals and the end-to-end development workflow: what makes the platform different and the constraints it imposes, local development setup, CLI usage, environments, deployment, installation, debugging, and app-wide code, security, architecture and testing standards. Read this for platform-level tasks — starting an app, setup, deploying, installing, or a cross-cutting standards question. For work inside a single area go straight to that guide instead: UI Kit, backends, the manifest, modules, Confluence macros or JSM Assets.
  • forge-ui-kit-developer-guide — Building Forge app frontends with UI Kit (@forge/react): choosing and composing components, the composition rules that are easy to get wrong, hooks and state, form state, bridge APIs for interacting with the product, error handling, performance, testing, and migrating from UI Kit 1. Read before writing UI code. For one component's exact props use get-ui-kit-component-reference; for the component inventory use list-ui-kit-components.
  • get-api-required-scopes — Get the exact required OAuth scopes for a specific Atlassian REST API endpoint and method, read straight from the Atlassian OpenAPI spec. This is the authoritative answer for scopes: declare what `requiredScopes` lists — classic scopes (e.g. write:jira-work) when the operation publishes them, otherwise granular ones (e.g. write:page:confluence); `alternativeScopes` is informational only. It returns scopes only; for request/response fields, parameters, or body schema use fetch-api-operation. `appAccessRuleCovered` tells you an admin data security policy can block the app from this data — it does NOT mean the call needs user context. Use whenever you need the scopes for manifest.yml.
  • get-ui-kit-component-reference — Returns prop types, required/optional flags, JSDoc descriptions, and a code-skeleton for one or more named Forge UI Kit components. This is the authoritative source for UI Kit component props — prefer it over search-forge-docs for prop details. Lookup is case-insensitive. Pass every component you plan to use in a single call (max 25). If a component is missing, the response includes close-name suggestions.
  • jira-service-management-assets-guide — Building JSM (Jira Service Management) apps against Assets (CMDB): why Assets differs from other product APIs, the scopes it needs, core object and attribute operations, AQL query syntax, the JSM modules, frontend and backend boundaries, and common failures. Read before writing any Assets call. For the scopes or schema of one specific Assets endpoint, prefer get-api-required-scopes and fetch-api-operation — the Assets REST API is indexed, and both accept the bare (/object/aql) and the callable (/jsm/assets/workspace/{workspaceId}/v1/object/aql) route form.
  • list-forge-modules — Every Forge module (extension point) with its exact manifest key and what it extends, grouped by product — Jira, Jira Software, Jira Service Management, Confluence, Bitbucket, Compass, Customer Service Management, Rovo, Automation and Teamwork Graph — plus the product-agnostic platform modules for functions, triggers, events, scheduled work, storage and APIs, and which modules are in Preview. Read to find where an app can extend a product, and to confirm a module key rather than recalling it. For the properties a module accepts once you have its key, use forge-app-manifest-guide.
  • list-ui-kit-components — Lists every Forge UI Kit component available in DynamicRenderer with a one-line description and docs URL. Call this first if you are unsure which component to use, then call get-ui-kit-component-reference for prop details on the components you choose.
  • search-forge-docs — Search the Forge documentation AND the Atlassian REST API specs and get focused results. Each result has a `kind`: "doc" (a guide-page chunk — `metadata.source` is the page URL) or "api" (a REST operation — has `route` + `method`, and its `pageContent` lists the required OAuth scopes; get the raw spec with fetch-api-operation). Use this to DISCOVER the right page or endpoint. For component props prefer get-ui-kit-component-reference; when you already know the exact endpoint prefer get-api-required-scopes. Forge specifics — scopes, module keys, API request/response schemas, and limits — change over time and are easy to misremember, so prefer these results over prior knowledge for such details.

Data as of 2026-10-13T05:12:31+00:00.

OpenApps records store listings and observed changes. Store ranks are not download counts; launch dates may be derived or use the first observation. Coverage gaps are shown in the interactive catalog.

REST API specification · Guide for AI clients · Manage API keys and MCP connections