Skip to main content
PodData’s MCP server gives an assistant PodData’s tools: every read route has one, and so does each change a diligence needs. It’s at:
It speaks Streamable HTTP: one JSON answer to each POST, no sessions. Each tool calls the API’s own route as you, so it keeps the same checks, limits, counts and error messages, and answers twice: as text an assistant can read, and as the route’s JSON.
This is PodData’s server, with PodData’s data. A docs site’s own “add to your assistant” button adds a server that searches these pages; it isn’t this one.

Add it with a key

  1. Keep the key in the environment as PODDATA_API_KEY.
  2. In the project’s folder, run this as it is, in single quotes, so Claude Code reads the key from the environment each time it starts and never writes it down:
  3. Start Claude Code again. /mcp lists poddata with its tools.
Any other client that speaks MCP over Streamable HTTP takes the same address and the same header.

Add it by signing in

With no key, the server asks the client to sign in, and the person signs in to PodData and picks their team.
  1. Add it without a header:
  2. In Claude Code, run /mcp, pick poddata and sign in. PodData’s sign-in opens in the browser.
  3. The sign-in asks for two scopes: quotes:read, for every tool that reads, and trackers:write, for every tool that changes something, such as confirming a link or saving a report’s page. Without trackers:write, those tools aren’t listed.
A sign-in works for an hour and renews itself for 30 days. Only a team whose plan includes the API can sign in.

When a tool is refused

A refusal comes back as the tool’s answer, marked as an error, with the API’s own sentence: a limit, a company that isn’t a target yet, a link confirmed for another company. Read it and do what it says. A call past the key’s requests a minute waits, as the API’s does: see Keys and limits.

Its tools

106 tools, in the order the server lists them. A tool that changes something needs the trackers:write scope when you sign in; with a key, every tool is there. Each operation in the API reference names its tool too, so you can go from a route to its tool and back.