Skip to content

MCP overview

EchoSift’s MCP server exposes 8 read-only tools over HTTP. It is designed for AI agents that need real developer-pain data to reason about build decisions, validate ideas, and write briefs grounded in evidence.

Streamable HTTP at https://mcp.echosift.io/mcp.

The server does not support stdio. For local development, run the MCP server binary against a local ApiService instance (see the McpServer README).

Two modes:

Mode When to use
OAuth 2.1 PKCE Recommended. Browser flow on first connect; token auto-refreshed.
Bearer API key (es_*) Fallback for clients without OAuth. Create keys at Settings > Integrations.

Both modes require a Pro subscription.

60 requests per minute per authenticated user.

Every tool carries readOnlyHint: true. The server never mutates state, never triggers brief generation, and never consumes quota.

  • Developer pain evidence: real quotes, post metadata, and source permalinks from GitHub, Stack Overflow, and Hacker News.
  • Signal metrics: score, volume, growth rate, owner diversity, and trend windows.
  • Market breadth: how many distinct products or repositories exhibit the same pain (the uniqueOwnerCount field).
  • Timeline and history: daily mention buckets and tracked score/volume over time.
  • Opportunity briefs: read existing EchoSift-generated briefs or synthesize your own from raw data.
  • Pricing or market size in dollars.
  • Competitor product analysis beyond named existing-solution lists in briefs.
  • Forward-looking predictions.

Do not ask the tools for these; say so rather than inventing them.

Tool Purpose
get_taxonomy Valid filter values and data freshness
search_signals Semantic search by natural-language query
list_pain_signals Browse with structured filters
trending_signals Trending, emerging, or top signals
get_pain_signal Full detail: stats, why-now, adjacent signals
get_signal_timeline Daily mentions and tracked history
get_signal_evidence Real developer quotes with source permalinks
get_brief Read existing opportunity briefs