Skip to main content

​
Viewing server logs

If the server isn’t working as expected, check the logs first.
Logs are written per session to ~/.claude/debug/. The latest symlink always points to the most recent session:
tail -n 50 -F ~/.claude/debug/latest

​
Common issues

​
”Authentication failed” or 401 errors

Cause: The AFFINITY_API_KEY is missing, invalid, or has extra spaces or quotes around it. Fix: Double-check the environment variable value in your client config. The key should be a plain string with no surrounding quotes or whitespace.

​
”Connection refused” or timeout errors

Cause: The server cannot reach api.affinity.co. Fix:
  • Check your internet connection
  • If you’re on a corporate VPN, ensure it allows traffic to Affinity’s API

​
”Tool not found” errors

Cause: The MCP server may have crashed or failed to start. Fix: Check the logs for startup errors.

​
get_meetings returns an access error

Cause: Your organization hasn’t been onboarded to Affinity’s unified events feature, which is required for the meetings API. Fix: Contact your Affinity CSM to request access.

​
Debugging with MCP Inspector

You can use the MCP Inspector to test tools and debug the server interactively in your browser. 
npx @modelcontextprotocol/inspector uvx affinity-mcp
The inspector lets you list available tools, call them with custom arguments, and inspect responses — useful for verifying the server is working before connecting a full AI client.