Inspect Tidebase agent runs, resolve approval gates, and trigger recovery from your AI assistant.
MCPpedia last refreshed this data
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"io-github-blueprintlabio-tidebase-2": {
"args": [
"-y",
"@tidebase/sdk"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Agent auth and credential brokering for AI agents, with checkpoints, queues, schedules, and approval gates. In your own Postgres.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y '@tidebase/sdk' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked @tidebase/sdk against OSV.dev.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in ai-ml
Dynamic problem-solving through sequential thought chains
Persistent memory using a knowledge graph
Workspace template + MCP server for Claude Code, Codex CLI, Cursor & Windsurf. Multi-agent knowledge engine (ag-refresh / ag-ask) that turns any codebase into a queryable AI assistant.
Compact, efficient, and extensible long-term memory for LLM agents.
MCP Security Weekly
Get CVE alerts and security updates for io.github.BlueprintLabIO/tidebase and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Agent auth and credential brokering for AI agents, with checkpoints, queues, schedules, and approval gates. In your own Postgres.
Quick start · API · Storage contract · Scope

Tidebase gives your AI agents an identity and a vault. When an agent calls an API, the call goes through Tidebase, which injects the credential, so the agent and the model never see the key. You can scope it, audit it, and revoke it.
It also keeps the durable parts: checkpoints, live state, queues, schedules, and approval gates, all in your own Postgres. Your code still runs in your app, worker, or job process; Tidebase does not run it. So "this run died at step 7, is it safe to rerun?" has an answer, and "the agent has my GitHub token in plaintext" stops being true.
Docs: https://tidebase.dev · Community: Discord · For AI assistants: /llms.txt
Agent products usually grow the same operational plumbing:
Tidebase packages that layer around your existing code, plus a credential broker so agents act on real services without holding the keys. It does not run your code (your runtime stays yours), and it is not an LLM proxy or a hosted worker runtime.
Fastest path (no Node needed), prebuilt server image:
docker compose --profile server up -d # Postgres + ghcr.io/blueprintlabio/tidebase on :7373
Then point any SDK at http://localhost:7373 (npm i @tidebase/sdk or pip install tidebase).
Dev setup (server + Studio from source):
Start Postgres:
docker compose up -d postgres
Install dependencies:
pnpm install
Run the server and Studio:
pnpm dev
Run the example workflow:
pnpm example
Force a failure after two completed checkpoints:
FAIL_WRITE=1 pnpm example
Copy the run id from Studio or the API, then resume:
TIDEBASE_RUN_ID=run_xxx pnpm example
The plan and fetch-sources steps are returned from checkpoints. Only write-report executes again.
Give an agent its own identity, vault a third-party secret, and let the agent call the API without ever hold