DeepThonk

DeepThonk runs locally from a Node.js package published to the npm registry: deepthonk version 0.3.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx — the usual command is npx -y deepthonk@0.3.1. It reads these environment variables: DEEPSEEK_API_KEY (secret), OPENROUTER_API_KEY (secret), DEEPTHONK_API_KEY (secret), DEEPTHONK_CONFIG and DEEPTHONK_PROFILES_DIR; set them in the client's configuration for this server. Required arguments: serve-mcp.

In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):

{
  "mcpServers": {
    "deepthonk": {
      "command": "npx",
      "args": [
        "-y",
        "deepthonk@0.3.1"
      ],
      "env": {
        "DEEPSEEK_API_KEY": "<secret>",
        "OPENROUTER_API_KEY": "<secret>",
        "DEEPTHONK_API_KEY": "<secret>",
        "DEEPTHONK_CONFIG": "<value>",
        "DEEPTHONK_PROFILES_DIR": "<value>"
      }
    }
  }
}

Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect