Skip to main content
<- Docs home

Guides

Connect ChatGPT to Fygment

Add Fygment to ChatGPT as a custom MCP server plugin using the hosted MCP URL and OAuth, with no workspace API key in the settings.

Audience
ChatGPT users who want their connector to search and use workspace-visible Fygment Skills.
Updated
2026-10-25

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.

What this connection does

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

ChatGPT is a hosted client, so it connects directly to Fygment over HTTPS and uses OAuth to keep the connection limited to the chosen workspace.

Connect in ChatGPT

These steps follow OpenAI’s guide to connecting an MCP server to ChatGPT. Menu names can change.

  1. 1

    Open Plugins

    In ChatGPT, open Plugins (chatgpt.com/plugins). Select +, then Add custom MCP server.

  2. 2

    Enter the name and connection

    Set Name to Fygment. For Connection, choose Public endpoint and enter https://fygment.dev/api/mcp. Do not add a workspace slug, query string, API key, or header.

  3. 3

    Keep OAuth

    Leave Authentication on OAuth.

  4. 4

    Confirm and create

    Review the warning and select “I understand and want to continue”. Then select Create as a plugin.

  5. 5

    Sign in and allow access

    Sign in to Fygment and allow access to the workspace you want to use.

  6. 6

    Check the first request

    Ask ChatGPT to search Fygment for a workflow. It should return only Skills visible in the workspace you approved.

Business and Enterprise accounts

Your admin may need to allow it

On ChatGPT Business or Enterprise accounts, workspace or admin policy can block custom MCP servers. If you cannot add Fygment, ask your ChatGPT admin.

Never copy a workspace API key into ChatGPT or save a token in a prompt.

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