MCP Server for BoondManager API - 158 tools across 36 domains for ERP/CRM data
BoondManager MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. MCP Server for BoondManager API - 158 tools across 36 domains for ERP/CRM data.
Serveur MCP (Model Context Protocol) pour l'API BoondManager, permettant a Claude (Desktop, Cowork, Code) de rechercher, consulter, creer et modifier des enregistrements dans votre instance BoondManager.
Installation goes through your MCP client rather than a global install: point it at boondmanager-mcp-server on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Once BoondManager is connected, these are the calls the assistant has available:
Reporting — The Reporting tool exposed by this serverSmithery — Le serveur est aussi disponible sur Smithery. La configuration est dans smithery.yamlCursor — Cliquez sur le badge **[Add to Cursor](https://cursor.com/install-mcp?name=boondmanager&config=eyJjb21tYW5kIjoibnB4IiwiYXJncyI6WyIteSIsImJvb25kbWFuYWdGoose — Ajoutez une extension de type STDIO dans Settings > Extensions > Add avec la commande npx -y boondmanager-mcp-server et la variableLogs — Le serveur utilise pino pour des logs structures JSON (agrégateurs, observabilité)Authentification — The Authentification tool exposed by this serverYou will need 8 environment variables: BOOND_API_TOKEN, BOOND_BASE_URL, BOOND_USER_TOKEN, BOOND_CLIENT_TOKEN, BOOND_CLIENT_KEY, BOOND_USER, BOOND_PASSWORD, BOOND_HTTP_TIMEOUT_MS. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
This sits in the monitoring and observability group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. BoondManager's toolset — Reporting, Smithery, Cursor and 3 more — is a fair guide to whether it matches your workflow. It is maintained by fauguste; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against BoondManager's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Reporting | The Reporting tool exposed by this server. |
| Smithery | Le serveur est aussi disponible sur [Smithery](https://smithery.ai/server/@fauguste/boondmanager-mcp-server). La configuration est dans smithery.yaml à la racine du repo : Smithery propose une UI avec les champs d'authen |
| Cursor | Cliquez sur le badge **[Add to Cursor](https://cursor.com/install-mcp?name=boondmanager&config=eyJjb21tYW5kIjoibnB4IiwiYXJncyI6WyIteSIsImJvb25kbWFuYWdlci1tY3Atc2VydmVyIl19)** en haut du README (ou ajoutez le serveur manu |
| Goose | Ajoutez une extension de type **STDIO** dans **Settings > Extensions > Add** avec la commande npx -y boondmanager-mcp-server et la variable d'environnement BOOND_API_TOKEN. En CLI : |
| Logs | Le serveur utilise [pino](https://getpino.io/) pour des logs structures JSON (agrégateurs, observabilité). |
| Authentification | The Authentification tool exposed by this server. |
{
"mcpServers": {
"boondmanager": {
"command": "npx",
"args": ["-y", "boondmanager-mcp-server"],
"env": {
"BOOND_API_TOKEN": "votre_token_jwt"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| BOOND_API_TOKEN | Credential the server authenticates with. | Yes |
| BOOND_BASE_URL | Endpoint or connection string the server talks to. | Yes |
| BOOND_USER_TOKEN | Credential the server authenticates with. | Yes |
| BOOND_CLIENT_TOKEN | Credential the server authenticates with. | Yes |
| BOOND_CLIENT_KEY | Credential the server authenticates with. | Yes |
| BOOND_USER | Configuration value read at startup. | Optional |
| BOOND_PASSWORD | Configuration value read at startup. | Optional |
| BOOND_HTTP_TIMEOUT_MS | Configuration value read at startup. | Optional |
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.
Errors with full context — stack traces, issue triage and AI-powered root-cause analysis from Sentry's server.
Enables enhanced web research capabilities for large language models through intelligent search queuing and advanced content extraction.
Automates browser interactions and enables Large Language Models (LLMs) to interact with web pages through Playwright and Chrome DevTools Protocol
Guides tool usage by providing recommendations for MCP tools at each problem-solving stage.