Skip to main content
Fygment
<- Docs home

Guides

Alpha

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, Manus, Perplexity, local editors, or CLI clients to Fygment MCP.
Updated
2026-05-20

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

  1. 1

    Copy the bare MCP endpoint

    Use the public MCP server URL shown in workspace MCP setup. Hosted clients should discover OAuth metadata from the protected-resource challenge.

  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.

Cloudflare/WAF

Allow user-triggered hosted MCP traffic

If a protected edge blocks hosted clients, allow the documented user-agent path for the hosted client before debugging the MCP tool registry itself.

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.

  • 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, readiness, 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.