Skip to main content
Fygment
<- Docs home

Guides

Alpha

Connect Claude Code to Fygment

Use the Fygment CLI to connect Claude Code to your workspace and make its governed Skills available in local sessions.

Audience
Claude Code users connecting a local workspace-scoped Fygment tool server.
Updated
2026-08-22

The guided CLI path signs you in, previews the local change, and registers a local Fygment connector through the installed Claude CLI.

What this connection does

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

The recommended setup uses a local authenticated connector, so the Fygment sign-in and workspace choice stay in the CLI rather than Claude Code configuration.

Recommended setup

Run this in a terminal, replacing the placeholder with the workspace slug you want to connect. It opens Fygment sign-in when needed and asks before it writes local configuration.

npx fygment setup --workspace=<workspace-slug> --target=claude-codeAlpha

Sign in, register the local connector through Claude Code, and install the Fygment companion Skill.

Finish and check

  1. 1

    Approve the preview

    Confirm the workspace before accepting the stdio MCP entry that setup adds through the Claude CLI.

  2. 2

    Restart Claude Code

    Start a new session so it loads the connector and companion Skill.

  3. 3

    Try a safe request

    Ask Claude Code to search Fygment for a workflow. If it cannot connect, run `fygment doctor` before changing configuration by hand.

Manual command

Use this only when guided setup is unavailable

After `fygment auth login --workspace=<workspace-slug>` completes, the local connector command is `claude mcp add --transport stdio fygment -- npx -y fygment mcp proxy`. Guided setup is preferred because it selects the workspace, previews changes, and installs the companion Skill.

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 OpenAI Codex to Fygment

    The guided CLI path signs you in, previews the local Codex registry change, and keeps workspace authentication in the Fygment CLI rather than a config file.

  • Install Skills in Claude-family tools

    Claude-family setup follows the same workspace-approved package model as Codex, with local writes kept explicit and previewable.

  • Troubleshooting

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