oci ghcr.io/wyre-technology/salesbuildr-mcp:v1.5.7stdioApache-2.0updated 8d ago
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.
What can you do with SalesBuildr?
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
Interactive Quote Card (MCP Apps)
salesbuildr_quotes_get renders as an interactive, read-only quote card in
MCP Apps hosts (Claude Desktop/web) — title, status, company/contact, dates,
line items, and totals; plain-JSON behavior is unchanged in other hosts.
The card is neutral by default and brandable via window.__BRAND__ injection
or MCP_BRAND_* env vars (MCP_BRAND_NAME, MCP_BRAND_LOGO_URL,
MCP_BRAND_PRIMARY_COLOR, MCP_BRAND_ACCENT_COLOR, MCP_BRAND_BG,
MCP_BRAND_TEXT) — no rebuild needed.
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, everynpm installneeds a token. The cloud builder runsnpm installfor you, so you must give it one, or the build fails withnpm 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).
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-ai/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-ai/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-ai/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
Install
Add SalesBuildr to your client. Pick the one you use.
claude mcp add ghcr-io-wyre-technology-salesbuildr-mcp- -- docker run -i --rm ghcr.io/wyre-technology/salesbuildr-mcp:v1.5.7codex mcp add ghcr-io-wyre-technology-salesbuildr-mcp- -- docker run -i --rm ghcr.io/wyre-technology/salesbuildr-mcp:v1.5.7amp mcp add ghcr-io-wyre-technology-salesbuildr-mcp- -- docker run -i --rm ghcr.io/wyre-technology/salesbuildr-mcp:v1.5.7{
"mcpServers": {
"ghcr-io-wyre-technology-salesbuildr-mcp-": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/wyre-technology/salesbuildr-mcp:v1.5.7"
]
}
}
}Add to `claude_desktop_config.json`, then restart Claude Desktop.
{
"mcpServers": {
"ghcr-io-wyre-technology-salesbuildr-mcp-": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/wyre-technology/salesbuildr-mcp:v1.5.7"
]
}
}
}Add to `~/.cursor/mcp.json`, or `.cursor/mcp.json` for a single project.
code --add-mcp '{"name":"ghcr-io-wyre-technology-salesbuildr-mcp-","command":"docker","args":["run","-i","--rm","ghcr.io/wyre-technology/salesbuildr-mcp:v1.5.7"]}'Or add the block manually to `.vscode/mcp.json` under `servers`.
{
"mcpServers": {
"ghcr-io-wyre-technology-salesbuildr-mcp-": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/wyre-technology/salesbuildr-mcp:v1.5.7"
]
}
}
}Add to `~/.codeium/windsurf/mcp_config.json`.
{
"mcpServers": {
"ghcr-io-wyre-technology-salesbuildr-mcp-": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/wyre-technology/salesbuildr-mcp:v1.5.7"
]
}
}
}Add to `cline_mcp_settings.json` via the MCP Servers panel.
{
"mcpServers": {
"ghcr-io-wyre-technology-salesbuildr-mcp-": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/wyre-technology/salesbuildr-mcp:v1.5.7"
]
}
}
}Add to `~/.gemini/settings.json`.
{
"mcpServers": {
"ghcr-io-wyre-technology-salesbuildr-mcp-": {
"type": "local",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/wyre-technology/salesbuildr-mcp:v1.5.7"
],
"tools": [
"*"
]
}
}
}Add to `~/.copilot/mcp-config.json`, or run `/mcp add` inside the CLI.
{
"context_servers": {
"ghcr-io-wyre-technology-salesbuildr-mcp-": {
"command": {
"path": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/wyre-technology/salesbuildr-mcp:v1.5.7"
]
}
}
}
}Add to your Zed `settings.json`.
docker run -i --rm ghcr.io/wyre-technology/salesbuildr-mcp:v1.5.7Run `goose configure`, choose **Add Extension → Command-line Extension**, and paste this command.
Score
39 / 100
Incomplete
- Documentation25/25
- Maintenance25/25
- Trust16/20
- Capability0/15
- Install experience12/15
- Documents what it does and how to connect
- Has a resolvable package or endpoint
- Exposes at least one tool, prompt or resource
- README has substantive content
- Includes a code example
- Documents its configuration
- Mentions credentials or security posture
- Last commit 0 days ago
- Has a release history
- Repository is not archived
- Licensed Apache-2.0
- Namespace verified in the official MCP registry
- Claimed by its owner
- Published under an organisation
- 0 tool(s) documented
- Provides prompt templates
- Provides resources
- 12 documented install method(s)
- Published to a package registry
- Offers a hosted endpoint — no local install
Version history
| Versions | Published |
|---|---|
| 1.5.7Latest | Aug 20, 2026 |
| 1.5.6 | Aug 13, 2026 |
| 1.5.5 | Aug 13, 2026 |
| 1.5.4 | Aug 10, 2026 |
| 1.5.3 | Aug 7, 2026 |
| 1.5.2 | Jul 24, 2026 |
| 1.5.1 | Jul 18, 2026 |
| 1.5.0 | Jul 17, 2026 |
| 1.4.0 | Jun 2, 2026 |
| 1.3.6 | Jun 2, 2026 |
| 1.3.5 | May 22, 2026 |
| 1.3.4 | May 21, 2026 |
| 1.3.3 | May 6, 2026 |