Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@D-Tools MCP Server What's the profitability of project 9876?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
A production-ready Model Context Protocol (MCP) server that connects AI assistants to the D-Tools System Integrator (SI) platform. Designed for professional audio-visual (AV) integrators, it exposes 25 tools covering the full SI workflow — projects, clients, catalogs, tasks, service orders, purchase orders, and health monitoring — directly to Claude Desktop, Cursor, and any other MCP-compatible host.
D-Tools SI manages the complete AV project lifecycle: quoting, equipment tracking, task management, and client records. Its API uses a queue-based publish/subscribe model where integrators publish changes and consumers poll or receive webhooks.
MCP standardises how AI agents call external tools. Combining the two means Claude (or any AI host) can look up a project, analyse its profitability, create a task, or check a purchase order — all through natural language, with no custom glue code.
Related MCP server: mcp-tap
# 1. Clone and install
git clone https://github.com/Saml1211/D-Tools-MCP-Server.git
cd D-Tools-MCP-Server
npm install
# 2. Configure
cp .env.example .env
# Edit .env — set DTOOLS_API_URL and DTOOLS_API_KEY
# 3. Build and run
npm run build
npm startThe server connects over stdin/stdout and is immediately usable by any MCP host.
Edit your Claude Desktop config (%APPDATA%/Claude/config.json on Windows, ~/Library/Application Support/Claude/config.json on macOS):
{
"mcpServers": {
"d-tools": {
"command": "node",
"args": ["/path/to/D-Tools-MCP-Server/dist/index.js"],
"env": {
"DTOOLS_API_URL": "https://api.d-tools.com",
"DTOOLS_API_KEY": "your-dtools-api-key"
}
}
}
}Restart Claude Desktop and try: "List all active projects" or "Analyse the profitability of project 12345".
docker build -t dtools-mcp .
docker run -it --rm \
-e DTOOLS_API_URL=https://api.d-tools.com \
-e DTOOLS_API_KEY=your-dtools-api-key \
dtools-mcpFeature | Detail |
25 MCP tools | Projects, clients, catalogs, tasks, service orders, purchase orders, health |
Strict validation | Every tool input validated with Zod before hitting the API |
Resilient HTTP | Axios with exponential retry/backoff for transient failures |
Rate limiting | Token-bucket limiter protects SI API quotas |
Webhook support | Optional listener with HMAC SHA-256 signature verification |
Structured logging | Pino JSON logs to stderr; sensitive headers redacted |
172+ tests | Unit, MCP-protocol, dispatch, and health suites — all offline |
Category | Tool | Purpose |
Projects |
| Fetch a project or change order by ID |
| Paginated list with search and status filters | |
| Publish a new project with optional line items | |
| Update any combination of fields | |
| Archive or unarchive one or more projects | |
| Cost, revenue, profit and gross margin from line items | |
| Equipment totals grouped by category | |
Clients |
| Retrieve a client by ID |
| Paginated list with search | |
| Publish a new client record | |
| Update contact or company details | |
Catalogs |
| Fetch a product catalog entry by ID |
| Search by keyword across the product catalog | |
| Paginated catalog listing | |
Tasks |
| Retrieve a task by ID |
| List tasks, optionally filtered by project | |
| Publish a new task | |
| Update status, assignee, or due date | |
Service Orders |
| Retrieve a service order by ID |
| List with client and progress filters | |
| Publish a new service order | |
Purchase Orders |
| Retrieve a purchase order by ID |
| List with vendor and status filters | |
Health |
| API connectivity, config, webhooks, and rate-limiter status |
| Uptime, memory usage, and Node.js version |
// Fetch a project
{ "name": "get_project", "arguments": { "id": "12345" } }
// Analyse profitability
{ "name": "analyze_project_profitability", "arguments": { "id": "12345" } }
// Create a client
{
"name": "create_client",
"arguments": {
"client": { "name": "Acme Corp", "email": "info@acme.example" }
}
}
// Search catalog
{ "name": "search_products", "arguments": { "searchText": "65 inch display" } }Copy .env.example to .env and set the variables:
Variable | Required | Description |
| Yes | Base URL of the SI API (no trailing slash) |
| Yes | Your SI API key ( |
| No | Enable the webhook listener on this port |
| No | HMAC-SHA256 secret for webhook signature verification |
| No | Pino log level — |
Get your API key from the D-Tools SI desktop app under Settings → API Integration.
# Install dependencies
npm install
# Type-check
npx tsc --noEmit
# Lint
npm run lint
# Run offline test suite
npm test
# Run with coverage
npm run test:ci
# Run MCP-protocol tests only
npm run test:mcp
# Run tests against the local mock API
node mock-api/server.js # Terminal 1
cp .env.test .env && npm test # Terminal 2See TESTING.md for the full testing guide, including integration tests and the mock API server.
src/
├── index.ts # Entry point — creates McpServer, registers tools, starts stdio transport
├── config.ts # Zod-validated environment configuration
├── logger.ts # Pino logger (sensitive header redaction)
├── lib/
│ ├── dtools-client.ts # Axios HTTP client with retry/backoff
│ ├── auth.ts # API key auth helper
│ ├── errors.ts # Custom error classes
│ ├── rate-limiter.ts # Token-bucket rate limiter
│ ├── request-context.ts # Async-local-storage request tracing
│ ├── webhook-handlers.ts # SI event handlers
│ └── webhook-server.ts # Optional HMAC-verified HTTP listener
├── tools/
│ ├── projects.ts # 7 project tools
│ ├── clients.ts # 4 client tools
│ ├── catalogs.ts # 3 catalog tools
│ ├── tasks.ts # 4 task tools
│ ├── service-orders.ts # 3 service order tools
│ ├── purchase-orders.ts # 2 purchase order tools
│ └── health.ts # 2 health tools
├── types/
│ ├── dtools.ts # SI domain types
│ └── mcp.ts # MCP response types
└── __tests__/ # Vitest test suite (172+ tests, all offline)The SI API uses a queue-based model: Publish/… endpoints write changes, Subscribe/… endpoints read them. When listing entities you may need to paginate to drain the full queue — use pageNumber and pageSize on any list tool.
The API key is loaded from .env and injected as X-DTSI-ApiKey on every request. The Pino logger redacts this header so it never appears in log output.
If webhooks are enabled, the server verifies every incoming request's x-signature header with HMAC SHA-256 before dispatching.
All tool inputs are validated by Zod before any API call is made.
Symptom | Fix |
Tools not listed in host | Ensure the server process started and logged |
401 Unauthorized | Invalid or missing |
Empty list responses | SI only returns data that has been published to the queue. Use |
Repeated timeouts | The client retries 3× with exponential backoff. Check network access to |
Pull requests are welcome. See CONTRIBUTING.md for branching conventions, code style, and how to add new tools.
MIT © Sam Lyndon
Built for the AV integration community
Analyse the financial profitability of a D-Tools SI project. Returns total cost, revenue, profit, and gross margin calculated from all line items.
Inputs: id (required).
Archive or unarchive one or more D-Tools SI projects by their IDs. Set archive to false to restore previously archived projects.
Inputs: ids (required), archive.
Create a new client record in D-Tools SI. Requires a name; optionally accepts email, phone, company, and address.
Inputs: client (required).
Create a new project in D-Tools SI. Requires a project name; optionally accepts description, client association, status, and line items.
Inputs: project (required).
Create a new service order in D-Tools SI. Requires a name; optionally accepts project, client, description, status, due date, and line items.
Inputs: serviceOrder (required).
Create a new task in D-Tools SI. Requires a name; optionally accepts project, description, status, assignee, and due date.
Inputs: task (required).
Retrieve a D-Tools SI product catalog entry by its unique ID.
Inputs: id (required).
Retrieve a D-Tools SI client record by its unique ID.
Inputs: id (required).
Return a grouped equipment summary for a D-Tools SI project, aggregating quantities and costs by category (falls back to product ID when no category is set).
Inputs: id (required).
Retrieve a D-Tools SI project or change order by its unique ID. Returns the full project record including all line items.
Inputs: id (required), coNumber.
Retrieve a D-Tools SI purchase order by its unique ID.
Inputs: id (required).
Retrieve a D-Tools SI service order by its unique ID.
Inputs: id (required).
Retrieve a D-Tools SI task by its unique ID.
Inputs: id (required).
Run a comprehensive health check verifying D-Tools API connectivity, configuration, webhook handler registration, and rate limiter status.
Inputs: no named parameters.
List D-Tools SI product catalog entries with optional pagination and search text filtering.
Inputs: pageSize, pageNumber, searchText.
List D-Tools SI client records with optional pagination, search text, and deleted or imported filters.
Inputs: pageSize, pageNumber, searchText, includeDeleted, +1 more.
List D-Tools SI projects with optional pagination and filtering by search text, archived, imported, or deleted status.
Inputs: pageSize, pageNumber, searchText, includeDeleted, +2 more.
List D-Tools SI purchase orders with optional pagination, search text, vendor filters, and status filters.
Inputs: vendors, pageSize, statuses, pageNumber, +3 more.
List D-Tools SI service orders with optional pagination, search text, client filters, and progress status filters.
Inputs: clients, pageSize, pageNumber, progresses, +3 more.
List D-Tools SI tasks with optional filters for project association, search text, pagination, and deleted or imported status.
Inputs: pageSize, projectId, pageNumber, searchText, +2 more.
Search the D-Tools SI product catalog by keyword. Returns matching entries with pricing, manufacturer, and specification data.
Inputs: searchText (required), pageSize, pageNumber.
Return a quick status snapshot of the MCP server process, including uptime, memory usage, and Node.js version.
Inputs: no named parameters.
Update an existing D-Tools SI client by ID. Accepts any combination of name, email, phone, company, and address.
Inputs: client (required).
Update an existing D-Tools SI project by ID. Accepts any combination of name, description, client, status, archived flag, and line items.
Inputs: project (required).
Update an existing D-Tools SI task by ID. Accepts any combination of project, name, description, status, assignee, and due date.
Inputs: task (required).
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Scored across 25 tools
Most tools are clearly distinct per resource, but there is overlap between archive_project and update_project (both can change archive status) and between search_products and list_catalogs (both filter catalog entries). This creates some ambiguity.
Naming predominantly follows verb_noun pattern (create_client, get_project, list_tasks), though exceptions like analyze_project_profitability, health_check, and server_status break the pattern, causing minor inconsistency.
25 tools is on the higher side but well-justified given the multiple domain entities (clients, projects, tasks, service orders, purchase orders, catalogs) plus utility tools. The count is reasonable for the scope.
Basic CRUD is present for clients and projects, but missing for other entities: no create for purchase orders, no update for service orders, and no delete operations for any entity. These gaps hinder full workflow coverage.
Hosted MCP server connecting AI assistants to 9,000+ apps and 40,000+ actions via Zapier.
MCP server unifying ERPs, CRMs, APIs and knowledge base for Claude, ChatGPT and Gemini.
MCP server that lets AI assistants use all OneSchema features exposed via the public API.
One MCP server for the services your AI needs: memory, files, Microsoft 365, kanban and more.
