Chuyển tới nội dung chính

Troubleshooting Guide

Common issues and solutions for FAOS MCP integration with Claude Desktop.

Quick Diagnostics

Run these checks first:

# 1. Verify MCP server installed
faos-mcp --version

# 2. Validate config JSON
cat ~/.config/claude/mcp.json | python -m json.tool

# 3. Test API connectivity
curl -H "Authorization: Bearer $FAOS_API_TOKEN" https://api.faosx.ai/health

Installation Issues

"faos-mcp: command not found"

Symptom: faos-mcp --version returns "command not found"

Causes:

  • Package not installed
  • Not in PATH
  • Virtual environment not activated

Solutions:

  1. Verify installation:
# Check if installed
pip show faos-mcp
# Or for pipx
pipx list | grep faos-mcp
  1. Reinstall:
pipx install faos-mcp
# Ensure PATH is updated
pipx ensurepath
# Restart terminal
  1. Use full path in config:
{
"servers": {
"faos": {
"command": "/Users/yourname/.local/bin/faos-mcp"
}
}
}

Find the path:

which faos-mcp  # macOS/Linux
where faos-mcp # Windows

"Python version not supported"

Symptom: Installation fails with Python version error

Solutions:

  1. Check version:
python --version
# Must be 3.10+
  1. Use pyenv to install correct version:
pyenv install 3.11.0
pyenv global 3.11.0
  1. Use pipx with specific Python:
pipx install faos-mcp --python python3.11

Configuration Issues

"MCP server not found" / Tools not appearing

Symptom: Claude doesn't show FAOS tools when asked

Solutions:

  1. Check config file location:
OSPath
macOS~/.config/claude/mcp.json
Windows%APPDATA%\claude\mcp.json
Linux~/.config/claude/mcp.json
  1. Validate JSON syntax:
cat ~/.config/claude/mcp.json | python -m json.tool

Common JSON errors:

  • Missing commas between properties
  • Trailing commas (not allowed in JSON)
  • Unquoted strings
  • Wrong quote characters (use ", not ' or ")
  1. Check server name spelling:
{
"servers": {
"faos": {
"command": "faos-mcp"
}
}
}
  1. Completely restart Claude Desktop:
  • macOS: Quit from menu bar (not just close window)
  • Windows: Exit from system tray
  • Linux: pkill -f claude && sleep 2 && claude-desktop
  1. Check Claude logs:
  • macOS: ~/Library/Logs/Claude/
  • Windows: %APPDATA%\Claude\logs\

"Invalid JSON in config"

Symptom: Config file rejected

Common fixes:

Trailing comma (wrong)
{
"servers": {
"faos": {
"command": "faos-mcp",
}
}
}

Remove the trailing comma after "faos-mcp"

Single quotes (wrong)
{
'servers': {
...
}
}

Use double quotes " not single quotes '

Comments (wrong)
{
"servers": {
// This is a comment
"faos": { ... }
}
}

JSON does not support comments - remove them

Correct format
{
"servers": {
"faos": {
"command": "faos-mcp",
"env": {
"FAOS_API_URL": "https://api.faosx.ai",
"FAOS_API_TOKEN": "your-token"
}
}
}
}

Authentication Issues

"Authentication failed" (401)

Symptom: Error 401 when invoking tools

Solutions:

  1. Verify token is valid:
  • Log in to FAOS Portal
  • Go to Settings → API Tokens
  • Check token hasn't expired or been revoked
  1. Regenerate token:
  • In portal: Settings → API Tokens → Generate New Token
  • Update mcp.json with new token
  • Restart Claude Desktop
  1. Check for typos:
  • Ensure no extra spaces in token
  • Verify token is properly quoted
  1. Check API URL:
// Production
"FAOS_API_URL": "https://api.faosx.ai"

// Staging (if applicable)
"FAOS_API_URL": "https://staging-api.faosx.ai"

"Insufficient permissions" (403)

Symptom: Error 403 when using specific tools

Solutions:

  1. Check token scopes:
  • In portal: Settings → API Tokens → View token details
  • Ensure required scopes are enabled
  1. Required scopes by tool:
ToolRequired Scope
faos_invoke_agentagents:invoke
faos_run_workflowworkflows:run
faos_get_contextcontext:read
faos_query_metricmetrics:read
faos_query_graphgraph:read
  1. Generate new token with correct scopes:
  • Delete old token
  • Create new token with all needed scopes
  • Update config and restart

"SSO login loop"

Symptom: Browser keeps asking for login

