MCP100 verdict
Not currently recommended. First-party or well-evidenced implementation identity, meaningful task value, maintained setup evidence, and no material admission veto were found in reviewed sources.
MCP100 Assessment
Editorial verdict
Reviewed October 19, 2026
Task Fit
Mapped
Specialized workflows
Trust
Status warning
Shortlist evidence is sufficient for identity, setup and task value; authenticated runtime tool-schema measurement and exhaustive security certification remain out of scope.
Maintenance
Date unavailable
No dated repository or package update is currently stored.
Popularity
Signals available
Visible usage signals are shown for discovery only, not as proof of safety.
Evidence scope
13 MCP repository stars
6.9k package downloads / 30 days
Repository identity: doitintl/doit-mcp-server
Package identity: @doitintl/doit-mcp-server · version 2.7.0
Stars observed October 20, 2026 · Downloads observed October 20, 2026
Current first-party DoiT MCP implementation repository.
Exact MCP-specific npm package identity verified against the current first-party implementation.
Publisher activity observed October 20, 2026
Current source snapshot
Source relationship: First-party MCP
Reviewed October 19, 2026
Evidence-backed setup
Choose your MCP client. A client connects to the MCP server; the language model is selected inside that client. Only stored, source-backed configurations are shown.
Transport not recorded
Complete client-specific setup, verification and removal are not documented in this reviewed source.
Publisher-documented setup is not the same as MCP100 execution testing. “MCP100 logic checked” means the stored configuration shape was reviewed, not that third-party MCP software was run.
Evidence checked 2026-10-20
Type-appropriate, source-backed setup for this mcp server profile.
{"preferred":{"url":"https://mcp.doit.com/mcp"},"local":{"command":"npx","args":["-y","@doitintl/doit-mcp-server@latest"],"env":{"DOIT_API_KEY":"<TOKEN>"}}}Capability
DoiT’s official MCP server connects AI clients to DoiT cloud-cost, analytics, savings, reporting and support workflows. Cloud-cost and billing data can be commercially sensitive. Access follows DoiT API permissions; use scoped identities and avoid exposing personal API tokens in prompts or repositories.
Current tool set is generated from DoiT APIs plus handwritten tools; no stable exact total is asserted.
Not measured yet
Estimated token footprint of the MCP tool schemas exposed to the agent.
https://mcp.doit.com/mcp
Reviewed access
Related reviewed MCPs
Connect MCP clients to enterprise databases with prebuilt or explicitly defined tools.
Choose this instead if
Choose Google MCP Toolbox for Databases instead if schema exploration and database-aware coding in development environments.
Connect MCP clients to enterprise databases with prebuilt or explicitly defined tools.
Use Stripe's remote MCP endpoint for supported payment workflows.
Choose this instead if
Choose Stripe MCP instead if searching Stripe documentation and support knowledge from an MCP client.
Use Stripe's remote MCP endpoint for supported payment workflows.
Codebase knowledge graph for AI agents — 159 languages, sub-ms queries, 99% fewer tokens.
Choose this instead if
Choose Codebase Memory MCP instead if repository indexing, symbol search, call-path tracing, impact analysis, and architecture queries across many languages.
Recommended after reviewed 2026-09-25 admission dossier: all_current_selected_gates_pass.
DoiT is listed as First-party MCP in MCP100’s current evidence.
Current official resources:
Original product, capability, tool, and usage documentation from the MCP publisher. Installation sections appear under Install & Agents.
DoiT MCP Server provides access to the DoiT API. This server enables LLMs like Claude to access DoiT platform data for troubleshooting and analysis.
How you authenticate depends on the connection method:
| Method | URL / command | Auth |
|---|---|---|
| Remote (Streamable HTTP) | https://mcp.doit.com/mcp | OAuth — your client opens a DoiT sign-in and consent page. Headless clients can instead send a customer personal API token as Authorization: Bearer. |
| Local (stdio) | npx -y @doitintl/doit-mcp-server@latest | Personal API token via DOIT_API_KEY. |
The legacy SSE endpoint (https://mcp.doit.com/sse) is deprecated and should not be used for new setups.
Your DoiT plan must include API access. Tools follow the same permissions as the DoiT API.
Tool results are capped at 140,000 serialized UTF-16 code units after response formatting, including structured content and metadata. Oversized reads return an actionable error; completed writes return a compact success receipt and must not be repeated just to retrieve their output. Errors remain errors. This is a response size policy, not a token limit or a bound on upstream downloads.
Each dispatched call emits a payload-free JSON mcp_tool_response event to stderr
on stdio; some clients display these logs. Hosts can supply onResponseMetrics
to route the events elsewhere. Use original.serializedChars for response-size
percentiles and exceededLimit for over-limit rates; returned measures the result
after the guard. Metrics also include UTF-8 byte counts, duration, tool/client, and
disposition, without tool arguments or response bodies.
The Claude Desktop steps below are examples, not the only supported clients. Cursor, VS Code, Amazon Q, Claude Code, and others are covered in the Connections guide.
Example with Claude Desktop: add a custom connector (+ → Add connector → Add custom connector) and set the remote MCP server URL to https://mcp.doit.com/mcp. Complete DoiT sign-in when prompted.
Agents that cannot open a browser (for example HolmesGPT on a cluster, CI jobs, cron workers) can authenticate to the same endpoint with a customer personal API token sent as a bearer header. Tools run with that token's permissions, exactly as on stdio. DoiT employee tokens are not accepted on the remote endpoint; employees use OAuth or the local server.
Example with HolmesGPT:
mcp_servers:
doit:
description: "DoiT Cloud Intelligence"
config:
url: "https://mcp.doit.com/mcp"
mode: streamable-http
headers:
Authorization: "Bearer {{ env.DOIT_API_KEY }}"
health_check_tool: "validate_user"
Keep the token in a secret store and rotate it on a schedule. Design notes: docs/remote-api-key-bearer-auth.md.
Supports Skills over MCP for compatible clients. No skills are bundled by default.
Requires Node.js v20 or higher and a personal API token as DOIT_API_KEY. Create a token from the Personal API tokens page in the DoiT console.
Example with Claude Desktop — add the following to claude_desktop_config.json (or Settings), then restart Claude:
{
"mcpServers": {
"doit_mcp_server": {
"command": "npx",
"args": ["-y", "@doitintl/doit-mcp-server@latest"],
"env": {
"DOIT_API_KEY": "your_doit_api_key"
}
}
}
}
DOIT_API_KEY: Your DoiT API token (required)CUSTOMER_CONTEXT: Customer context identifier (optional)The stdio server works with clients of both MCP protocol eras without any configuration:
2024-10-07 through 2025-11-25, through the initialize handshake.2026-07-28, through server/discover.Each connection's opening message decides which era it uses. See docs/protocol-compatibility.md for the details and the tests that verify it.
If you want to clone and run this MCP server directly from the source code, follow these steps:
git clone https://github.com/doitintl/doit-mcp-server
cd doit-mcp-server
yarn install
yarn build
DOIT_API_KEY=your_doit_api_key node dist/index.js
Applications that provide their own MCP transport can reuse the published, transport-independent implementation:
npm install @doitintl/doit-mcp-server@latest
import {
COVERED_ENDPOINTS,
executeToolHandler,
generateTools,
generatedToolsOpenApiSpec,
HAND_WRITTEN_TOOLS,
} from "@doitintl/doit-mcp-server/core";
The /core entry includes the tool and prompt definitions, generated-tool
utilities, request handling, and shared configuration APIs. It does not initialize
the stdio transport or include the Cloudflare Worker, OAuth, Durable Objects, or
widget implementation.
Here are some common queries you can ask using the DoiT MCP server:
These examples demonstrate basic usage patterns. You can combine and modify these queries based on your needs. The MCP server will interpret your natural language queries and use the appropriate tools to fetch the requested information.
Used by the local stdio server. Remote /mcp connections authenticate with OAuth.
DOIT_API_KEY: Your DoiT personal API token (required for stdio)CUSTOMER_CONTEXT: Your customer context identifier (optional)