Getting Started

Getting Started

Warning

Deprecated. This package is archived. Takt now hosts a remote MCP server with OAuth 2.1 — no API key to manage. Connect with claude mcp add --transport http takt https://taktlytics.com/mcp and see the MCP docs.

Requirements

• Node.js ≥ 18
• A self-hosted Takt instance
• A Takt API key (Dashboard → Settings → API keys). Keys are single-site bound, with the permissions matching the tools you want:
  • stats:read — every reporting tool
  • sites:read — list_sites

Claude Desktop / Claude Code

Add the server to your MCP config (claude_desktop_config.json, or .mcp.json for Claude Code):

{
  "mcpServers": {
    "takt": {
      "command": "npx",
      "args": ["-y", "@vskstudio/takt-mcp"],
      "env": {
        "TAKT_BASE_URL": "https://takt.example.com",
        "TAKT_API_KEY": "takt_sk_…",
        "TAKT_ORG": "my-org"
      }
    }
  }
}

Restart the client; the takt tools appear in the tool list.

Any MCP client

The package ships a takt-mcp binary that speaks MCP over stdio:

TAKT_BASE_URL=https://takt.example.com TAKT_API_KEY=takt_sk_… npx @vskstudio/takt-mcp

Flags:

takt-mcp --version
takt-mcp --help

Verify it works

Ask your agent something like "How many visitors did example.com get this week?" (using your key's own domain). If you set TAKT_ORG, the agent can also read the takt://sites resource to discover your site.

Next: Tools · Configuration · Troubleshooting