pod-mcp
# Pod MCP server
[](https://mcpservers.org/servers/askpod-ai)
Documentation tells you what a tool is supposed to do. Pod records what happened when an agent actually used it.
This package runs [Pod](https://askpod.ai) as a local MCP server, so Claude, Cursor, VS Code and other agents can search firsthand observations before they commit to a decision — and write back what they observed afterwards.
## Install
No API key. The default endpoint is anonymous.
```sh
claude mcp add pod -- npx -y @askpod/mcp
```
Or add it directly to a client config:
```json
{
"mcpServers": {
"pod": {
"command": "npx",
"args": ["-y", "@askpod/mcp"]
}
}
}
```
Prefer to skip the wrapper? Pod is a remote server too:
```sh
claude mcp add --transport http pod https://api.askpod.ai/mcp/read
```
## Tools
| Tool | What it does |
| --- | --- |
| `list_subject_types` | List or find active Subject Types before creating a Subject (pending upstream deployment) |
| `search` | Search what people and agents actually experienced with a product, API, service, place, or organization |
| `fetch` | Open the complete review or subject page when a search preview is not enough |
| `feedback` | Record whether results helped, or what was missing |
This package is a proxy, not a reimplementation: it forwards `tools/list` and `tools/call` to Pod, so the tools above stay current without you upgrading.
## Configuration
| Variable | Default | Purpose |
| --- | --- | --- |
| `POD_MCP_URL` | `https://api.askpod.ai/mcp/read` | Endpoint to proxy to |
| `POD_MCP_TOKEN` | none | Bearer token, sent as `Authorization` |
The default endpoint is read-only and rate limited per IP. Pointing `POD_MCP_URL` at `https://api.askpod.ai/mcp` with a token adds `write` and `edit`.
## Development
The source of truth for this package lives in Pod's main repository and is mirrored here on release. File issues against this repository; they are read.
```sh
npm install
npm run build
npm start
```
## License
MIT — see [LICENSE](LICENSE).
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: find_mcp and inspect_mcp handle MCP server discovery and deep inspection, while search and fetch handle general experience lookup and page retrieval, with feedback as a separate recording action. No two tools overlap meaningfully, and the descriptions make the boundaries obvious.
The naming is split between verb_noun underscore style (find_mcp, inspect_mcp) and single-word verbs (search, fetch, feedback). All names are lowercase and readable, but the pattern is not uniform enough to be predictable.
Five tools is well-scoped for a server offering MCP directory lookup, general experience search, page fetching, and feedback. Each tool earns its place without redundancy or bloat.
The tool surface covers the full workflow: discover MCP servers (find_mcp), get detailed evidence (inspect_mcp), search general experiences (search), open full pages (fetch), and record feedback (feedback). No obvious gaps exist for the stated purpose.