Troubleshoot MCP server

Before you start

The Attune AI MCP server provides tool handlers, prompts, and resources for Model Context Protocol clients like Claude Code. Common issues include server startup failures, tool call timeouts, and authentication problems.

Symptom table

If you observe Check
Server won't start or exits immediately Process logs and .mcp.json configuration
Tool calls timeout or hang Rate limiter state and tool handler exceptions
Authentication errors User ID setup and workspace root permissions
Missing tools in client Tool schema registration and server handshake
Memory operations fail Memory module installation and database access

Step-by-step diagnosis

  1. Verify server startup Test the server directly: uv run python -m attune.mcp.server Check for import errors, missing dependencies, or configuration issues.

  2. Check MCP configuration Ensure .mcp.json exists in your project root with correct command syntax:

    {
      "mcpServers": {
        "attune": {
          "command": "uv",
          "args": ["run", "--from", "attune-ai", "python", "-m", "attune.mcp.server"]
        }
      }
    }
    
  3. Test tool registration Call EmpathyMCPServer().get_tool_list() to verify tools are properly registered. Missing tools indicate schema loading failures or import problems.

  4. Examine rate limiting The RateLimiter (60 calls per 60 seconds) may be blocking requests. Check recent call patterns and consider if you've exceeded limits.

  5. Validate workspace setup Confirm the server can access your workspace root and has proper file permissions. Memory tools require write access to store session data.

Common fixes

Source files

Tags: mcp, tools, server