MCP Clients
Supported MCP clients and configuration for Dark Matter.
Overview
The DMTR MCP server works with any MCP-compatible client. Officially tested clients include Claude Desktop and Cursor. Custom clients that implement the MCP protocol can also connect. Configuration varies by client; all require the server command and API key (or credentials path).
Claude Desktop
Add the DMTR MCP server to claude_desktop_config.json. Specify the server command (e.g., npx /mcp-server or path to binary) and set DMTR_API_KEY in env. Claude Desktop connects via stdio. Restart Claude Desktop after config changes. See the Quickstart for a minimal config example.
Cursor
Add the DMTR MCP server in Cursor Settings > MCP. Provide the server command and environment variables. Cursor supports stdio and HTTP transports. The server appears in the MCP tools list; use it in the Cursor composer or chat to query Dark Matter.
Custom clients
Custom clients must implement the MCP protocol (resources, tools, prompts). Connect to the DMTR server via stdio (spawn process, read/write stdin/stdout) or HTTP (if server is deployed remotely). Discover tools and resources via the MCP initialization handshake. Pass DMTR_API_KEY in the server's environment.
Configuration
Common config keys: command (server executable or script), args (optional arguments), env (environment variables including DMTR_API_KEY). For HTTP, use url instead of command. Never commit API keys to version control; use env vars or secret managers.