
BoondManager MCP Server
Let your coding agent query and update BoondManager ERP/CRM data—projects, resources, billing—through a large stdio MCP surface instead of manual portal work.
Overview
BoondManager MCP Server is a MCP server for the Operate phase that exposes 167 BoondManager ERP/CRM API tools plus prompts and resources over stdio.
What is this MCP server?
- 167 MCP tools covering BoondManager API operations
- 11 bundled prompts and 21 resources for ERP/CRM context
- stdio transport via npm package boondmanager-mcp-server v2.2.0
- Alternate mcpb release artifact with published file SHA256
- Self-hosted GitHub repo with 128x128 icon in registry manifest
- 11 prompts
Community signal: 12 GitHub stars.
What problem does it solve?
Updating BoondManager records and reports through the web UI breaks flow when you already use an AI coding agent for everything else.
Who is it for?
Indie consultancies and small shops on BoondManager who want agent-driven CRM/ERP queries and updates with stdio MCP.
Skip if: Builders not on BoondManager, or teams that forbid agents from touching production CRM without human approval on every write.
What do I get? / Deliverables
After install, your agent can read and act on BoondManager data via MCP so operational CRM work stays in the same environment as your code.
- 167 BoondManager API operations callable from the agent
- 11 prompts and 21 resources for structured ERP/CRM context
- Local stdio MCP server wired into your editor config
Recommended MCP Servers
Journey fit
Operate is the canonical shelf because BoondManager supports running a consulting or services business after the product exists, syncing ops data daily. Iterate fits ongoing CRM/ERP adjustments, reporting fixes, and workflow tweaks driven from the agent.
How it compares
Full ERP/CRM API MCP bridge, not a generic PostgreSQL connector or a sales copywriting skill.
Common Questions / FAQ
Who is BoondManager MCP Server for?
BoondManager customers—often small agencies or freelancers—who use MCP-enabled coding agents and want direct API coverage from the editor.
When should I use BoondManager MCP Server?
Use it in Operate when you iterate on projects, resources, timesheets, or billing data and want the agent to call BoondManager instead of retyping portal steps.
How do I add BoondManager MCP Server to my agent?
Install boondmanager-mcp-server from npm at v2.2.0 or the published mcpb release, add stdio MCP config with your BoondManager API credentials, and restart your client.