Skip to main content
There are two ways to connect. OAuth is the one to use unless you are scripting something headless. No key to create, copy or store. You sign in to Stover in the browser, approve the connection once, and the client holds a short-lived token it refreshes on its own.
1

Add the connector

In Claude, open Settings > Connectors > Add custom connector and enter:
2

Approve it

Claude opens the Stover consent screen at dashboard.stover.app/oauth/consent. Sign in if you are not already, review what the connector is asking for, and approve.
3

Done

The tools appear in the client. Nothing else to configure.
Under the hood the client registers itself (RFC 7591), discovers the authorization server from the endpoint (RFC 9728), and completes an OAuth 2.1 authorization code exchange with PKCE. Access tokens last 15 minutes and are bound to the MCP resource, so one cannot be replayed against anything else.

​
API key

For scripts, CI, or a client that does not implement OAuth.
1

Create a key

In the Stover dashboard, go to Settings > API Keys and create one. The full key is shown once — copy it then.
Key creation is deliberately not available over MCP. An API key authenticates the entire Stover REST API, not just this server, so creating one stays a deliberate human action.
2

Add the server

​
Verify the connection

Ask the client to list your deals, or call a read-only tool directly:
A working connection returns your current plan. If it returns a 401 instead, see Troubleshooting.

​
Testing with MCP Inspector

To exercise tools outside a chat client:
Set the transport to Streamable HTTP and the URL to https://api.stover.app/v1/mcp. Leave authentication empty to walk the OAuth flow, or supply a stover_pk_* key as a bearer token.