Skip to content
Back to search
100
MCP live MCP 2025-11-25 streamable-http

forge-skills (forge)

claude-plugin:forge-skills/forge

Forge-focused skills and MCP configuration for Atlassian Forge: scaffold and deploy apps (forge create, templates, dev spaces), build Teamwork Graph connectors for Rovo Search/Rovo Chat, pre-deploy review, systematic debugging, plus Forge docs and Atlassian Design System lookups via MCP.

Listed in Claude Code plugin
Watch this dependency Share evidence report
Uptime
100.0%
5 direct probes · 30d
Response
732ms
last probe
Tools
14
callable
Resources
0
readable
Prompts
0
available
Score: 100/100
Handshake verified by our own probe.
pass Answers the MCP handshake 50/50
The handshake and the list calls succeeded on the primary URL.
pass Lists tools, resources or prompts 30/30
14 tools, 0 resources, 0 prompts returned.
pass 3 or more catalogue items 10/10
14 items in total; 3 or more earns these points.
pass Describes itself 10/10
288 characters; more than 30 earns these points.

Tools · 14

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, ins…

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 w…

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…

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 vari…

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 v…

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 modu…

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 Servic…

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 ho…

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 opera…

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 `req…

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, OA…

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-refer…

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…

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-do…

How to use

Claude Desktop or claude.ai: add a custom connector (Customize → Connectors; on Team and Enterprise plans an owner adds it under Organization settings → Connectors) with this server URL: https://mcp.atlassian.com/v1/forge/mcp

Cursor or Cline: add to your MCP config:

{
  "mcpServers": {
    "forge-skills_(forge)": {
      "url": "https://mcp.atlassian.com/v1/forge/mcp",
      "transport": "streamable-http"
    }
  }
}