Skip to main content
Fygment
Get started
<- Docs home

Guides

Set up Fygment MCP

Connect hosted MCP clients or local editors to the Fygment MCP endpoint without exposing tokens or workspace-private data.

Audience
Users connecting Claude, ChatGPT, other hosted AI clients, local editors, or CLI clients to Fygment MCP.
Updated
2026-10-25

MCP setup gives AI clients access to workspace-scoped Fygment tools. Hosted clients use OAuth; local clients use guided setup and a local authenticated proxy where needed.

Hosted MCP setup

Hosted clients such as Claude and ChatGPT connect to one address: https://fygment.dev/api/mcp. Each client has its own guide: Connect Claude Desktop to Fygment, Connect ChatGPT to Fygment, and Connect another MCP client to Fygment.

  1. 1

    Copy the bare MCP endpoint

    Use https://fygment.dev/api/mcp exactly. Do not add a workspace slug, query string, API key, or header. The client finds the sign-in details on its own.

  2. 2

    Complete OAuth

    Authorize only after confirming the workspace. Tokens are workspace-scoped and should not expose other workspace data.

  3. 3

    Verify tools

    Use a simple search or get call to confirm the client can see workspace-visible Skills only. The MCP tools reference lists every tool and the permission it needs.

Other hosted clients

Other hosted AI clients, such as Manus or Perplexity, can connect when they support a remote MCP server with OAuth. Follow Connect another MCP client to Fygment: use the same URL and choose OAuth when asked.

Local editors and CLI clients

Claude Code and Codex have their own guides. For Cursor and Gemini CLI, run guided setup in a terminal, replacing the placeholder with your workspace slug.

npx fygment setup --workspace=<workspace-slug> --target=cursor

Sign in and add Fygment to Cursor.

npx fygment setup --workspace=<workspace-slug> --target=gemini-cli

Sign in and add Fygment to Gemini CLI.

Connection problems

If a hosted client cannot reach Fygment

Try connecting again after a minute. If it still fails, contact Fygment support with the client name and the time you tried, so we can find the request.

Related docs

  • Get started with Fygment

    Start here when you need the shortest path from sign-in to a workspace that can import, review, install, and check governed AI Skills.

  • Connect Claude Code to Fygment

    The guided CLI path signs you in, previews the local change, and registers a local Fygment connector through the installed Claude CLI.

  • Connect Claude Desktop to Fygment

    Claude connects directly to Fygment’s hosted endpoint. Add a custom connector with the bare URL, sign in with Claude’s published identity, then approve the workspace in Fygment.

  • Connect OpenAI Codex to Fygment

    The guided CLI path signs you in, previews the local Codex registry change, and keeps workspace authentication in the Fygment CLI rather than a config file.

  • Connect ChatGPT to Fygment

    ChatGPT connects to Fygment’s hosted endpoint. Add a custom MCP server in Plugins, keep OAuth, create it as a plugin, and approve only the workspace you intend to use.

  • Connect another MCP client to Fygment

    Use the bare hosted endpoint, select OAuth or protected-resource discovery, and confirm that the client can complete a workspace-scoped Fygment approval.

  • MCP tools reference

    The Fygment MCP server offers 20 tools. Most need a permission (scope) that you approve when you connect: fygment:read, fygment:write or fygment:install. Two account tools need none.

  • CLI reference

    The CLI is the local bridge between a governed workspace and writable AI harness targets. Use it for setup, install state, update checks, setup checks, and selected imports.

  • Troubleshooting

    Start with safe, non-sensitive checks. Fygment support reports should capture bounded diagnostics, not package bodies, secrets, raw prompts, or local paths.