Skip to main content

Documentation Index

Fetch the complete documentation index at: https://developer.affinity.co/llms.txt

Use this file to discover all available pages before exploring further.

​
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

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.
  • Confirm you copied the full key, including any trailing characters.
  • Confirm the Authorization header uses the exact format Bearer <your-key> (one space, no quotes around the value).
  • In Affinity → Settings → Manage Apps, verify the key hasn’t been rotated or revoked.
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.
Cause: The MCP server may have crashed or failed to start.Fix: Check the logs for startup errors.
  • Refresh / restart the AI client (some clients only refresh the tool list on startup).
  • In the client, verify the MCP server status is “connected” or “healthy”.
  • For Copilot CLI, run /mcp show. For Claude Code, run /mcp.
Most common cause: your Affinity admin has disabled the AI client you’re connecting from, or your plan doesn’t include MCP access.
  • In Affinity, go to Settings → Affinity MCP and confirm your client is enabled.
  • Confirm your plan is Scale, Advanced, or Enterprise.
  • Affinity may not support OAuth for the AI client you’re using. Check Supported Clients to see which auth methods are available for your client, and use API key auth if OAuth isn’t supported.
  • If all of the above check out, disconnect the AI client and re-authenticate from scratch.
MCP tool calls run with your Affinity user’s permissions. If you can’t read a list or create a note in Affinity directly, MCP can’t either. Ask your admin to grant the needed list / role access.
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. 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. 
npx @modelcontextprotocol/inspector uvx affinity-mcp
Set the AFFINITY_API_KEY environment variable before running, or pass it inline:
AFFINITY_API_KEY=your_api_key_here npx @modelcontextprotocol/inspector uvx affinity-mcp