Thalovant MCP

Thalovant MCP runs locally from a Node.js package published to the npm registry: @thalovant/mcp-server version 0.6.2. 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 @thalovant/mcp-server@0.6.2.

Thalovant MCP runs locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: ghcr.io/thalovant/thalovant-mcp:0.6.2. The package starts a local server that speaks MCP over Streamable HTTP; the client then connects to it by URL.

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

{
  "mcpServers": {
    "thalovant-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@thalovant/mcp-server@0.6.2"
      ]
    }
  }
}

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