Connect Cursor

Add Acquisity to Cursor and use campaign tools from Agent.

1. Create a key

Create a workspace API key with workspaces:read and campaigns:read. Add campaignLeads:read if you want to inspect individual leads.

Start with read-only permissions. Add campaigns:write only when you want the assistant to change campaigns, including launching or pausing live outreach.

2. Add Acquisity to your MCP configuration

Open your user-level Cursor MCP configuration at ~/.cursor/mcp.json. Add the following entry inside mcpServers, preserving any servers you already have. Replace YOUR_ACQUISITY_API_KEY with your complete key:

{
  "mcpServers": {
    "acquisity": {
      "url": "https://api.acquisity.ai/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_ACQUISITY_API_KEY"
      }
    }
  }
}

Keep this file private. Do not put a real key in a shared project's .cursor/mcp.json or commit it to Git.

If you prefer environment variables, Cursor supports "Authorization": "Bearer ${env:ACQUISITY_API_KEY}". The variable must be available to the Cursor process when it starts; setting it in an unrelated terminal after Cursor is open is not enough.

3. Check the server in Cursor

Save the file, open Cursor's MCP settings from Customize, and check that acquisity is enabled and its tools load. Reload Cursor if the new configuration has not appeared. This is an API-key connection, so do not choose an OAuth sign-in flow.

4. Try it in Agent

Use Acquisity to list my available workspaces. Ask me which workspace to use, then show its campaigns and statuses. Do not change anything.

Choose a workspace when asked. Review any tool-approval prompt in Cursor before allowing it. Approval prompts are a client feature; your API key's scopes are what enforce access on Acquisity's side.

Browse the tools, try more prompts, or fix a connection error.

Disconnect or replace the key

Remove the acquisity entry from your MCP configuration to remove this connection. To stop the credential working in any client, revoke it in Acquisity. Neither action undoes earlier changes or pauses a live campaign.

Client configuration reference: Cursor MCP documentation.