TokenKnows MCP Server

What the code does

We read the source, 4 d ago · rules 995398eba69f

Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.

    for root, dirs, names in os.walk(watch_dir):

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add tokenknows -- uvx tokenknows-mcp

{
  "mcpServers": {
    "tokenknows": {
      "command": "uvx",
      "args": [
        "tokenknows-mcp"
      ]
    }
  }
}

[mcp_servers.tokenknows]
command = "uvx"
args = ["tokenknows-mcp"]

{
  "mcpServers": {
    "tokenknows": {
      "command": "uvx",
      "args": [
        "tokenknows-mcp"
      ]
    }
  }
}

{
  "servers": {
    "tokenknows": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "tokenknows-mcp"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: TOKENKNOWS_API_BASE (Self-hosted TokenKnows backend URL), TOKENKNOWS_API_TOKEN (API token (tkk_...) or JWT bearer for the backend; create one in the web UI under Project Settings - MCP Access (optional for default local deployments)), TOKENKNOWS_DEFAULT_PROJECT (Default project_id for event submission and distill), TOKENKNOWS_WEB_BASE (Web UI base URL used to build view_url links returned by distill/list tools (login required to open them)).