Connect Taufinity Studio to your AI assistant

Taufinity Studio speaks the Model Context Protocol. Connect any MCP-compatible AI assistant — Claude, Cursor, VS Code Copilot, ChatGPT — and ask questions in plain language. The assistant generates the queries, calls the right tools, and returns results.

Server URL: https://studio.taufinity.io/mcp

Pick your client

Client	Status	CLI one-liner	Page
Claude Code	Stable	taufinity mcp login --init --global	Setup →
Claude Desktop	Stable	taufinity mcp install	Setup →
Cursor	Stable	manual config (see page)	Setup →
VS Code Copilot	Stable	manual config (see page)	Setup →
GitHub Copilot CLI	Stable	manual config (see page)	Setup →
Gemini CLI	Stable	manual config (see page)	Setup →
ChatGPT Custom Connector	Coming soon	(OAuth-based, paste connector URL)	Preview →

What you can do

Capability	Example prompt
Query dashboards	"Show me last month's top results"
Run natural-language data queries	"Which post had the most reactions in Q1?"
Send messages through your widgets	"Ask my support widget what the most common questions are"
Inspect knowledge base content	"What does our knowledge base say about returns?"
List widgets, conversations, dashboards	"Which widgets are configured?"

The full tool catalogue (~70 tools across data, dashboards, widgets, and knowledge files) is documented on each per-client page under Available tools.

Why MCP

MCP is an open protocol from Anthropic that lets AI assistants call external tools and read external data without custom integrations. One server, every client. See modelcontextprotocol.io for the protocol spec.

How authentication works today

All clients in v1 use bearer-token authentication. Sign in with taufinity auth login and run the appropriate install command for your client (see table above). To print your current token manually use taufinity auth token. Tokens can be revoked at any time from Studio → Settings → API Keys.

OAuth 2.1 with PKCE and Dynamic Client Registration is shipping next (Track 3). It will replace the manual paste flow for ChatGPT and become the recommended path for all clients. Existing bearer-token configs will keep working — see the ChatGPT page for the OAuth flow.

Alternative setup methods

The Taufinity CLI is the fastest path, but every client also accepts a plain JSON config block. Here's a comparison of all approaches:

Taufinity CLI (recommended)

taufinity auth login               # device-code flow, stores token
taufinity mcp login --init --global  # Claude Code
taufinity mcp install              # Claude Desktop

Pros: one command, token auto-written, server entry auto-named, config file location handled for you. Cons: requires the taufinity CLI installed (Go binary, ~10 MB). See CLI install.

Direct HTTP config (manual)

Every MCP-capable client accepts a plain url + headers block. Add this to your client's config file:

{
  "mcpServers": {
    "taufinity-studio": {
      "type": "http",
      "url": "https://studio.taufinity.io/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_TAUFINITY_TOKEN"
      }
    }
  }
}

Retrieve your token with taufinity auth token, or copy it from Studio → Settings → API Keys.

Pros: no extra tools, works on any OS, survives CLI updates without re-running install. Cons: manual token rotation — when your token is revoked you must edit the file by hand.

Client	Config file location
Claude Code	~/.claude/mcp.json (global) or <project>/.mcp.json
Claude Desktop	~/Library/Application Support/Claude/claude_desktop_config.json (macOS)
Cursor	~/.cursor/mcp.json (user) or <project>/.cursor/mcp.json
VS Code Copilot	<project>/.vscode/mcp.json (use key servers, not mcpServers)
GitHub Copilot CLI	~/.config/copilot/mcp-config.json
Gemini CLI	~/.gemini/settings.json (use key httpUrl, not url)

npx mcp-remote (stdio bridge)

For clients that only accept stdio transports (older Claude Desktop builds, mcp-inspector, CI scripts):

npx -y mcp-remote https://studio.taufinity.io/mcp \
  --header "Authorization: Bearer YOUR_TAUFINITY_TOKEN"

Or in a config file:

{
  "mcpServers": {
    "taufinity": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote",
        "https://studio.taufinity.io/mcp",
        "--header", "Authorization: Bearer YOUR_TAUFINITY_TOKEN"
      ]
    }
  }
}

Pros: works with stdio-only clients, no CLI install needed, available anywhere Node.js is present. Cons: requires Node.js 18+, downloads mcp-remote on first run (~5 s), adds an extra process hop, token in plain text in the config.

taufinity mcp stdio (self-contained bridge)

If you have the Taufinity CLI but need a stdio bridge (no Node.js):

{
  "mcpServers": {
    "taufinity-studio": {
      "command": "taufinity",
      "args": ["mcp", "stdio"]
    }
  }
}

Pros: no Node.js dependency, reads credentials from taufinity auth login automatically, single binary. Cons: requires the taufinity CLI binary in $PATH.

Need help?

• Reach out to your implementation partner for credentials, scopes, and configuration help.
• Email [email protected] for product issues.
• For the security model, see Data Governance and API Keys.