Skip to main content
Fygment
<- Docs home

Guides

Alpha

Connect Claude Desktop to Fygment

Add Fygment as a Claude custom connector with the hosted MCP URL and OAuth, without copying a workspace key into Claude Desktop.

Audience
Claude Desktop users connecting their workspace through a hosted custom connector.
Updated
2026-08-22

Claude Desktop connects directly to Fygment’s hosted endpoint: paste the bare URL, leave static OAuth credentials blank, then approve the workspace in Fygment.

What this connection does

MCP (Model Context Protocol) is a standard way to let an AI client use Fygment workspace tools.

Claude Desktop uses Fygment’s hosted connection and OAuth. Do not add an API key, workspace slug, query string, or custom header to the URL.

Connect in Claude

  1. 1

    Open custom connector settings

    In Claude, open Settings, then Connectors, then Add custom connector.

  2. 2

    Enter the fields

    Set Name to `Fygment` and Remote MCP server URL to `https://fygment.dev/api/mcp`. Leave OAuth Client ID and OAuth Client Secret blank unless Fygment support gives you static credentials.

  3. 3

    Connect and approve access

    Choose Connect, sign in with Fygment, and approve the workspace connection.

  4. 4

    Verify the connection

    Ask Claude to search Fygment for a known workflow. If it fails, re-add the connector with the exact bare URL above.

Keep credentials out

OAuth is the normal path

Fygment discovers OAuth details through the hosted endpoint. A static client secret is not required for the Claude custom connector setup.

Related docs

  • Set up Fygment MCP

    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.

  • Connect ChatGPT to Fygment

    ChatGPT connects to Fygment’s hosted endpoint. Paste the URL exactly, choose OAuth when prompted, 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.

  • Troubleshooting

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