20 tools, the full surface
| Tool | What it does |
|---|---|
| quote | Price a search or catch before running it |
| search | One-off search across the sources you name |
| capture | Fetch one post or page with thread context |
| classify | Classify results against caller-defined criteria |
| create_catch | Register a standing query with a destination |
| list_catches | List catches with their status |
| get_catch | Read one catch, including its last run |
| update_catch | Change query, sources, interval, or destination |
| pause_catch | Pause a running catch |
| resume_catch | Resume a paused catch |
| delete_catch | Remove a catch and stop its firings |
| test_catch | Fire the destination with a sample payload |
| get_results | Read results delivered by a catch so far |
| get_events | Read the account event log from a cursor |
| create_subscription | Route filtered events to a target |
| list_subscriptions | List subscriptions with delivery health |
| delete_subscription | Remove a subscription |
| doctor | The orientation manifest: where to start, prices, sources |
| list_sources | Sources live now and whether deep coverage is possible |
| get_usage | Units consumed this period, by kind, with spend |
Connect from any MCP client
The server URL is the same for every client. Add it, approve the OAuth prompt, and the tools appear. Auth discovery is at mcp.discatch.com/.well-known/oauth-protected-resource.
Claude Code (.claude/mcp.json)
{
"mcpServers": {
"discatch": { "url": "https://mcp.discatch.com" }
}
}Codex
{
"mcpServers": {
"discatch": { "url": "https://mcp.discatch.com" }
}
}Cursor (.cursor/mcp.json)
{
"mcpServers": {
"discatch": { "url": "https://mcp.discatch.com" }
}
}VS Code (.vscode/settings.json)
{
"mcp": {
"servers": {
"discatch": { "url": "https://mcp.discatch.com" }
}
}
}MCP pulls, catches push
MCP is a request and a response. A server cannot start a conversation. Products in this category that ship only MCP leave the agent polling; some say so in their own docs. discatch treats the MCP server as the read and control surface. Delivery is a separate feature: a catch has a destination, and the destination wakes the agent when the catch fires.
An agent that registers a catch from MCP and gives it a webhook destination gets both: control through the session, delivery through the push. The MCP tools let you create the catch, set the query, pick the sources, choose the interval, and point it at a destination. The destination does the waking.
Scoped keys
Keys are scoped: read, search, catches:write, billing:read. The OAuth flow asks for the scopes it needs and nothing else. An agent that only searches never gets catches:write. An agent that manages billing never gets search.
Resources and prompts
- Resource: discatch://catches/{id}/results for streaming reads where the client supports it.
- Prompt: write-reply drafts a reply that matches how the user writes, for the user to post. discatch never posts.
- Prompt: daily-digest summarizes what a catch found in the last 24 hours.