doit

This MCP server provides access to the DoiT API so large language models and automation tooling can query DoiT data for troubleshooting, cost analysis, incident details, invoices, and more. The server exposes a collection of tools (e.g., get_cloud_incidents, get_anomalies, list_reports, run_query, get_report_results, validate_user, and various allocation, alert, and invoice related endpoints) that you can call through natural-language prompts. Use the supported commands via the MCP interface described in the repository, or configure clients like Claude Desktop or Cursor to point at the MCP URL and feed it your API key to perform authenticated queries. You can also run the server locally from source for development or testing, then connect your client to http://localhost or your deployed host.

Prerequisites:

• Node.js v18 or higher
• npm or yarn
• A DoiT API key with appropriate permissions

Option A: Quick start with npx (recommended for end users)

1. Ensure you have Node.js v18+ installed.
2. Run the MCP server via npx (this pulls the latest package):

npx -y @doitintl/doit-mcp-server@latest

3. When prompted, provide your DOIT_API_KEY in environment configuration if required by your setup, otherwise configure via your MCP client (Claude Desktop, Cursor, etc.).

Option B: Run from source (development)

1. Clone the repository:

git clone https://github.com/doitintl/doit-mcp-server
cd doit-mcp-server

2. Install dependencies:

yarn install

3. Build the project:

yarn build

4. Run the server:

node dist/index.js

Option C: Claude Desktop / Arial Desktop integration (example configuration)

1. In Claude Desktop App, configure your MCP server as:

{
  "mcpServers": {
    "doit_mcp_server": {
      "command": "npx",
      "args": ["-y", "@doitintl/doit-mcp-server@latest"],
      "env": {
        "DOIT_API_KEY": "your_doit_api_key"
      }
    }
  }
}

2. Restart Claude for Desktop after changing configuration to apply changes.

Environment variables and config tips:

• DOIT_API_KEY is required for authenticating with the DoiT API. Keep it secret and do not commit it to source control.
• CUSTOMER_CONTEXT is optional but may be required for certain Do’ers contexts; include it if your workflow needs a specific customer context.
• If using Claude Desktop or Cursor, ensure you restart the client after updating the MCP configuration for changes to take effect.
• If deploying via npx, you can pin to a specific version like @latest or a particular version tag to control updates.
• The MCP server exposes a broad set of tools (e.g., get_cloud_incidents, list_reports, run_query, get_report_results, list_invoices, get_invoice, list_allocations, create_allocation, etc.). Use the exact tool names when composing natural language queries or API calls.
• Ensure your DoiT API key has the minimum required permissions for the operations you intend to perform (incidents, anomalies, reports, invoices, etc.).