Tidebase MCP Server

Inspect Tidebase agent runs, resolve approval gates, and trigger recovery from your AI assistant.

Remote serverstreamable-httpPython

What is the Tidebase MCP server?

Tidebase MCP server exists for a simple reason — assistants are far more useful when they can act on Tidebase directly instead of describing what you should do. Inspect Tidebase agent runs, resolve approval gates, and trigger recovery from your AI assistant.

What you get

Agent auth and credential brokering for AI agents, with checkpoints, queues, schedules, and approval gates. In your own Postgres.

  • per-agent identity instead of one shared API key
  • a vault for third-party secrets and OAuth tokens
  • a way to call APIs without handing the secret to the model
  • status tables for runs and steps
  • checkpoint blobs for partial progress
  • retry flags and manual-review states

Setting it up

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Configuration and credentials

You will need 7 environment variables: TIDEBASE_RUN_ID, TIDEBASE_API_KEY, GITHUB_TOKEN, TIDEBASE_URL, REVIEW_WEBHOOK_URL, TIDEBASE_WEBHOOK_SECRET, VITE_TIDEBASE_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Before you rely on it

  • Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the tidebase mcp server does with a few real requests.

Choosing this one

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. It is maintained by BlueprintLabIO; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

How to install the Tidebase MCP server

{
  "mcpServers": {
    "tidebase": {
      "command": "npx",
      "args": ["-y", "@tidebase/sdk"],
      "env": {
        "TIDEBASE_RUN_ID": "your-value",
        "TIDEBASE_API_KEY": "your-value",
        "GITHUB_TOKEN": "your-value",
        "TIDEBASE_URL": "your-value",
        "REVIEW_WEBHOOK_URL": "your-value",
        "TIDEBASE_WEBHOOK_SECRET": "your-value",
        "VITE_TIDEBASE_API_KEY": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
TIDEBASE_RUN_IDConfiguration value read at startup.Optional
TIDEBASE_API_KEYCredential the server authenticates with.Yes
GITHUB_TOKENCredential the server authenticates with.Yes
TIDEBASE_URLEndpoint or connection string the server talks to.Yes
REVIEW_WEBHOOK_URLEndpoint or connection string the server talks to.Yes
TIDEBASE_WEBHOOK_SECRETCredential the server authenticates with.Yes
VITE_TIDEBASE_API_KEYCredential the server authenticates with.Yes

Frequently asked questions

It connects Tidebase to MCP-compatible AI assistants such as Claude and Cursor. Instead of copying data back and forth by hand, the assistant works with Tidebase directly.