Doit MCP Server
DoiT platform data access for troubleshooting and analysis via LLMs.
Data last scanned today · Reviewed today
Overview
The DoiT MCP Server allows LLMs to query the DoiT API directly, facilitating automated troubleshooting and data analysis tasks within your AI workspace. It supports both remote connections via OAuth or Bearer token and local stdio execution for tailored environment setups. Configuration options include remote streamable HTTP access for standard clients or direct stdio execution for headless environments requiring automated API interactions. The server relies on the existing DoiT API permissions assigned to your user account, ensuring compatibility with your current organizational access levels.
Our verdict
With a security score of 43/100, this server is currently classified as high risk. The security architecture, specifically its authentication method and read-only status, has not yet undergone a formal editorial review. Due to the lack of independent validation for its security claims, it is best suited for experienced users or development environments who can monitor the server's activities closely.
- Supports local stdio and remote streamable HTTP connection modes.
- Maintains an active development cycle with recent commits.
- Small dependency footprint with only four direct packages.
- Includes documented support for headless and CI/CD integrations.
- Security implementation remains unverified by third-party editorial review.
- No definitive audit confirmation for read-only operation enforcement.
- Not maintained directly by the official DoiT organization.
Setup
{
"mcpServers": {
"doit-mcp-server": {
"args": [
"-y",
"@doitintl/doit-mcp-server"
],
"command": "npx"
}
}
}Paste into ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows), then restart Claude Desktop. Some servers require API keys or tokens as environment variables — check the project's README and add an "env" object if needed.
- No read-only mode — running this grants full read/write access.
- No built-in authentication — anyone with access to this config can invoke every tool it exposes.
Compatibility
| Client | Local | Docker | Remote | Read-only |
|---|---|---|---|---|
| Claude Desktop | ||||
| Cursor | ||||
| VS Code | ||||
| Windsurf | ||||
| ChatGPT |
Frequently asked questions
›What are the system prerequisites for running the local stdio version?
You must have Node.js version 18 or higher installed and a personal API token generated from the DoiT console.
›How do I authenticate with the remote HTTP server in a headless environment?
Headless clients can authenticate by sending a personal API token as a Bearer token in the Authorization header to the remote URL.
›Are DoiT employee tokens accepted by the remote MCP endpoint?
No, DoiT employee tokens are not supported on the remote endpoint; employees should use OAuth or the local stdio server instead.
›What permissions do the server's tools have?
The tools inherit the same permissions as your personal API token within the DoiT platform.
›Can I use the server if I am not running Claude Desktop?
Yes, the server is compatible with other MCP-supported clients such as Cursor, VS Code, Amazon Q, and Claude Code.
›Is the legacy SSE endpoint still supported?
No, the legacy SSE endpoint is deprecated and should not be used for new setups.
Changelog
Badge
Maintain this server? Add the live badge to your README.