MCP server

The Single Origin MCP server lets an AI assistant look up your query history, job health, table metadata, recommendations and measured savings. It speaks the Model Context Protocol, so any MCP client can use it. Your assistant can then explain a slow job, check a proposed fix or confirm a saving with evidence instead of guesses.

Quickstart

1. Create an access token. In the Single Origin web app, open Account → Access Tokens and click Create Token. Give it a name, such as Claude Code. Copy the Token ID and the Token Secret from the dialog. The secret is shown only once.

2. Add the server to your MCP client. The MCP URL is https://<company>-api.singleorigin.tech/mcp, where <company> is your company's name as given by Single Origin. The Authorization header is Bearer <token_id>:<token_secret>: both values from the dialog, joined by a colon.

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

3. Restart your client and check that the singleorigin server is connected. In Claude Code, run /mcp.

4. Ask a question. For example: "Which of my jobs cost more than usual yesterday?" or "Walk me through my top recommendation."

Clients

The server uses the streamable HTTP transport. Any client that supports it and lets you set a request header works.

The steps for each client are in the tabs under step 2 above.

Authentication

• Every request carries Authorization: Bearer <token_id>:<token_secret>.
• Tokens belong to your user. Tools that change something, such as a recommendation's status, record the change as made by you.
• A token can have an expiry date. An expired token is rejected. The web app warns you before your token expires.
• You can have up to 2 active tokens at a time. To rotate, create a new token, switch your clients to it, then delete the old one.
• Delete a token at any time from Account → Access Tokens.

What your agent can do

To run a ready-made workflow, see Built-in prompts.

The server has more tools than these pages cover. Your MCP client lists them all, each with its own description.

Engine-specific tools

Some tools read data that only one engine provides. Tools marked Snowflake only are served only to workspaces with Snowflake data. On other engines they are not listed.

Costs and savings

Every tool that returns or takes a cost ends its description with a line naming the unit those costs are in. Your agent reads that line; check it there if you need the unit.

Write tools

Most tools only read. The tools that change something are marked Write tool on their page. MCP clients usually ask you to approve each call to them.

Troubleshooting

• 401 Unauthorized. Check that you copied both the Token ID and the Token Secret, joined by a colon: <token_id>:<token_secret>. The most common mistake is sending only the secret. Also check that the token hasn't expired and that the client sends the Authorization: Bearer ... header.
• The client can't follow a redirect. Some MCP clients fail on a trailing slash. Use https://<company>-api.singleorigin.tech/mcp exactly, with no trailing slash.
• Connected, but no tools appear. Restart your client. Tool discovery runs only when the client connects.
• A tool on these pages is missing. It may be engine-specific (see above). Ask [email protected].
• A tool returns {"error": ...}. Tools return errors as data, with a sentence saying what went wrong, such as an unknown id or an ambiguous table name. Your agent can usually correct the call from the message.

Have a use case we should support? Write to [email protected].