Fix a connection
Resolve MCP authentication, workspace, permission and operation errors.
The client does not offer sign-in
Check that the server URL is exactly https://api.acquisity.ai/mcp and remove any custom Authorization header. Codex and Claude discover Acquisity sign-in from that URL.
In Codex CLI, run codex mcp login acquisity. In Claude Code, open /mcp, select Acquisity and authenticate. In Claude web, Desktop or Cowork, add Acquisity as a custom connector rather than a local extension.
Older clients without OAuth support can use a manually created API key. Follow the dedicated Cursor instructions or your client's custom-header documentation.
The server is missing or disconnected
- Check the URL is exactly
https://api.acquisity.ai/mcp. - Complete the browser sign-in and return to the client.
- Reload the client's MCP configuration, then check its server status. In Claude Code, use
claude mcp listor/mcp. - If your organisation manages connectors, ask an administrator whether Acquisity must be approved.
Do not use a separate /sse URL. The connection uses Streamable HTTP at /mcp.
I get 401 Unauthorized
The sign-in token is missing, expired or revoked. Disconnect Acquisity, connect it again and complete browser approval. If the connection was revoked from Acquisity, a new sign-in is required.
For a static API-key setup, verify the key is active and unexpired, copy the whole value including acq_org_ or acq_live_, and do not add quotes inside the header value. If needed, create a replacement key.
I get 403 Forbidden
Check whether the connection was approved as Read-only or Full. Reconnect and choose Full when changes are intended. Webhook creation also requires the connecting user to be a workspace owner or admin.
Full access never grants payment tools, workspace-settings changes or workspace-knowledge updates. For a static key, check the required scope in the tool list.
My workspace or campaign is missing
Call list_workspaces and use the returned ID. A signed-in connection can access only the workspace selected during approval. To use another workspace, disconnect and sign in again.
If the connecting user was removed from the workspace or changed to the client role, the connection can no longer access it.
Check that the campaign belongs to the chosen workspace. A missing or inaccessible resource can return 404; do not assume the token can access a resource just because you know its ID.
The CRM tools are missing
CRM tools are available in every workspace, subject to connection permissions. A signed-in connection can use them with Read-only or Full access. A static-key connection must use a workspace API key; personal access tokens never receive the CRM catalogue.
If connection permissions changed after the client connected, reconnect or refresh the client's tool list.
An update says precondition_failed
Another change may have happened since your last read. Call get_campaign again and use its current updatedAt as the update's ifMatch value. Review the current state before retrying rather than repeatedly sending a stale update.
A sequence says failed_precondition
AI-generated sequences require the workspace's cold-email and niche-research setup; the direct method also requires its own setup fields. Follow the error's named missing prerequisite. Attaching a sequence also requires a draft without an existing sequence; use the app for individual step edits.
The tool timed out or is still running
A tool waits only briefly for background work. Keep the returned operation ID and call get_operation to check progress. A timeout does not prove that the original change failed or never started.
If a paid search needs retrying, reuse its original idempotencyKey and the same arguments. A new key may start another billed search. Operation states.
The search succeeded, but I cannot see the leads
For search_campaign_leads, success means the search was dispatched. Scraping and attachment can continue for several minutes. Check list_campaign_leads afterward.
For search_leads, the completed operation returns a download link after search and verification finish. Check expiresAt and download before the link expires.
I get 429 Too Many Requests
Wait before retrying and respect any returned retry guidance. A single MCP tool can make several API requests, including operation checks, so repeated polling consumes quota. Rate limits.
What should I send support?
Include the client name/version, the step that failed, the tool name, the error text and a request or operation ID when available. Remove keys and private values from screenshots. Never send your full API key.