MCP setup

The remote MCP server with OAuth is planned for roadmap phase 3. This page lists the tools it will expose and the client configs to paste when it ships.

Auth

OAuth 2.1 with PKCE. Discovery at /.well-known/oauth-protected-resource. No API key to paste. Every plan gets access when the server ships.

Tool list

Tool	Purpose	Units consumed
quote	Price a search or catch before running it	none
search	One-off search across sources	search, result
capture	Fetch one post or page with thread context	capture
classify	Classify results against caller criteria	classify
create_catch	Register a standing query and destination	alert on each firing
list_catches	List catches with status	none
get_catch	Read one catch, including last run	none
update_catch	Change query, sources, interval, destination	none
pause_catch	Pause a catch	none
resume_catch	Resume a paused catch	none
delete_catch	Delete a catch	none
test_catch	Fire the destination with a sample payload	none
get_results	Results delivered by a catch	none
get_events	Read the event log from a cursor	none
create_subscription	Route events to a target	none
list_subscriptions	List subscriptions with delivery health	none
delete_subscription	Remove a subscription	none
doctor	The orientation manifest	none
list_sources	Sources and current availability	none
get_usage	Units consumed this period	none

Resources: discatch://catches/{id}/results for streaming reads where the client supports it. Prompts: write-reply (draft a reply in the user’s voice), daily-digest (summarize a catch’s last 24 hours).

Client setup

Claude Code

.claude/settings.json

{
  "mcpServers": {
    "discatch": {
      "url": "https://mcp.discatch.com"
    }
  }
}

Codex

codex config

{
  "mcpServers": {
    "discatch": {
      "url": "https://mcp.discatch.com"
    }
  }
}

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "discatch": {
      "url": "https://mcp.discatch.com"
    }
  }
}

VS Code

.vscode/mcp.json

{
  "servers": {
    "discatch": {
      "url": "https://mcp.discatch.com"
    }
  }
}

MCP is pull-only

MCP is pull by spec. The agent calls tools; the server does not push. That is why discatch ships push separately. A catch calls your destination when it fires. The MCP server and push are complementary, not alternatives.

Until the server ships

The REST API with a trial key does everything the MCP server will do. POST /v1/keys/trial returns a key with no email and no card. The agent makes the same calls over HTTP.

Last reviewed 2026-09-10 by Parsa Khazaeepoul, founder, dcouple. Copy from docs/onboarding.md, docs/query-language.md, docs/events.md, docs/api.md.