Skip to main content

​
What it is

Stover runs a Model Context Protocol server, so an MCP client such as Claude can read and act on your Stover workspace directly. Ask about your pipeline, draft a post with a tracking link attached, or check which post produced a deal, without leaving the conversation. Endpoint: https://api.stover.app/v1/mcp

Connect it

Add Stover to Claude in about a minute, with no API key.

​
What it can reach

63 tools across the whole product surface.

CRM and pipeline

Contacts, companies, deals across every stage, and proposals.

Social publishing

Draft, schedule, read and delete posts on LinkedIn, Instagram, X, Threads, TikTok and YouTube.

Revenue attribution

Opt-in pages, tracking short links, and per-post attribution from click to closed deal.

Meetings and account

Fathom meeting summaries and transcripts, webhooks, billing and usage.
See the full tool catalogue for every tool and what it does.

​
How it behaves

Everything is scoped to you. Every tool operates only on the records belonging to the authenticated account. No tool accepts a user or account id, so there is no way to address another tenant’s data. Reads and writes are separate tools. There is no general-purpose query tool. Each tool is annotated as read-only, additive or destructive, and your MCP client uses those annotations to decide what to run without asking and what to confirm first. Nothing leaves Stover. Every tool reads and writes Stover’s own database. No tool calls a third-party service, and none of them generate media or move money. Credentials stay in the dashboard. The server will not mint an API key and will not return a webhook signing secret. Both are available in the Stover dashboard, where a person performs the action.

​
Limits

  • Rate limit: 60 tool calls per minute, per account.
  • Pagination: list tools default to 20 records and accept up to 100, and every list reports the unpaged total so you can tell when there is more.
  • Large text: list responses omit long bodies. Proposal content comes from stover_get_proposal, and meeting transcripts from stover_get_meeting.

​
Transport and protocol

Streamable HTTP, stateless — each request is self-contained, with no session to keep alive. Authorization follows the MCP specification: OAuth 2.1 with PKCE and dynamic client registration, discoverable from the endpoint itself. See Setup for both connection methods, and Troubleshooting when something does not connect.