POST {RETRIEVER_API_URL}/mcp). Names and descriptions match the runtime contract; exact input schemas are returned by tools/list when you connect.
For Cursor or Claude Desktop setup, see Model Context Protocol (MCP).
Account
Public services (level 1)
Resource:
retriever://skills/retriever-services — instructions for the discover → inspect → execute loop.
service_discover filter categories: contacts, companies, jobs, web, social, ads, generate.
List-building (agent runs)
REST equivalent:
POST /v1/runs, GET /v1/runs/{id}, cancel via the runs API.
Autonomous research (Go)
Tables
Sequences (outreach)
Senders
Shared inbox
MCP annotations
Many tools expose MCP hints (readOnlyHint, destructiveHint) so host agents know when to ask for confirmation. Destructive or sensitive operations often accept confirm: true by default.
Verify the tool list from a client
After connecting, your MCP client exposestools/list. In the monorepo:
server-contract.test.ts contract test pins expected tool names in the repo—useful to catch doc drift.