Competiscan
Get help with the Competiscan MCP server — the Model Context Protocol interface that exposes Competiscan’s direct mail archive as tools to Claude and other MCP clients.
mcp@ai.competiscan.com reaches the team that runs this service, for anything technical: connecting a client, authentication errors, rate limits, or a tool call that isn’t behaving as documented.
For account, billing, or general Competiscan questions, contact contactus@competiscan.com.
Every call to the MCP server returns an x-request-id
response header. Pasting it into your email is the fastest way for us
to find the exact call in our logs.
Sign in to your account at mcp.competiscan.com/portal/login to see your usage against your quota, your recent calls, and the last four characters of your current API key. From there you can generate a new key or rotate an existing one at any time — no support ticket required.
If you were invited by email and don’t have a password yet, use the temporary password from your invitation and you’ll be prompted to set a permanent one on first sign-in. Lost the invitation, or locked out? Email mcp@ai.competiscan.com and we can resend it.
In Claude, open Settings → Connectors, search for “Competiscan,” and sign in with your Competiscan account to add it. The same account works whether you connect through Claude, another MCP client, or the account portal.
| Symptom | Likely cause | What to do |
|---|---|---|
401 missing_credentials / invalid_api_key |
No key sent, or the key was revoked or rotated | Check the X-API-Key header, or generate a fresh key from the portal |
403 account_not_provisioned |
Your sign-in is valid but not yet linked to a Competiscan account | Email mcp@ai.competiscan.com to get linked |
429 rate_limit_exceeded / quota_exceeded |
Too many calls too fast, or the monthly quota is used up | Check current usage on your dashboard; the response names when you can retry |
| Can’t find “Competiscan” in Connectors | Not yet signed in with a linked account | Sign in with the email your invitation was sent to |
Full documentation covers authentication, how to connect a client, and every tool argument in detail. It’s the authority on how a query should behave; this page is for when something doesn’t.