@orboto/mcp vs @tempo-ai/mcp
@orboto/mcp is an MCP server published by orboto. Marketplaces we read that list it: 1 (npm registry (MCP servers)). @tempo-ai/mcp is an MCP server published by @tempo-ai. Marketplaces we read that list it: 1 (npm registry (MCP servers)). As of our marketplace pass on 2026-11-07. 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
| Marketplace |  @orboto/mcp | |
|---|---|---|
| npm registry (MCP servers) | Listed Version: 0.238.0 Downloads/month (npm): 8 514 Downloads/week (npm): 2 342 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.0.140 Downloads/month (npm): 6 192 Downloads/week (npm): 2 725 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
| Fact | @orboto/mcp | @tempo-ai/mcp |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release (differs) | 2026-11-07 (better) | 2026-11-06 (worse) |
| Where it runs (differs) | On your machine (@orboto/mcp) | On your machine (@tempo-ai/mcp) |
| Transport | Not stated | Not stated |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/orboto/orboto-mcp | github.com/trytempo/tempo |
| Changes in the last 7 days | 4 | 4 |
| First seen | 2026-10-12 | 2026-10-12 |
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
@orboto/mcp
Model Context Protocol server for orboto - exposes tickets, projects, milestones, time, docs, primer-facts, alerts and absences as MCP tools for Claude Desktop / Cursor / Copilot Chat / any MCP-aware AI client.
@tempo-ai/mcp
Tempo MCP server for Claude Code, Codex, Cursor, and any other MCP-compatible host. One server exposing Tempo's issues, docs, comments, agents, scripts, Slack, Linear, and canvas toolsets.
How to run each
@orboto/mcp
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
@tempo-ai/mcp
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
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
Neither one's marketplaces publish the settings it asks for.
What it can do: @orboto/mcp · What it can do: @tempo-ai/mcp · Compare two other plugins
Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.