Skip to main content
Fygment
Get started
<- Docs home

Troubleshooting

Troubleshooting

Resolve common Fygment setup, import, MCP, install, support-report, and access issues without leaking sensitive data.

Audience
Users and support operators diagnosing setup, import, and access workflows.
Updated
2026-10-25

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

Common issues

A docs or setup link redirects to login unexpectedly.

Check: Confirm the route is intended to be public. Public docs, resources, support, privacy, and terms should not require a session.

Next: Report the route and exact URL through support if a public docs page redirects.

MCP connects but tools return no workspace data.

Check: Ask the client to run the fygment_current_user tool. It shows which workspace the connection uses. If a tool answers with error_code: "insufficient_scope", the connection is missing a permission that tool needs.

Next: Disconnect and reconnect, then approve the right workspace and every permission the client asks for. Verify with a simple workspace-visible Skill search.

Import fails for a public source.

Check: Look for candidate selection, validation, unsupported provider, or inaccessible source errors.

Next: Use the report action only after reviewing the disclosure; do not paste tokens or private package content into support.

Support reports

Send safe details only

Good support reports include workspace slug, page or command, timing, non-sensitive error text, and diagnostic id if visible. Do not send API keys, OAuth tokens, private package bodies, secrets, local full paths, stdout, stderr, or raw prompts.

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.

  • MCP tools reference

    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.

  • Import Skills

    Import turns a Skill you already have into a Fygment Skill. Each import is validated and trust reviewed. A Skill that passes is ready for you to use right away. Sharing it more widely is a separate step.

  • Security and privacy boundaries

    The Fygment trust model is metadata-minimizing: keep customer Skill content, package bodies, prompts, secrets, tokens, and raw local paths out of admin, support, analytics, and billing surfaces.