Connect ChatGPT to Fygment

Create a remote Fygment connector in ChatGPT using the hosted MCP URL and OAuth, with no workspace API key in the connector settings.

Audience: ChatGPT users who want their connector to search and use workspace-visible Fygment Skills.
Updated: 2026-08-22

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

1
Create a remote MCP connector
Open ChatGPT connector setup and create a remote MCP connector.
2
Paste the Fygment server URL
Use `https://fygment.dev/api/mcp` as the Remote MCP server URL. Do not add a workspace slug, query string, API key, or header.
3
Choose OAuth and sign in
When ChatGPT asks how to authenticate, choose OAuth. Sign in with Fygment and approve the workspace connection.
4
Check the first request
Ask ChatGPT to search Fygment for a workflow. It should return only Skills visible in the workspace you approved.

Connection safety

The hosted connector discovers OAuth metadata from Fygment. Do not copy a workspace API key into ChatGPT or save a token in a prompt.

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 Claude Desktop to Fygment
Claude Desktop connects directly to Fygment’s hosted endpoint: paste the bare URL, leave static OAuth credentials blank, 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.