Solutions:

  1. Clear browser cookies:
  • Clear cookies for your IdP domain
  • Clear cookies for *.faosx.ai
  1. Try incognito/private window:
  • Sometimes extensions interfere
  1. Clear FAOS auth cache:
rm ~/.faos/auth_cache.json
faos-mcp auth clear
  1. Check IdP configuration:
  • Verify redirect URIs in IdP admin
  • Contact your IT admin for SSO issues

Runtime Issues

"Tool not found"

Symptom: Claude says it can't find a specific FAOS tool

Solutions:

  1. Check tool name spelling:
  • Tool names are case-sensitive
  • Use exact names: faos_invoke_agent, not faos-invoke-agent
  1. Verify tools are loaded:

"List all available FAOS tools"

  1. Restart Claude Desktop:
  • New tools may not appear until restart
  1. Check MCP server logs:
# Run manually to see errors
FAOS_API_TOKEN=your_token FAOS_API_URL=https://api.faosx.ai faos-mcp

"Rate limit exceeded" (429)

Symptom: Error 429, requests rejected

Solutions:

  1. Wait and retry:
  • Default: Wait 60 seconds
  • Rate limits reset per minute
  1. Reduce request frequency:
  • Batch related queries
  • Avoid rapid-fire tool calls
  1. Check your plan limits:
  • Free tier: 100 requests/hour
  • Pro tier: 1000 requests/hour
  • Enterprise: Custom limits
  1. Upgrade plan:

"Timeout during workflow" (504)

Symptom: Long-running workflows fail

Solutions:

  1. Use async execution:
Don't: "Run FAOS create-prd workflow and wait for completion"
Do: "Run FAOS create-prd workflow" (returns immediately)
"Check status of workflow wfrun_abc123" (poll later)
  1. Check workflow status separately:

"What's the status of FAOS workflow wfrun_abc123?"

  1. For long workflows, expect async:
  • create-prd: 30-60 minutes
  • create-architecture: 45-90 minutes
  • Always use wait_for_completion: false

"Connection refused"

Symptom: Can't connect to FAOS API

Solutions:

  1. Check internet connectivity:
ping api.faosx.ai
curl https://api.faosx.ai/health
  1. Check firewall/VPN:
  • Corporate VPNs may block external APIs
  • Whitelist *.faosx.ai
  1. Check API URL:
  • Ensure no typos
  • Use HTTPS, not HTTP
  1. Check service status:

Agent-Specific Issues

"Agent not responding" / Slow responses

Solutions:

  1. Try a different agent:

"Use FAOS pm agent instead of auto-routing"

  1. Simplify the task:
  • Break complex tasks into smaller pieces
  • Provide clearer instructions
  1. Check agent availability:

"List available FAOS agents"


"Auto-routing selected wrong agent"

Solutions:

  1. Be explicit about the domain:

"I need HELP WITH ARCHITECTURE for..." (emphasize domain)

  1. Specify agent directly:

"Use the FAOS architect agent to..."

  1. Provide more context:
  • Include relevant keywords
  • Mention the type of output you need

Workflow-Specific Issues

"Workflow stuck at step X"

Solutions:

  1. Check status:

"Get detailed status of FAOS workflow wfrun_abc123"

  1. Wait longer:
  • Some steps take time (research, analysis)
  • Check progress percentage
  1. Cancel and retry:

"Cancel FAOS workflow wfrun_abc123" "Run FAOS [workflow] with [modified inputs]"

  1. Report issue:
  • If stuck for >30 minutes past estimated time
  • Contact support with workflow_run_id

"Workflow output incomplete"

Solutions:

  1. Check if actually complete:
  • Status should be completed, not running
  1. Verify inputs were correct:
  • Missing required inputs cause incomplete outputs
  1. Re-run with better inputs:
  • Add more context
  • Be more specific about requirements

Getting Help

Self-Service

  1. Check this guide for common issues
  2. Search documentation at docs.faosx.ai
  3. Community Discord at discord.gg/faosx

Support Channels

Issue TypeChannelResponse Time
Bug reportsGitHub Issues24-48 hours
Account issuessupport@faosx.ai24 hours
Enterprise supportDedicated Slack channel4 hours
Security issuessecurity@faosx.aiImmediate

Information to Include

When reporting issues:

  1. Environment:

    • OS and version
    • Claude Desktop version
    • faos-mcp version (faos-mcp --version)
    • Python version
  2. Steps to reproduce:

    • Exact prompt used
    • Expected vs actual behavior
  3. Logs:

    • MCP server output (if run manually)
    • Claude Desktop logs
    • Error messages (full text)
  4. Config:

    • Your mcp.json (redact token!)