Ext Ops Panel
Open dashboard
Comparison

io.github.BlueprintLabIO/tidebase vs RoutineKit

io.github.BlueprintLabIO/tidebase is an MCP server published by BlueprintLabIO. Marketplaces we read that list it: 1 (Official MCP Registry). RoutineKit is an MCP server published by sjh9714. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplaceio.github.BlueprintLabIO/tidebaseRoutineKit
Official MCP Registry Listed
Version: 0.1.1
Downloads/month (npm): 156
Downloads/week (npm): 32
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Listed
Version: 0.2.0
Downloads/month (npm): 1 122
Downloads/week (npm): 359
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

io.github.BlueprintLabIO/tidebase vs RoutineKit
Factio.github.BlueprintLabIO/tidebaseRoutineKit
Marketplaces that list it11
Stars (GitHub)11
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@tidebase/mcp)On your machine (routinekit)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 02, secrets among them: 0
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/blueprintlabio/tidebasegithub.com/sjh9714/routinekit
Changes in the last 7 days (differs)40
First seen2026-10-112026-10-11

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

io.github.BlueprintLabIO/tidebase

In its own words, on Official MCP Registry:

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

RoutineKit

In its own words, on Official MCP Registry:

Capture tool workflows, save typed tools, and replay with human approval. Includes an MCP Apps UI.

How to run each

io.github.BlueprintLabIO/tidebase As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio tidebase -- npx -y @tidebase/mcp

RoutineKit As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio routinekit -- npx -y routinekit mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Only io.github.BlueprintLabIO/tidebase asks for

  • TIDEBASE_URL

Only RoutineKit asks for

  • ROUTINEKIT_CONFIG
  • ROUTINEKIT_HOME

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: io.github.BlueprintLabIO/tidebase · What it can do: RoutineKit · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built