thing

thing runs locally from a Node.js package published to the npm registry: @unravel-tech/thing version 0.10.0. 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 @unravel-tech/thing@0.10.0. It reads these environment variables: THING_TOKEN (required, secret) and THING_SERVER; set them in the client's configuration for this server. Required arguments: mcp.

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

{
  "mcpServers": {
    "thing": {
      "command": "npx",
      "args": [
        "-y",
        "@unravel-tech/thing@0.10.0"
      ],
      "env": {
        "THING_TOKEN": "<secret>",
        "THING_SERVER": "<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