Connect your AI assistant

Connect Codex, Claude or Cursor to your Acquisity campaigns, leads and results.

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

Before you connect

1. Choose the workspace you want your assistant to use. Public API access must be enabled for it.
2. Create an API key. Start with workspaces:read and campaigns:read to view campaigns and results. Add campaignLeads:read to view individual leads.
3. Choose your setup guide above. Add the key in the client's configuration, never in a chat message.

A workspace key works in one workspace and is required for campaign changes. A personal token can read campaigns across your eligible workspaces, but cannot create, launch or pause campaigns. 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 choose one:

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

The assistant uses list_workspaces and list_campaigns. If you have more than one workspace, name the workspace or include its ID each time. Your key's permissions determine which requests can succeed.

Connection details

This connection uses an API key, not an OAuth sign-in. A client must support a custom Authorization header. Choose the guide for the app you actually use. Codex connects directly; Claude Desktop uses a local helper. Claude web and Cowork do not use these local desktop settings. A setup screen that only offers OAuth needs a different connection method.

The URL is for your MCP client. Opening it as a webpage is not a connection test: authenticated GET requests receive 405 Method Not Allowed because the server handles MCP requests over POST.