> ## Documentation Index
> Fetch the complete documentation index at: https://developers.stover.app/llms.txt
> Use this file to discover all available pages before exploring further.

# MCP Server

> Connect Claude and other MCP clients to your Stover CRM, pipeline, social publishing and revenue attribution

## What it is

Stover runs a [Model Context Protocol](https://modelcontextprotocol.io) 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`

<Card title="Connect it" icon="plug" href="/mcp/setup" horizontal>
  Add Stover to Claude in about a minute, with no API key.
</Card>

## What it can reach

63 tools across the whole product surface.

<CardGroup cols={2}>
  <Card title="CRM and pipeline" icon="address-book">
    Contacts, companies, deals across every stage, and proposals.
  </Card>

  <Card title="Social publishing" icon="share-nodes">
    Draft, schedule, read and delete posts on LinkedIn, Instagram, X, Threads, TikTok and YouTube.
  </Card>

  <Card title="Revenue attribution" icon="chart-line">
    Opt-in pages, tracking short links, and per-post attribution from click to closed deal.
  </Card>

  <Card title="Meetings and account" icon="microphone">
    Fathom meeting summaries and transcripts, webhooks, billing and usage.
  </Card>
</CardGroup>

See the [full tool catalogue](/mcp/tools) 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](/mcp/setup) for both connection methods, and
[Troubleshooting](/mcp/troubleshooting) when something does not connect.

## Legal

* [Privacy Policy](https://stover.app/privacy-policy)
* [Terms of Service](https://stover.app/terms-of-service)
* Support: [support@stover.app](mailto:support@stover.app)