Skip to main content

Set up the Affinity MCP server

Affinity's remote MCP server gives AI agents read and write access to your CRM: people, companies, opportunities, lists and saved views, notes, meetings, reminders, and relationship strength. This guide covers checking your plan and permissions in Affinity, installing the server from MintMCP's recommended servers, and connecting each user with their own Affinity API key, so every tool call runs under that user's Affinity permissions.

Prerequisites​

  • A MintMCP admin account
  • An Affinity plan that includes MCP access. Affinity lists the eligible plans in its MCP documentation
  • Each connecting user needs the Generate API Key permission in Affinity, which most users have by default. If your workspace uses Affinity roles, their role also needs Manage MCP Agents (see Check plan and permissions in Affinity)

Check plan and permissions in Affinity​

An Affinity admin confirms the workspace can use MCP before users connect:

  1. In Affinity, go to Settings > Billing Settings and confirm the workspace is on a plan that includes MCP access. Affinity keeps the list of eligible plans in its MCP documentation.
  2. If your workspace uses Affinity roles, go to Settings > Users and Permissions > Roles and turn on Manage MCP Agents for each role whose members will connect through MintMCP.

The Settings > Affinity MCP page governs OAuth-based clients such as Claude and ChatGPT and does not list MintMCP. Access through API keys is audited and revoked under Settings > Manage Apps instead.

Create an Affinity API key​

Affinity allows one active API key per user, and creating a new key revokes the existing one. A user who already runs a personal integration on their current key should expect that integration to stop working once they create a key for MintMCP.

Each user who connects to Affinity through MintMCP creates their own key:

  1. In Affinity, go to Settings > Manage Apps.
  2. Click + New App.
  3. Enter a Name (for example, MintMCP) and an optional Description.
  4. Click Add App.
  5. Copy the secret. Affinity shows it only once.
  6. Click Done.

Paste the key when MintMCP prompts for a bearer token. MintMCP sends it as the bearer token on every call that user makes.

Add Affinity to MintMCP​

  1. In MintMCP, go to MCP store and open the Recommended servers tab.
  2. Select Affinity to open the configuration panel. The server URL, the Bearer Token authorization method, and the Per-user credentials connection type are pre-set from the catalog.
  3. Click Install.

Each user then creates their own API key and supplies it when MintMCP prompts for a bearer token on first connect.

What the connector exposes​

Affinity maintains the list of tools its MCP server exposes, and the list changes as Affinity ships new capabilities, so check the available tools reference in Affinity's developer documentation for the current set and for which tools write. Some tools depend on Affinity features being enabled for your workspace, such as the Deal Assist add-on for note and file search and unified-events onboarding for meeting tools, and the same reference lists those dependencies.

An Affinity API key carries the user's full Affinity permissions and has no per-tool scopes, so what an agent can do is bounded by what that user can already do in Affinity.

Security considerations​

  • Every call runs as the signed-in Affinity user, so list access, field-level visibility, and role gates apply unchanged, and MintMCP's audit log attributes each tool call to that user.
  • An API key is long-lived and shown once. Rotate or revoke it under Settings > Manage Apps; Affinity revokes a user's key automatically when that user is deactivated.
  • Keys have no read-only variant, so use tool customization to hide the write and delete tools for roles that should only read. Affinity's available tools reference marks which tools write.
  • Affinity's server is a stateless proxy that keeps no CRM data or prompts.
  • Shared credentials are not recommended, because a single key would run every user as the key's owner and drop per-user attribution.

Troubleshooting​

  • 401 or authentication failed: the key is wrong, was revoked, or was replaced by a newer key for the same user; the workspace plan lacks MCP access; or the user's Affinity role lacks Manage MCP Agents. Create a new key under Settings > Manage Apps and reconnect.
  • Permission errors on specific lists or fields: the user lacks that access in Affinity itself. A key never grants more than the user already has.
  • Meeting tools return an access error: the workspace is not onboarded to unified events. Contact your Affinity customer success manager.
  • Note or file search is unavailable: those tools require the Deal Assist add-on.
  • 429 rate limit errors: Affinity applies a per-user request rate limit and, on some plans, a monthly organization-wide API allowance, and MCP calls count against both. Agents that page through every company can use up the monthly allowance. Affinity publishes the current values in its rate limits documentation.

Next steps​