Connect your AI assistant

Connect Codex, Claude or Cursor to Acquisity campaigns and supported CRM records.

Connect your assistant to Acquisity so you can ask it to check campaign results, prepare drafts, find leads and work with supported CRM records in plain English. MCP is the connection that gives your assistant access to these tools.

Before you connect

1. Make sure you are a workspace owner, admin or member. Client-role users cannot create an assistant connection.
2. Decide whether the assistant should have Read-only or Full access.
3. Follow the guide for your client. The sign-in page asks you to choose one workspace or All my workspaces, and an access level, before approving the connection.

You do not need to create or paste an API key for Codex or Claude. The connection follows your current workspace membership. Removing your membership, disconnecting the app or reconnecting with a different access level updates what the assistant can do.

CRM tools are available in every workspace, subject to connection permissions. Clients without OAuth support can use a static API key instead. Choose permissions.

Make your first request

Once your client shows Acquisity as connected, ask:

List the Acquisity workspaces I can access. Show their names and IDs. Do not change anything.

Then ask:

In workspace [workspace ID], list my campaigns and their statuses. Do not create, update or launch anything.

A signed-in connection returns the workspace selected during approval, or every workspace where you're an owner, admin or member if you chose All my workspaces. To change the choice or the access level, reconnect Acquisity and make a new selection.

For a signed-in connection or workspace key with CRM permissions, you can instead ask:

In workspace [workspace ID], find people or companies matching Acme. Do not change anything.

The assistant uses search_crm. CRM tools are available in every workspace within the connection’s permissions.

Connection details

For OAuth-capable clients, add the URL without a custom Authorization header; they discover the Acquisity sign-in page automatically. For clients such as Cursor that require a static bearer credential, follow the client-specific guide and configure a manually created acq_org_… or acq_live_… API key.