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/ads/public/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

  • ads_analyze_a11y — Analyzes a **string of React/JSX** code for likely accessibility issues (heuristics and/or axe-related paths) and returns hints that often **point to** `ads_suggest_a11y_fixes` or generic axe/WCAG-style context—not every finding maps to a specific ADS component fix. WHEN TO USE: You have component source as text and want automated checks or heuristics before or during a code review. LIMITATIONS: - Does not replace testing in a real browser with assistive technologies or full keyboard traversal. - For rendered UI, `ads_analyze_localhost_a11y` (live URL + axe) is preferable when available—it is **only exposed when this MCP runs locally**, not in the remote MCP deployment.
  • ads_get_a11y_guidelines — Returns Atlassian Design System (ADS) accessibility guidance: best practices and patterns for buttons, interactions, color contrast, forms, and other design-system topics shipped in this tool. Use this alongside the Context Engine MCP tool `get_accessibility_docs` for Atlassian-wide accessibility standards (e.g. A11YKB); this tool supplies ADS-specific component and pattern guidance. WHEN TO USE: You MUST call this when generating or substantially changing a new interactive or visual user interface built with ADS, or when you need topic-specific ADS guidance (e.g. focus, forms, motion). DO NOT rely on generic web accessibility advice alone—ADS conventions may differ. Use `get_accessibility_docs` for org-wide standards and this tool for ADS-topic guidance.
  • ads_get_all_components — Returns **every** Atlassian Design System component record as separate JSON text chunks (full catalog; large payload). WHEN TO USE: Last resort when `ads_plan` / `ads_search_components` is insufficient and you must enumerate all components. Prefer search for normal component picking. No parameters.
  • ads_get_all_icons — Returns **every** ADS icon record as separate JSON text chunks (full catalog; large payload). WHEN TO USE: Last resort when `ads_plan` / `ads_search_icons` is insufficient and you must enumerate all icons. Prefer search for normal icon picking. No parameters.
  • ads_get_all_tokens — Returns **every** ADS design token from bundled metadata (name, example value, usage guidelines)—one JSON object per token, **very large** output. WHEN TO USE: Last resort when `ads_plan` / `ads_search_tokens` cannot answer the question and you need the full list (e.g. exhaustive audit). Prefer targeted search for normal development. No parameters.
  • ads_get_guidelines — Returns Atlassian Design System (ADS) **foundations** guidelines as Markdown: the bundled design-system-docs foundations set (not component API docs). TOPIC COVERAGE: - **Content & UX writing**: messaging types (empty state, error, success, warning, info, feature discovery), voice and tone, inclusive language, grammar and style, date/time copy handoff, vocabulary pointers. - **Visual foundations**: color (roles, accents, palette, charts, pickers), borders and radius, elevation and z-index, spacing and layout primitives (box/inline/stack), grid, iconography, logos. - **Design tokens**: concepts, themes, migration, using tokens in code and in Figma. - **Typography**: typefaces, scale, applying text styles and tokens. - **Accessibility overview**: building accessible apps and related foundations pages bundled here. When working with content, use this tool alongside the Context Engine MCP tool `get_content_standards_docs` for Atlassian-wide content standards (CDSTD/BAIT-style org guidance); this tool supplies ADS-specific foundations. WHAT YOU GET: - With `terms`: fuzzy search over keywords and content; concatenated Markdown for matches. - Without `terms` (or empty): the full guideline set as Markdown. WHEN TO USE: Use this when you are **building or updating a visual interface**, **writing or reviewing user-facing copy**, or need to **answer foundations questions** about ADS: content patterns, visual appearance, design tokens, typography, spacing, color, grid, motion, and related topics shipped in this bundle. It is **not** for picking a component’s props or package (use `ads_plan` / `ads_search_components`) or for interactive accessibility rules and patterns (use `ads_get_a11y_guidelines`, with Context Engine `get_accessibility_docs` for org-wide a11y standards).
  • ads_get_lint_rules — Returns documentation for **Constellation** (Atlassian Design System) ESLint rules shipped with this MCP—rule purpose, examples, and fixes where available. WHAT YOU GET: - No `terms`: JSON array of all rule payloads. - With `terms`: fuzzy search (or exact rule name when `exactName` is true); JSON for one or more matching rules. WHEN TO USE: Explaining or fixing an ESLint message from ADS rules (e.g. `icon-label`, `ensure-proper-xcss-usage`, `no-deprecated-apis`), or browsing rule docs without opening the repo. Prefer this over guessing from rule id alone. This tool does not run ESLint; it only returns bundled documentation.
  • ads_i18n_conversion_guide — Returns a **bundled** step-by-step guide for replacing hardcoded UI strings with `formatMessage` (and related patterns) using @atlassian/jira-intl or react-intl-next: message constants, placeholders, descriptions, and scope/limitations for systematic refactors. When working with i18n or hardcoded UI strings, use this tool alongside the Context Engine MCP tool `get_i18n_docs` for Atlassian-wide Traduki / i18n standards (message definition, extraction, pluralisation, formatting, workflow); this tool supplies the concrete hardcoded-string → `formatMessage` playbook bundled in ADS MCP. WHEN TO USE / TYPICAL TRIGGERS: - Refactoring JSX or TS literals to i18n; "fix hardcoded string(s)", "convert hardcoded string in [file]", "literal string in JSX". - "Convert to i18n", "convert to formatMessage", "translate this string", "internationalize this string", "i18n this string". - "Use formatMessage", "use FormattedMessage", "wrap in formatMessage", "fix literal string". - ESLint: `Literal string in JSX content should be internationalized. Use FormattedMessage or intl.formatMessage()`. - ESLint: `@atlassian/i18n/no-literal-string-in-jsx`.
  • ads_migration_guides — Returns a structured Atlassian Design System (ADS) **migration guide** for a known package or API migration (before/after examples, best practices, links). WHEN TO USE: You are upgrading or refactoring code between ADS packages or APIs and need the official migration pattern for a specific id listed below. Pass **both** `migration` and `description` using a **matching pair** from the enum (schema enforces valid combinations). Available migrations: - "jira-spotlight": Use when code contains `JiraSpotlight` import from `@atlassian/jira-spotlight`,- "single-step": Use when code ONLY has `Spotlight` from `@atlaskit/onboarding` (no JiraSpotlight),- "multi-step": Migrate a multi-step spotlight tour from @atlaskit/onboarding to @atlaskit/spotlight,- "motion": Migrate a single step spotlight with entrance animation from @atlaskit/onboarding to @atlaskit/spotlight using @atlaskit/motion
  • ads_plan — Runs **ads_search_tokens**, **ads_search_icons**, **ads_search_components**, and **ads_search_atlaskit_components** in one call and returns a single JSON payload (each section only if that list was non-empty). Use this as the default way to discover ADS **tokens**, **icons**, and **components** (including legacy/broader Atlaskit) for a UI task. WHEN TO USE: **Implementing or iterating on a UI**—new screen, feature, or polish—and you need candidate **token** names, **icon** imports, and **component** packages/props in one pass. Also use when exploring ADS building blocks before you write code. At least one of `tokens`, `icons`, `components`, or `atlaskitComponents` must contain search terms (use `[]` for lists you do not need). Prefer supplying **multiple** terms per non-empty array when you know them—broader queries improve recall. Some queries return no rows where metadata is thin; try alternate wording. This is equivalent to calling the individual search tools; there are no extra merge semantics beyond concatenating results. Example request: ```json { "tokens": ["spacing", "inverted text", "background primary", "animation"], "icons": ["search", "folder", "user"], "components": ["button", "input", "select", "heading"], "atlaskitComponents": ["inline-dialog", "onboarding", "page-layout"] } ``` Example token usage: ```tsx import { token } from '@atlaskit/tokens'; const styles = css({ color: token('color.text'), padding: token('space.100') }); ``` Example icon usage: ```tsx import AddIcon from '@atlaskit/icon/core/add'; <AddIcon label="Add work item" size="small" /> ```
  • ads_search_components — Searches the bundled Atlassian Design System (ADS) component catalog. Returns JSON objects with **name**, **package**, **examples**, and **props** for each match (trimmed payload). WHEN TO USE: **Selecting which ADS component to use**—package name, examples, and props—before implementation. Use when composing a new view or swapping a primitive. Prefer `ads_plan` when you also need token and icon discovery in one shot.
  • ads_search_icons — Searches the bundled Atlassian Design System **icon** catalog. Returns JSON with **componentName**, **package**, and **usage** for each match. WHEN TO USE: **Choosing an icon** for a control, nav item, empty state, or illustration—find `@atlaskit/icon` import paths and usage notes. Prefer `ads_plan` when you also need tokens and components together. Example: ```tsx import AddIcon from '@atlaskit/icon/core/add'; <AddIcon label="Add work item" size="small" /> ```
  • ads_search_tokens — Searches Atlassian Design System **design tokens** from bundled metadata. Returns JSON objects with **name** and **exampleValue** for each match (search also considers description, usage guidelines, and CSS property hints in metadata). WHEN TO USE: **Styling or theming in code**—you need the right `token('…')` names for colors, space, typography, etc. Use during layout and visual work when tokens must match ADS. Prefer `ads_plan` when you also need icons and components in the same step. Example: ```tsx import { token } from '@atlaskit/tokens'; const styles = css({ color: token('color.text'), padding: token('space.100') }); ```
  • ads_suggest_a11y_fixes — Suggests remediation steps for an accessibility issue described in natural language (often pasted from **axe-core**, ESLint, or review). WHAT YOU GET (varies by match): - **Curated hit:** ADS-biased examples and patterns from this server’s recipe map (components, tokens, common fixes). - **No strong match:** Generic guidance (e.g. “use ADS components”, labeling, testing)—still useful, but **not** guaranteed to be ADS-specific. May reference axe/atlassian.design resources. WHEN TO USE: After `ads_analyze_a11y` or `ads_analyze_localhost_a11y`, or whenever you have a violation string. For **topic-level** Atlassian Design System accessibility guidance, call `ads_get_a11y_guidelines` (this tool is fix-oriented, not a full guideline browse). Does not replace manual testing with assistive technologies or keyboard-only navigation.
  • atlaskit_get_components — Returns the names and packages of all atlaskit components excluding components covered by the Atlassian Design System. WHEN TO USE: Use this when you want to see what components are available without the full metadata payload. No parameters.
  • atlaskit_search_components — Searches the bundled Atlaskit component catalog. Returns JSON objects with **name**, **package**, **examples**, and **props** for each match (trimmed payload). WHEN TO USE: **Selecting which Atlaskit component to use**—package name, examples, and props—before implementation. Use when searching for specific Atlaskit components that might not be in the core ADS catalog.

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