User Guide

Overview

Single Origin MCP Server

✨

New — The Single Origin MCP server is now available. Connect Claude Code, Cursor, or any MCP client.

The Single Origin MCP server exposes our query optimization data — query history, execution profiles, table metadata, similar-query clusters, and recommendations — as tools that any Model Context Protocol client can call. Drop it into Claude Code, Cursor, Claude Desktop, or your own agent, and your LLM can investigate slow queries and propose optimizations with grounded evidence instead of guesses.

Quickstart

1. Create a Personal Access Token. In the Single Origin web app, go to Account → Access Tokens, click Create Token, give it a name (e.g. Claude Code), and copy the Token ID and Token Secret from the dialog. The secret is shown only once.

2. Add the server to your MCP client config (Claude Code's .mcp.json, Cursor's MCP settings, or any other MCP-aware client). The Bearer value is <token_id>:<token_secret> — paste both values from the dialog, joined by a colon.

{
  "mcpServers": {
    "singleorigin": {
      "type": "http",
      "url": "https://mcp.singleorigin.tech/mcp",
      "headers": {
        "Authorization": "Bearer <token_id>:<token_secret>"
      }
    }
  }
}

3. Restart your client and run /mcp (Claude Code) or your client's equivalent to confirm the singleorigin server is connected.

What you can do

The server exposes 20 tools plus 4 built-in prompts, grouped by use case:

SectionToolsWhen to use
Recommendations4Surface and act on optimization opportunities Single Origin has already identified.
Query Inspection6Dig into a specific slow or expensive query — SQL, profile, fragments.
Similar Query Clusters4Find groups of structurally similar queries; fix one shape to fix dozens.
Tables & References4Look up schema, partitions, view definitions, resolve ambiguous table names, and list the queries hitting a table.
Table & Column Usage2See how columns are used over time and scan table storage/usage metrics — the signals behind cluster-key and clean-up decisions.
Built-in Prompts4Pre-written prompts that walk an agent through the most common workflows.

Authentication

The hosted server validates Bearer tokens via Personal Access Tokens (format <token_id>:<token_secret>), scoped to your user. All tool calls run with your identity — you only see data your workspace already grants you. Tokens can be revoked at any time from Account → Access Tokens.

Troubleshooting

  • /mcp returns a redirect the client can't follow. Some MCP clients (older FastMCP, langchain4j) fail on trailing slashes. Use https://mcp.singleorigin.tech/mcp exactly as documented — no trailing slash.
  • 401 Unauthorized. Confirm you copied both the Token ID and the Token Secret from the dialog, joined by a colon: <token_id>:<token_secret>. The most common mistake is using only the Token Secret. Also check that the token hasn't expired and the Authorization: Bearer ... header is being sent.
  • /mcp connects but no tools appear. Restart your client — tool discovery only runs on (re)connect.

Have a use case we should support? Drop us a note at [email protected].

Updated about 23 hours ago