Fix a connection

Resolve MCP authentication, workspace, permission and operation errors.

The client asks me to sign in with OAuth

Acquisity's MCP endpoint uses a static bearer key, not OAuth. Choose Streamable HTTP and configure Authorization: Bearer YOUR_API_KEY. A registration or OAuth request can return 404 because those routes are not provided by this connection.

For desktop apps, use the Codex desktop or Claude Desktop guide. Claude Desktop uses a local helper; its web connector form is a different setup.

Use the dedicated Claude Code or Cursor instructions. A setup screen that only accepts an OAuth sign-in is not the same connection method.

The server is missing or disconnected

• Check the URL is exactly https://api.acquisity.ai/mcp.
• Confirm the header name is Authorization and its value starts with Bearer followed by the complete key.
• If you use an environment variable, confirm it is available to the client process when it starts.
• Reload the client's MCP configuration, then check its server status. In Claude Code, use claude mcp list or /mcp.

Do not test the connection by opening the URL in your browser. The server accepts MCP over POST; authenticated GET and DELETE requests return 405 Method Not Allowed. It does not provide a separate /sse URL.

I get 401 Unauthorized

The key is missing, expired, revoked or incorrect. Copy the whole value, including acq_org_ or acq_live_. Do not add quotes inside the header value. If necessary, create a replacement key and update the client.

I get 403 Forbidden

Check the required scope in the tool list and confirm Public API access is enabled for the workspace. For campaign changes and lead-search tools, use a workspace key; adding write scopes to a personal token does not bypass this requirement.

My workspace or campaign is missing

Call list_workspaces and use an ID from that response. A workspace key can access only its own workspace. Personal tokens follow the user's membership and Public API availability.

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.

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.