Salesbuildr MCP Server

An MCP server for the Salesbuildr public API, the quoting and sales platform built for MSPs. It lets an AI agent search companies, contacts, the product catalog, opportunities and quotes and, on explicit request, create or update companies, contacts and opportunities, delete companies and contacts, and create draft quotes from catalog products.

• Transport: MCP Streamable HTTP at POST /mcp, health probe at GET /health

• Stateless and multi-tenant: the API key arrives on every request as an HTTP header and is never stored; every tool is listed from the first tools/list

• Python 3.12, uv, FastMCP, httpx

• License: Apache-2.0, Copyright 2026 MSPbots.ai

MSPbots Connector

The MCP Gateway built for MSPs: visible, controlled, and your data stays where it belongs.

Get started at connect.mspbots.ai →

MSPbots Connector gives your AI clients one MCP URL to reach your entire MSP stack (RMM, PSA, documentation, security, finance), and gives you control over who can call which tool and a record of everything that was called.

Hosted service: connect.mspbots.ai · Free to use.

Why Connector

Quick start

1. Sign up at connect.mspbots.ai.

2. Connect your vendors. Pick from 150+ connectors and authorize each one on the vendor's own page, or bring your own API keys. No extra vendor accounts needed.

3. Set access. Create roles and decide which tools each role may call. Nothing is allowed until you allow it.

4. Add your MCP URL to your AI client. Copy the URL from your Connector dashboard into Claude, ChatGPT, Cursor, VS Code, Gemini, Codex, or any MCP-capable client.

5. Ask your AI to do real work, and watch every call appear in the audit log.

Features

Unified gateway

• One MCP URL for all your AI clients

• 150+ connectors across the MSP stack

• Custom MCP servers supported, free

• Authorization happens on each vendor's own page; the AI never sees passwords or tokens

• Bring your own credentials: use the vendor API keys you already have

• Multiple accounts per app; connect once, reuse across AI clients

• Tool search: finds the right action for the task

• One sign-in; vendor credentials are injected behind the scenes and OAuth tokens refresh automatically

Visibility

• Audit log for every tool call (who, which vendor, when)

• Usage dashboard: call volume, top vendors, error rate, per-user activity

• Export audit logs to CSV, or stream to Loki, Graylog, or LogScale (SIEM)

• Optional recording of tool arguments and result summaries (off by default, enabled per organization)

Control

• Per-role, per-tool allowlist, deny by default

• owner / admin / member roles

• SCIM provisioning with Entra ID, Okta, JumpCloud, and Google Workspace

Security

• Credentials encrypted one record at a time (AES-256-GCM, per-record key)

• AI clients authenticate with OAuth 2.1 + PKCE

• Vendor responses are scanned for prompt-injection patterns and returned as structured data. This is one layer of defense, not a guarantee against every attack.

• Static egress IP for customer firewall and API allowlisting

Pricing

Free.

Links: connect.mspbots.ai · mspbots.ai

Related MCP server: MCP Suite CRM

Authentication headers

Where to get it: a Salesbuildr administrator creates an API key in the Salesbuildr portal's integration / API settings. The key acts on the whole Salesbuildr account.

How the key is sent to Salesbuildr: in the api-key header of every call to https://portal.salesbuildr.com/public-api/....

A request to /mcp without the key gets HTTP 401; a base URL that is not https gets HTTP 400.

Tools

All tools return a JSON string. Lists search with query, page with from (offset) and size (default 25, max 100) and return {items, count, total, from, has_more, next_from}, most recently changed first.

Field mapping to the API: company phone -> telephone, notes -> stickyNote, address / city / state / zip / country -> the address object, domain -> website when no website is given; opportunity title -> name, value -> one-time revenue, monthlyValue -> monthly revenue, stage -> pipeline stage id, notes -> description, probability 0-1 (a percentage above 1 is divided by 100).

Errors come back as a JSON envelope instead of an exception:

{"error": {"code": "invalid_argument", "message": "Salesbuildr returned HTTP 400 for company: number must be a string", "retryable": false}}

code is one of not_configured, unauthorized, not_found, invalid_argument, rate_limited, upstream_error. Reads are retried with backoff on 429, 5xx and network errors; writes are retried only on 429.

Run locally

uv sync
uv run python -m salesbuildr_mcp          # listens on 0.0.0.0:8080

or with Docker:

docker build --platform linux/amd64 -t salesbuildr-mcp:dev .
docker run --rm -p 8080:8080 salesbuildr-mcp:dev

Configuration (environment variables, all optional): MCP_HTTP_HOST (default 0.0.0.0), MCP_HTTP_PORT (default 8080), LOG_LEVEL (default INFO). The key is never read from the environment.

Testing example

# list tools
curl -s http://localhost:8080/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "X-SalesBuildr-API-Key: your-api-key" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'

# quotes of one opportunity
curl -s http://localhost:8080/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "X-SalesBuildr-API-Key: your-api-key" \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"salesbuildr_quotes_list","arguments":{"opportunityId":"your-opportunity-id"}}}'

Unit tests (no network access needed):

uv run pytest

Delivery notes

• Tool count (21). Kept as is because the tool names are an existing contract.

• API contract. Requests follow Salesbuildr's published API reference (https://portal.salesbuildr.com/public-api). Older versions sent field names the API does not have (for example company phone, zip and notes at the top level, opportunity title / value / stage, quote items with free-text names); those now map to the real fields listed above, and parameters with no API field (contact title and notes, quote companyId / contactId / notes / validUntil) were removed.

• Quotes. The API creates quotes only for an opportunity and only from catalog products, so opportunityId is required and each line needs a productId.

• Updates. Company and contact updates replace the whole record in the API; this server reads the current record first and changes only the fields given.

• Deletes need confirm: true.

License

Apache License 2.0 - see LICENSE and NOTICE.