{"apiVersion":"v1","directorySlug":"atlassian-mcp-acbe7eade9","title":"Atlassian Forge","description":"Forge app builder skill bundle with Forge MCP integration for building, deploying, and troubleshooting Atlassian Forge apps.","pageUrl":"https://www.mcpbundles.com/skills/atlassian-mcp-acbe7eade9","connectPath":"importable","connectAction":"import_server","catalogListing":false,"bundleSlug":null,"listingKind":"remote_mcp","kind":"provider","transportUrl":"https://mcp.atlassian.com/v1/forge/mcp","hostedMcpUrl":null,"toolCount":14,"toolInventoryStatus":"observed","refreshedAt":"2026-11-03T13:26:00.516172+00:00","registryName":"com.atlassian/atlassian-mcp-acbe7eade9","registryVersion":"2026.11.3","registryEligible":true,"tools":[{"name":"forge-development-guide","description":"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 man","inputSchema":{"type":"object","properties":{}},"logicalName":"forge-development-guide","displayName":"forge-development-guide","title":"forge-development-guide","annotations":{"untrustedContentHint":true,"readOnlyHint":true}},{"name":"forge-ui-kit-developer-guide","description":"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.","inputSchema":{"type":"object","properties":{}},"logicalName":"forge-ui-kit-developer-guide","displayName":"forge-ui-kit-developer-guide","title":"forge-ui-kit-developer-guide","annotations":{"untrustedContentHint":true,"readOnlyHint":true}},{"name":"forge-backend-developer-guide","description":"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.","inputSchema":{"type":"object","properties":{}},"logicalName":"forge-backend-developer-guide","displayName":"forge-backend-developer-guide","title":"forge-backend-developer-guide","annotations":{"untrustedContentHint":true,"readOnlyHint":true}},{"name":"forge-app-manifest-guide","description":"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.","inputSchema":{"type":"object","properties":{}},"logicalName":"forge-app-manifest-guide","displayName":"forge-app-manifest-guide","title":"forge-app-manifest-guide","annotations":{"untrustedContentHint":true,"readOnlyHint":true}},{"name":"confluence-macro-developer-guide","description":"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.","inputSchema":{"type":"object","properties":{}},"logicalName":"confluence-macro-developer-guide","displayName":"confluence-macro-developer-guide","title":"confluence-macro-developer-guide","annotations":{"untrustedContentHint":true,"readOnlyHint":true}},{"name":"jira-service-management-assets-guide","description":"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 (","inputSchema":{"type":"object","properties":{}},"logicalName":"jira-service-management-assets-guide","displayName":"jira-service-management-assets-guide","title":"jira-service-management-assets-guide","annotations":{"untrustedContentHint":true,"readOnlyHint":true}},{"name":"list-forge-modules","description":"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. Fo","inputSchema":{"type":"object","properties":{}},"logicalName":"list-forge-modules","displayName":"list-forge-modules","title":"list-forge-modules","annotations":{"untrustedContentHint":true,"readOnlyHint":true}},{"name":"atlassian-design-tokens","description":"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.","inputSchema":{"type":"object","properties":{}},"logicalName":"atlassian-design-tokens","displayName":"atlassian-design-tokens","title":"atlassian-design-tokens","annotations":{"untrustedContentHint":true,"readOnlyHint":true}},{"name":"search-forge-docs","description":"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-requir","inputSchema":{"type":"object","$schema":"http://json-schema.org/draft-07/schema#","required":["query"],"properties":{"query":{"type":"string","maxLength":250,"minLength":1}},"additionalProperties":false},"logicalName":"search-forge-docs","displayName":"search-forge-docs","title":"search-forge-docs","annotations":{"untrustedContentHint":true,"readOnlyHint":true}},{"name":"get-api-required-scopes","description":"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. `app","inputSchema":{"type":"object","$schema":"http://json-schema.org/draft-07/schema#","required":["endpoint","method"],"properties":{"method":{"type":"string","pattern":"^[A-Z]+$","maxLength":10,"minLength":3},"endpoint":{"type":"string","pattern":"^\\/","maxLength":500,"minLength":1}},"additionalProperties":false},"logicalName":"get-api-required-scopes","displayName":"get-api-required-scopes","title":"get-api-required-scopes","annotations":{"untrustedContentHint":true,"readOnlyHint":true}},{"name":"diagnose-forge-error","description":"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.","inputSchema":{"type":"object","$schema":"http://json-schema.org/draft-07/schema#","required":["errorCode","apiEndpoint"],"properties":{"method":{"type":"string","pattern":"^[A-Z]+$","maxLength":10,"minLength":3},"errorCode":{"type":"integer"},"apiEndpoint":{"type":"string","pattern":"^\\/","maxLength":500,"minLength":1},"errorMessage":{"type":"string","maxLength":2000}},"additionalProperties":false},"logicalName":"diagnose-forge-error","displayName":"diagnose-forge-error","title":"diagnose-forge-error","annotations":{"untrustedContentHint":true,"readOnlyHint":true}},{"name":"list-ui-kit-components","description":"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.","inputSchema":{"type":"object","properties":{}},"logicalName":"list-ui-kit-components","displayName":"list-ui-kit-components","title":"list-ui-kit-components","annotations":{"untrustedContentHint":true,"readOnlyHint":true}},{"name":"get-ui-kit-component-reference","description":"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.","inputSchema":{"type":"object","$schema":"http://json-schema.org/draft-07/schema#","required":["names"],"properties":{"names":{"type":"array","items":{"type":"string","maxLength":64,"minLength":1},"maxItems":25,"minItems":1}},"additionalProperties":false},"logicalName":"get-ui-kit-component-reference","displayName":"get-ui-kit-component-reference","title":"get-ui-kit-component-reference","annotations":{"untrustedContentHint":true,"readOnlyHint":true}},{"name":"fetch-api-operation","description":"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.","inputSchema":{"type":"object","$schema":"http://json-schema.org/draft-07/schema#","required":["endpoint"],"properties":{"method":{"type":"string","pattern":"^[A-Za-z]+$"},"endpoint":{"type":"string","pattern":"^\\/","maxLength":500,"minLength":1}},"additionalProperties":false},"logicalName":"fetch-api-operation","displayName":"fetch-api-operation","title":"fetch-api-operation","annotations":{"untrustedContentHint":true,"readOnlyHint":true}}],"toolSource":"directory_preview","agentAction":"both","installLinks":[{"id":"cursor","label":"Cursor","href":"cursor://anysphere.cursor-deeplink/mcp/install?name=Atlassian-Forge&config=eyJ1cmwiOiAiaHR0cHM6Ly9tY3AuYXRsYXNzaWFuLmNvbS92MS9mb3JnZS9tY3AifQ%3D%3D"},{"id":"vscode","label":"VS Code","href":"vscode:mcp/install?%7B%22name%22%3A%22Atlassian-Forge%22%2C%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fmcp.atlassian.com%2Fv1%2Fforge%2Fmcp%22%7D"},{"id":"vscode-insiders","label":"VS Code Insiders","href":"vscode-insiders:mcp/install?%7B%22name%22%3A%22Atlassian-Forge%22%2C%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fmcp.atlassian.com%2Fv1%2Fforge%2Fmcp%22%7D"},{"id":"claude-web","label":"Claude.ai","href":"https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=Atlassian+Forge&connectorUrl=https%3A%2F%2Fmcp.atlassian.com%2Fv1%2Fforge%2Fmcp"},{"id":"codex","label":"Codex","copyText":"codex mcp add \"Atlassian-Forge\" --url \"https://mcp.atlassian.com/v1/forge/mcp\""},{"id":"chatgpt","label":"ChatGPT","href":"https://www.mcpbundles.com/docs/integrations/chatgpt"}],"catalogUrl":"https://www.mcpbundles.com/api/directory/v1/servers/atlassian-mcp-acbe7eade9","callUrl":"https://www.mcpbundles.com/api/directory/v1/servers/atlassian-mcp-acbe7eade9/tools/{tool}","mcpServerUrl":"https://mcp.atlassian.com/v1/forge/mcp","liveCatalogUrl":"https://www.mcpbundles.com/api/directory/v1/servers/atlassian-mcp-acbe7eade9?live=1"}