Documentation
Fygment docs for real product use.
Set up a workspace, import or create Skills, review and approve packages, connect Codex or Claude-family tools, configure MCP, and troubleshoot key workflows without bouncing through marketing pages or authenticated dead ends.
Start here
First useful path
- 1
Get started with Fygment
Start here when you need the shortest path from sign-in to a workspace that can import, review, install, and check governed AI Skills.
Open guide - 2
Import Skills
Import turns an existing Skill into a validated Fygment package. Start with one selected package or public source and review the validation result before broader migration.
Open guide - 3
Review and approve Skills
Governance is the difference between a shared Skill library and a loose pile of files. Review decisions decide what can be installed and trusted.
Open guide - 4
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.
Open guide
Guides
Guides
Task-oriented product documentation for setup, Skills, installs, and MCP.
Get started with Fygment
Create a workspace and reach the first useful Fygment workflow without guessing where to click.
Audience: New users, workspace owners, and teammates joining an existing workspace.
Import Skills
Import Skill packages, Skill files, and supported public sources while keeping validation, provenance, and review state explicit.
Audience: Users moving local or public Skills into a governed workspace.
Create a Skill
Start a valid draft Skill from a template, then add instructions and metadata before review or publication.
Audience: Vibecoders, super-users, and workspace builders creating new Skills.
Review and approve Skills
Use lifecycle states, proposal review, version decisions, and owner/admin approvals to keep install decisions clear.
Audience: Owners, admins, maintainers, and reviewers managing Skill lifecycle.
Install Skills in Codex
Use Fygment CLI setup, install, check, and update flows for Codex-targeted Skill usage.
Audience: Codex users who want workspace-approved Skills in their local harness.
Install Skills in Claude-family tools
Use Fygment setup and install/check flows with Claude Code and Claude-family harnesses where a writable target is available.
Audience: Claude Code and Claude-family users using Fygment-managed Skills.
Set up Fygment MCP
Connect hosted MCP clients or local editors to the Fygment MCP endpoint without exposing tokens or workspace-private data.
Audience: Users connecting Claude, ChatGPT, Manus, Perplexity, local editors, or CLI clients to Fygment MCP.
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.
Connect Claude Desktop to Fygment
Add Fygment as a Claude custom connector with the hosted MCP URL and OAuth, without copying a workspace key into Claude Desktop.
Audience: Claude Desktop users connecting their workspace through a hosted custom connector.
Connect OpenAI Codex to Fygment
Use the Fygment CLI to connect Codex to one workspace through a local authenticated MCP proxy and companion Skill.
Audience: OpenAI Codex users who want Fygment search and governed Skills in local coding sessions.
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.
Connect another MCP client to Fygment
Connect an OAuth-capable MCP client to Fygment’s hosted Streamable HTTP endpoint using portable settings shared by supported clients.
Audience: Users of an MCP client that is not listed in a dedicated Fygment connection guide.
Concepts
Concepts
Core product concepts that explain how Fygment scopes trust, access, and workflow state.
Reference
Reference
Command and interface references for users wiring Fygment into real local workflows.
CLI reference
Reference for Fygment CLI commands: setup, install, check, update, readiness, lockfile, sync, doctor, and import.
Audience: Power users and workspace operators using Fygment from a terminal.
REST API reference
How to call the Fygment REST API: base URL, authentication, versioning and deprecation policy, rate limits and the error format.
Audience: Developers and agents calling Fygment from scripts, integrations or API plugins.
Troubleshooting
Troubleshooting
Safe checks and report guidance when imports, setup, MCP, or access do not behave as expected.
Billing and security
Billing and security
Plans, billing, privacy, and trust boundaries.
Billing and plans
Understand Fygment plans, how workspace billing works with Stripe, and what each tier includes.
Audience: Workspace owners and admins deciding how their workspace should be billed.
Security and privacy boundaries
What Fygment does and does not expose in docs, support reports, admin views, imports, MCP, and billing metadata.
Audience: Workspace operators, support reviewers, and users checking trust boundaries.
Product docs explain how to use Fygment. Resources are for broader articles and category thinking. For help or policies, see Support, Privacy, and Terms.