Skip to main content

Connections

The DoiT MCP server uses the standard MCP protocol. Connect with either of the supported methods below. Use the method your client supports. The client examples show how common AI tools connect.

Required permissions​

  • Your DoiT plan must include access to the DoiT API. Without that access, authorization may fail or requests may return authorization errors. If you're unsure whether your plan includes access to the DoiT API, contact your DoiT account manager or review your DoiT Cloud Intelligence plan.

  • Authentication depends on the connection method. Remote Streamable HTTP uses your signed-in DoiT account. Local stdio uses a personal API token provided as DOIT_API_KEY.

  • The DoiT MCP server tools map to the DoiT Cloud Intelligence API. Each DoiT API operation enforces its own permissions. Scope the API token (or ensure your user has) the permissions needed for the tools you use.

Prerequisites​

  • For remote (Streamable HTTP) connections, a supported web browser to complete the DoiT sign-in flow when you connect.

  • For local (stdio) connections, Node.js must be on your machine so npx can run @doitintl/doit-mcp-server, and a personal API token available as DOIT_API_KEY. Local stdio does not use the browser sign-in flow.

Connection methods​

Remote (Streamable HTTP)​

Your client connects over HTTPS to:

https://mcp.doit.com/mcp

  • Authentication: When you connect, your browser opens a DoiT sign-in page. Sign in with your DoiT account and select Allow access on the DoiT consent screen.

  • Configuration: In your MCP client, add a remote / HTTP server entry and set the server URL to https://mcp.doit.com/mcp. Field names vary by client (for example url, httpUrl, or Remote MCP server URL).

Local (stdio)​

Your client launches the published package on your machine using standard input/output (stdio):

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

  • Authentication: Local stdio authenticates with a personal API token. Set DOIT_API_KEY in the client configuration env block (or in your shell environment before the client starts the server). It does not use the browser OAuth sign-in flow.

  • Configuration: Typically you set a command of npx, args of ["-y", "@doitintl/doit-mcp-server@latest"], and an env entry for DOIT_API_KEY in an mcp.json, config.toml, or equivalent file. Exact keys depend on the client.

Legacy SSE (deprecated)​

The endpoint https://mcp.doit.com/sse remains available only so already connected clients keep working. It is deprecated, does not expose the full tool set, and must not be used for new setups. Use Streamable HTTP or stdio instead.

Client examples​

Local and desktop clients generally support both stdio and Streamable HTTP. Browser-based clients are typically Streamable HTTP only.

ClientstdioStreamable HTTP
ChatGPT (web)NoYes
Claude (Desktop / Code / web connectors)YesYes
CursorYesYes
VS Code (Copilot MCP)YesYes
Codex (CLI / IDE)YesYes
Gemini CLIYesYes

Each page walks through at least one worked example. For method details, see Connection methods.

Use your AI tool for connection

If you prefer, you can ask your AI tool to help connect to the DoiT MCP server in your environment.

Example prompt: Connect me to the DoiT MCP server at https://mcp.doit.com/mcp (Streamable HTTP) or via npx -y @doitintl/doit-mcp-server@latest with DOIT_API_KEY (stdio). I'm using <tool name>, <OS>, and <shell>. Walk me through configuration and authorization. If any command fails, help me troubleshoot and continue.

Last updated on