MCP server

The MCP server lets an AI assistant (Claude, Cursor, and any client that speaks the Model Context Protocol) read your radars and newsletters and set them up, in conversation. It is at https://app.trymarketradar.com/api/mcp, over Streamable HTTP. An assistant connects in one of two ways:

• By signing in, for Claude.ai and ChatGPT: you give it the URL, it sends you to Market Radar, you sign in, pick the workspace and allow. It then acts with your rights: it reads, and it can add companies, create radars and change newsletters.
• With a key, for clients that take a header (Claude Code, Cursor, Claude Desktop): the URL and a key in the same header as the API. A read key shows the assistant the read tools only; give it a read and write key only if you want it to add companies, create radars and change newsletters.

The MCP server and the API share one rate limit: 60 requests a minute per key, or per assistant signed in. Each tool call is one request; past the limit, the tool answers with an error that says how many seconds to wait.

The tools hold to the account's plan as the API does: a radar, company or custom source past what the plan counts this month is refused with a sentence that says what is over, by how many, and when places free up, such as 2 companies over: the plan counts 40 companies a month, and 40 are used since 1 October. Places free up on 1 November. What a plan leaves to Scale is refused as a Scale feature.

ConnectingCopy Anchor Link

Claude.ai: Settings, Connectors, Add custom connector, with the URL above. Claude opens Market Radar's sign-in; sign in, choose the workspace, and allow. On a Team or Enterprise plan, an owner adds the connector once, under the organization's settings, and each member then connects it.

ChatGPT: add a custom app (a connector) with the URL above, in ChatGPT's settings. The same sign-in follows.

Claude Code:

claude mcp add --transport http market-radar https://app.trymarketradar.com/api/mcp \
  --header "Authorization: Bearer <your key>"

Cursor, in ~/.cursor/mcp.json:

{
  "mcpServers": {
    "market-radar": {
      "url": "https://app.trymarketradar.com/api/mcp",
      "headers": { "Authorization": "Bearer <your key>" }
    }
  }
}

Claude Desktop, in claude_desktop_config.json, through the mcp-remote bridge (Node.js needed). The header is passed through env, without a space after the colon, so that no shell splits it:

{
  "mcpServers": {
    "market-radar": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://app.trymarketradar.com/api/mcp", "--header", "Authorization:${MARKET_RADAR_AUTH}"],
      "env": { "MARKET_RADAR_AUTH": "Bearer <your key>" }
    }
  }
}

Other clients: the URL, and either Authorization: Bearer <your key> as a header or the sign-in, which follows the MCP specification's authorization (OAuth 2.1, with client ID metadata documents). A client signing in asks for the scopes the server's 401 names: profile email user:org:read market_radar:mcp. A token without market_radar:mcp is refused with 403 and error="insufficient_scope"; sign in again.

To disconnect an assistant signed in this way, remove it in the assistant.

ToolsCopy Anchor Link

create_radar builds the query the way the app places chips:

It needs company_ids, group_ids or own_words, and a folder, as POST /radars does, and reads the open web unless sources says otherwise. Each of own_words is a text chip: a sentence, read, the AI proposing its terms; or { "text": "…", "terms": ["…"] }, the sentence with 1 to 3 terms of your own, searched as given. list_filters shows each own filter's terms and what it keeps. create_tender_radar takes countries as ISO 3166 alpha-3 codes, words to watch for and exclude words that drop a call, as POST /radars with type tenders does, create_exchange_rate_radar takes pairs and interest_rates as type rates does, and create_commodity_price_radar takes commodities as type commodity_prices does. Each takes folder_id, one of the account's folders from list_folders or one create_folder made, or folder_name to make one with the radar. update_group's member_ids replaces the whole list, as PATCH /groups/{id} does. delete_group deletes the group's companies or custom sources with it, as the app does; to delete the group alone, empty it with update_group first. delete_folder deletes the folder's radars with it, as DELETE /folders/{id} does. The server has no tool to edit or delete a radar or a company, or to move a radar out of a folder: do that in the app or through the REST API.

The newsletter tools follow the newsletter endpoints. A few differences suit an assistant:

• get_issue without issue_id reads the issue on its way: the one to approve.
• get_newsletter lists each block of the template with its id, so the assistant can name one to update_block, move_block or delete_block. add_block and update_block take every type's fields as arguments; a field the block's type has not is refused, naming it. A text block takes text, plain.
• delete_newsletter and delete_block are marked destructive, so an assistant asks you before it calls them. The server has no tool to remove a recipient: do that in the app or through the REST API.
• Live is turned on and off in the app only.

Every tool answers with structured JSON (the objects) and a short text an assistant can quote. Examples of what to ask:

• What happened at our competitors this week? (list_signals with since)
• Summarise the M&A signals on Competitors and AI since September.
• Add Revolut, revolut.com, and create a radar for its product launches and partnerships.
• Which calls for tender on solar carports close this month? (list_tenders with status open)
• How has the euro moved against the dollar and the yuan since July? (get_rates with since)
• How have nickel and cobalt moved this quarter? (get_prices)
• What goes out in Monday's brief? Approve it without the second item. (get_issue, remove_from_issue, approve_issue)
• Add a Calls for tender section to the weekly newsletter, after Competitors. (add_block)