Skip to main content
Fygment
Get started
<- Docs home

Guides

Connect another MCP client to Fygment

Connect an OAuth-capable MCP client to Fygment’s hosted Streamable HTTP endpoint using portable settings shared by supported clients.

Audience
Users of an MCP client that is not listed in a dedicated Fygment connection guide.
Updated
2026-10-25

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

What this connection does

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

This guide applies to clients that support a remote Streamable HTTP MCP server and OAuth or OAuth protected-resource discovery. Client menus vary, but the connection values do not.

Portable connection settings

  1. 1

    Add a remote MCP server

    Create a remote or hosted MCP server entry. Use HTTP or Streamable HTTP when the client asks for transport.

  2. 2

    Use the bare endpoint

    Set the server URL to https://fygment.dev/api/mcp. Do not add a workspace slug, query string, API key, token, or custom header.

  3. 3

    Use OAuth

    Choose OAuth or OAuth protected-resource discovery. The client should discover Fygment’s authorization details and show Fygment sign-in and workspace approval.

  4. 4

    Verify workspace access

    Run a simple Fygment search. If the client cannot discover OAuth, use its current MCP documentation and contact Fygment support with the client name and safe error details.

Not a legacy key setup

Do not configure a workspace API key by default

The public hosted connection path is OAuth-first. API-key authentication is a legacy or development fallback, not the normal 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.

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

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

  • Troubleshooting

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