Documentation / MCP / Connect an AI Agent

Connect an AI Agent

POSThttps://mcp.oppalerts.com/mcp

Connect Claude Code, Codex, or another AI agent to the OppAlerts MCP server.

What the MCP server is

The OppAlerts MCP server lets an AI agent, such as Claude Code or Codex, call OppAlerts tools. Every tool uses the same URL: https://mcp.oppalerts.com/mcp. The request includes the tool name.

Connect Claude Code

claude mcp add --transport http oppalerts https://mcp.oppalerts.com/mcp

The first call opens a browser window for the OppAlerts login. The server uses OAuth 2.0 with PKCE from https://auth.oppalerts.com.

Planned video. Connect Claude Code to OppAlerts, from the claude mcp add command to the first tool call.
Source: a new screen recording.
File: img/docs/mcp/connect.mp4
Connect Claude Code to the OppAlerts MCP server.

How a call looks

An MCP call is a JSON-RPC request to POST https://mcp.oppalerts.com/mcp with the token in the Authorization: Bearer header.

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "account_calls_left",
    "arguments": {}
  }
}

Rules for every call

  • Authentication. Every call needs a token in the Authorization: Bearer header: a personal token or an OAuth access token. The MCP server needs the scope mcp:use. A tool that changes data also needs api:write. A missing or invalid token returns HTTP 401 unauthorized. See Authentication.
  • Daily limits. The 14 news_ and prospects_ tools are index searches. All index searches for an account share one daily count. Every other tool has a daily count of its own. Team members use the account’s counts. The counts reset every day at 04:00 New York time. account_calls_left shows the calls left today. A call over a count is refused with daily_limit (HTTP 429 in the API).
  • What counts. Each tool call through the API or MCP uses one call from its daily count. A refused call with an HTTP status from 400 to 499 uses no daily call. Two responses are not refusals and use one call: a search stopped by the index (HTTP 422), and a server error (HTTP 500 to 599). The MCP messages initialize, tools/list, and ping are not tool calls and use no daily call. Calls from web app pages use the same counts, except when one of these 12 tools reads data from your own account: campaigns_list, campaigns_settings, campaigns_organizations, campaigns_saved_opportunities, campaigns_dashboard, account_usage, account_team_members, account_calls_left, llm_answers_content_phrases, llm_answers_search_keywords, llm_answers_top_sites, and taxonomy_taxonomies.
  • One search at a time. Only one index search runs at a time for each account. A call to a news_ or prospects_ tool made while another index search runs is refused with one_at_a_time (HTTP 429 in the API) and uses no daily call. Wait a few seconds and send it again.
  • One change at a time. Only one change runs at a time for each account. A call to one of the 16 tools that change data, made while another change is running for the account, is refused with one_at_a_time (HTTP 429 in the API) and uses no daily call. Send it again after a few seconds. The 16 tools: campaigns_create, campaigns_update, campaigns_finalize, campaigns_archive, campaigns_activate, campaigns_rerun_research, campaigns_rebuild_counts, campaigns_set_taxonomy_presets, campaigns_set_daily_opportunities_email, campaigns_organization_add, campaigns_organization_update, campaigns_organization_delete, campaigns_saved_opportunity_add, campaigns_saved_opportunity_update, campaigns_saved_opportunity_archive, and campaigns_saved_opportunity_activate.
  • Request log. Each tool call with a valid token is written to the account’s request log: the time, the source, the token, the tool, the HTTP status, and whether it used a daily call. Refused calls are also logged. The MCP messages initialize, tools/list, and ping are in the log with counted false. A call of account_calls_left through the API or MCP is never logged. account_usage and the Usage page of the web app show the log for the last 14 days.

The API page lists the daily counts of each plan.

Errors

A refused tool call returns a normal JSON-RPC response with "isError": true. Its text starts with the error code, the same code that the API returns, then a colon and one sentence:

{
  "content": [
    {"type": "text", "text": "no_campaign: That campaign is not in this account."}
  ],
  "isError": true
}

The API page lists the error codes that many tools share. Each tool’s page lists its error codes.

One type of refusal is not a tool result. When the token does not have a scope that the call needs, the server returns HTTP status 403, as the MCP standard requires. The response has a WWW-Authenticate header with error="insufficient_scope" and the scopes that the call needs. An MCP app that reads this header asks you for those permissions. An example: a tool that changes a campaign, called by an app that can only read. The response body has the error code forbidden and one sentence.

All tools

The server has 50 tools, in 10 groups. Each tool has an MCP page and an API page.

Account (3)

Backlinks (2)

Campaigns (21)

Link Graph (1)

LLM Answers (3)

News Index (7)

Prospect Index (7)

Site Info (1)

Taxonomies (3)

Types (2)