Reference

MCP tools reference

Every tool the Fygment MCP server offers, what it does, the OAuth permission (scope) it needs, and which tools need the Advanced / Teams plan.

Audience: Users and workspace admins who want to know what an AI client can do once it is connected to Fygment.
Updated: 2026-10-25

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.

How permissions work

When you connect an AI client, you approve permissions called scopes. fygment:read lets the client find and read Skills. fygment:write lets it import, propose, review and give feedback. fygment:install lets it install Skills and report installs.

If a tool needs a scope the connection does not have, you do not get an HTTP 403. The tool answers with an error result instead. Its structuredContent carries error_code: "insufficient_scope" and names the scope to ask for. Reconnect and approve that scope, then try again.

Tools marked Advanced / Teams plan need a paid workspace. On a Solo workspace they answer with an error that names the plan they need.

Find and read Skills (fygment:read)

skill_search

Search the Skills you can see in this workspace. All plans.

skill_get

Get the details of one Skill, with its versions and files if asked. All plans.

skill_list_versions

List the published versions of a Skill. All plans.

skill_get_workflow

Get the step-by-step workflow of one Skill version. All plans.

skill_get_diff

Compare two versions of a Skill, or a version and a proposed change. All plans.

skill_check_updates

Check installed Skills against the approved versions. All plans.

Import, change and review Skills (fygment:write)

skill_import_github_preview

Preview the Skills in a GitHub repository before importing. Nothing is saved. Advanced / Teams plan.

skill_import_github

Import a Skill you picked from a GitHub preview. Advanced / Teams plan.

skill_import_local

Import a Skill folder from your computer, after a preview you confirm. Advanced / Teams plan.

skill_approve_import

Approve or reject an import that is waiting for review. Owners and admins only. All plans.

skill_propose_change

Propose a change to a Skill for its owner to review. All plans.

skill_review_proposal

Approve, reject or merge a proposed change. Needs review rights on the Skill. All plans.

skill_submit_feedback

Send feedback on a Skill to its owner. All plans.

skill_run_evaluation

Check whether a Skill declares tests and run a quick safety check on it. All plans.

skill_scan_trust

Scan a Skill for trust and safety issues. The quick scan works on all plans; the full scan needs the Advanced / Teams plan.

Install Skills (fygment:install)

skill_install_instructions

Get the steps to install a Skill in a chosen AI tool. All plans.

skill_export_package

Get an installable package of a Skill, after a safety check. All plans.

skill_report_install

Record that a Skill was installed on this computer. All plans.

Account and setup (no scope needed)

fygment_current_user

Show who is signed in, which workspace the connection uses, its plan and your role. All plans.

fygment_agent_setup

Check whether the Fygment companion Skill is installed and current in this AI tool. All plans.

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 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 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.
Billing and plans
Billing uses a workspace effective tier: Solo remains free for the local creator loop, Advanced / Teams (Fygment Team) unlocks paid collaboration and external import actions, and Enterprise is support-managed.
Troubleshooting
Start with safe, non-sensitive checks. Fygment support reports should capture bounded diagnostics, not package bodies, secrets, raw prompts, or local paths.