Business operationsPublic source

Sales MCP Server

Enterprise sales MCP server with 29 tools across 4 backends — PandaDoc, Apollo.io, Calendly, and Stripe Billing. Proposals with lifecycle management, CPQ (configure-price-quote), sales sequences, meeting scheduling, and…

Open the source Read the official guide ↗

What it gives an agent

A purpose-built capability behind one MCP connection.

The server owns its domain logic and publishes a tool contract an MCP client can discover. ADK-Rust can load that contract into an agent, normalize each schema for the chosen model provider, and keep the connection lifecycle outside the agent’s business logic.

Full sales lifecycle — draft → sent → viewed → signed → won with tracking at every stage

Modular backends — each backend is optional; use any combination

Revenue-focused — proposals, quotes, and forecasting drive pipeline visibility

Engagement tracking — know when prospects open emails, view proposals, click links

No credential exposure — API keys stay in env vars

Architecture

How Sales MCP Server fits into an agent system.

The model never needs the implementation details or credentials of the system behind the server. It sees reviewed tool definitions. The MCP client handles discovery and calls, while the server keeps ownership of validation, policy, and communication with its domain system.

ADK-Rust agent

Chooses a capability from the reviewed tool catalog.

→

MCP client

Discovers schemas, sends calls, and receives typed content.

→

Sales MCP Server

Validates the request and owns 29 documented tool contracts.

→

Domain system

Keeps the API, data, credentials, and business rules behind the server.

Connection: stdio · Server framework: ADK MCP SDK + rmcp

Sales MCP Server architecture diagram from its official repository

Tool catalog

What can an agent ask Sales MCP Server to do?

Each tool has a stable name, a human-readable purpose, and a JSON input contract discovered during MCP initialization. Risk classes come from the project’s registry manifest when one is available.

29 named tools

create_proposal

Create a new proposal/document in draft state

internal write

list_proposals

List proposals with optional status filter

read only

get_proposal

Get proposal details including status, recipients, and metadata

read only

send_proposal

Send a draft proposal to recipients for review/signature

external write

delete_proposal

Delete a proposal

external write

list_templates

List available proposal/document templates

read only

create_from_template

Create a new proposal from a template with variable substitution

internal write

request_signature

Request e-signature on a sent proposal

external write

get_signature_status

Get signature status for a proposal

read only

list_signatures

List all documents pending or completed signature

read only

get_proposal_views

Get view/open events for a proposal (who viewed, when, duration)

read only

get_proposal_analytics

Get aggregate analytics for proposals (conversion rates, avg time to sign)

read only

Governance

Understand the effect of every tool.

A server connection inherits the authority of its credentials and deployment environment. The declarations below come from this project’s README and MCP registry manifest; your application still decides which tools an agent receives and where approval is required.

17 read only6 internal write6 external write

The registry manifest declares internal write, read only, external write tool risk classes.

MCP surface

What the current documentation declares.

MCP can carry tools, resources, prompts, structured results, progress, cancellation, and long-running work. This record highlights the modern protocol features explicitly mentioned by this repository.

The current README concentrates on its tool surface. Check the source and release notes before relying on optional MCP capabilities beyond tool discovery and invocation.

ADK MCP SDKrmcpRegistry manifest

Install and connect

Follow the project’s documented starting point.

Install the server in the environment that owns its credentials and domain access. Add it to your MCP host, verify the discovered tools, and narrow the toolset before giving it to a production agent.

Install

cargo install mcp-sales --features all-backends

MCP client configuration

export PANDADOC_API_KEY="your-api-key"

Commands and configuration are extracted from the public README. Confirm prerequisites, environment variables, and release-specific options in the official documentation before deployment.

Official documentation

Continue with the project maintainers’ source of truth.

This page provides an approachable map of the server. The repository remains authoritative for exact schemas, prerequisites, configuration, examples, tests, releases, and security updates.

Overview ↗README.md CHANGELOG ↗CHANGELOG.md Architecture ↗docs/assets/architecture.svg Issues and support ↗github.com issues

Keep exploring