SalesBuildr MCP Server
A Model Context Protocol (MCP) server for integrating with the SalesBuildr quoting and sales platform. Built with a decision-tree architecture to expose domain-specific tools without overwhelming the LLM.
Architecture
The server uses a decision tree pattern:
- At root, only
salesbuildr_navigateis exposed - User selects a domain (companies, contacts, products, opportunities, quotes)
- Domain-specific tools become available along with
salesbuildr_back - Tool calls route to domain handlers that interact with the SalesBuildr API
Domains
| Domain | Tools | Description |
|---|---|---|
| companies | 5 | Company/account management (list, get, create, update, delete) |
| contacts | 5 | Contact management (list, get, create, update, delete) |
| products | 2 | Product catalog (list, get) |
| opportunities | 4 | Sales pipeline (list, get, create, update) |
| quotes | 3 | Quote management with line items (list, get, create) |
One-Click Deployment
IMPORTANT
Before you click: this server depends on @wyre-technology/node-salesbuildr,
which is hosted on the GitHub Packages npm registry. GitHub Packages has no
anonymous access — even though the package is public, every npm install needs a
token. The cloud builder runs npm install for you, so you must give it one, or
the build fails with npm error 401 Unauthorized ... npm.pkg.github.com.
- Create a GitHub Personal Access Token with the
read:packagesscope (classic token). Any GitHub account works — you do not need to be a member of thewyre-technologyorg to read its public packages. - Add it as a build variable when prompted by the deploy flow:
- Cloudflare Workers → set a build variable named
NODE_AUTH_TOKENto your PAT (Workers → Settings → Build → Variables and Secrets). - DigitalOcean App Platform → set an encrypted env var named
GITHUB_TOKENwith scope Build Time to your PAT (the Dockerfile reads it for the install).
- Cloudflare Workers → set a build variable named
Installation
This package is published to the GitHub Packages npm registry, which requires a token even for public packages. Authenticate once, then install:
# Authenticate npm to GitHub Packages (token needs the read:packages scope)
export NODE_AUTH_TOKEN=$(gh auth token) # or a PAT with read:packages
npm install @wyre-technology/salesbuildr-mcp
The repo's .npmrc already points the @wyre-technology scope at GitHub Packages and
reads the token from NODE_AUTH_TOKEN, so no further config is needed.
Configuration
Environment Variables
| Variable | Required | Default | Description |
|---|---|---|---|
SALESBUILDR_API_KEY | Yes (env mode) | - | Your SalesBuildr API key |
SALESBUILDR_BASE_URL | No | Library default | Tenant-specific base URL (e.g. https://mytenant.salesbuildr.com) |
MCP_TRANSPORT | No | stdio | Transport type: stdio or http |
MCP_HTTP_PORT | No | 8080 | HTTP server port |
MCP_HTTP_HOST | No | 0.0.0.0 | HTTP server host |
AUTH_MODE | No | env | Authentication mode: env or gateway |
Stdio Mode (Claude Desktop)
Add to your Claude Desktop config (claude_desktop_config.json):
{
"mcpServers": {
"salesbuildr": {
"command": "npx",
"args": ["@wyre-technology/salesbuildr-mcp"],
"env": {
"SALESBUILDR_API_KEY": "your-api-key"
}
}
}
}
HTTP Mode (Gateway)
MCP_TRANSPORT=http AUTH_MODE=gateway node dist/index.js
In gateway mode, pass credentials via request headers:
X-Salesbuildr-API-Key: your-api-key
Docker
docker run -d \
-p 8080:8080 \
-e SALESBUILDR_API_KEY=your-api-key \
ghcr.io/wyre-technology/salesbuildr-mcp:latest
Development
# Install dependencies
npm install
# Run tests
npm test
# Type check
npm run typecheck
# Build
npm run build
# Run locally (stdio)
SALESBUILDR_API_KEY=your-key npm start
# Run locally (HTTP)
MCP_TRANSPORT=http SALESBUILDR_API_KEY=your-key npm start
License
Apache-2.0