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-11-01
The Fygment MCP server offers 23 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, share, retire 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_searchSearch the Skills you can see in this workspace. All plans.
skill_getGet the details of one Skill, with its versions and files if asked. Only workspace owners and admins, the Skill's owner or author, and leads of a team it's shared with see the text of a version that isn't approved. All plans.
skill_list_versionsList the published versions of a Skill. All plans.
skill_get_workflowGet the step-by-step workflow of one Skill version. Only workspace owners and admins, the Skill's owner or author, and leads of a team it's shared with can read a version that isn't approved. All plans.
skill_get_diffCompare two versions of a Skill, or a version and a proposed change. Only workspace owners and admins, the Skill's owner or author, and leads of a team it's shared with can compare a version that isn't approved. All plans.
skill_check_updatesCheck installed Skills against the approved versions. All plans.
Import, change and review Skills (fygment:write)
skill_import_github_previewPreview the Skills in a GitHub repository before importing. Nothing is saved. Advanced / Teams plan.
skill_import_githubImport a Skill you picked from a GitHub preview. The answer says whether it was published, is still being checked, or is held for a decision, and may carry a short note. Advanced / Teams plan.
skill_import_localImport a Skill folder from your computer, after a preview you confirm. For developer tools. All plans; Solo workspaces get up to 20 attempts a day, refused imports included.
skill_import_textBring in a Skill and its files as text, after a preview you confirm. It starts as your own Skill, and workspace owners and admins can view it. All plans; Solo workspaces get up to 20 attempts a day, refused imports included, shared with Skill folders.
skill_approve_importApprove or reject an import that is waiting for review. Owners and admins; a member only for a Caution on their own personal Skill. All plans.
skill_shareShare a Skill with a team or the whole workspace, after a preview you confirm. Owners and admins share with any team and the workspace, team leads with rights on the Skill with their own team, and a Skill's owner or manager can ask for workspace sharing. Team plan.
skill_retireRetire a Skill for the workspace, or bring one back, after a preview you confirm. Owners and admins only. All plans.
skill_propose_changePropose a change to a Skill for its owner to review. All plans. Asking to share a Skill this way needs the Team plan.
skill_review_proposalApprove, reject or merge a proposed change. Needs review rights on the Skill. All plans. Approving a request to share a Skill needs the Team plan.
skill_submit_feedbackSend feedback on a Skill to its owner. All plans.
skill_run_evaluationCheck whether a Skill declares tests and run a quick safety check on it. All plans.
skill_scan_trustScan a Skill for trust and safety issues. The quick scan works on all plans; the full scan needs the Advanced / Teams plan.
Bringing in a Skill from an AI tool
skill_import_text takes one Skill as its full SKILL.md, in readable text, up to 256 KB. The first call shows what would be saved and saves nothing. The second call imports it, after you agree.
Extra files go in the same call, as text, up to 1 MB in total. Images and other non-text files can’t go this way. A tool that can make a zip file can send those with skill_import_local. Otherwise your AI tool tells you which files can’t be sent.
The safety check can take a few minutes. Your AI tool tells you it’s still checking and asks again until it’s done. Nothing is saved until the check ends.
The daily limit on Solo counts attempts. An attempt counts once you confirm the import, even if the import is then refused. A preview uses none. With skill_import_text, neither does text that fails its checks or contains a secret. Asking again while a safety check is still running doesn’t use another.
Install Skills (fygment:install)
skill_install_instructionsGet the steps to install a Skill in a chosen AI tool. All plans.
skill_export_packageGet an installable package of a Skill, after a safety check. All plans.
skill_report_installRecord that a Skill was installed on this computer. All plans.
Account and setup (no scope needed)
fygment_current_userShow who is signed in, which workspace the connection uses, its plan and your role. All plans.
fygment_agent_setupCheck whether the Fygment companion Skill is set up in this AI tool, and how this tool keeps it. 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 and for bringing in your own Skills from an AI tool, 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.