SHIP vs Timebook Cli — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
SHIP vs Timebook Cli
In-depth architectural comparison of the SHIP and Timebook Cli MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
SHIP
Workplace & Productivity · Remote HTTP/SSE
Quality: 52/100 (Good) | Auth: No auth required
Timebook Cli
Workplace & Productivity · Local stdio
Quality: 56/100 (Good) | Auth: No auth required
Verdict Summary: Choose SHIP if you need specialized Workplace & Productivity tools running via a hosted cloud SSE transport. Choose Timebook Cli if your workspace requires Workplace & Productivity integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
S
Choose SHIP when:
You need dedicated capabilities in the Workplace & Productivity domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Assign Linear, Jira or GitHub issues to an AI coding agent team that plans, builds, reviews, tests.
Official MCP server for Timebook — time tracking, invoicing, and bookkeeping for freelancers and solo LLCs. Manage clients and projects, start/stop timers, and log, update, and delete time entries. Runs locally via the @squidcode/timebook npm CLI or as a hosted OAuth endpoint at https://usetimebook.com/mcp. Published in the MCP registry as io.github.squidcode/timebook.
Category & Scope
Tools & Capabilities Breakdown
SHIP Tools (71)
start_mission
Give an issue that is already in your tracker to the agent team. By default, the mission starts at the Planner. With a plan, it starts at the Builder. With an open pull request, it starts at the Reviewer or the Tester
create_mission
Create the issue and start the mission in one call, for work that has no issue yet
send_mission_instruction
Tell an active mission what to change, or record a note for the agent that runs next
inspect_mission
The full record of a mission: its stages, verdicts, provenance and session logs
list_missions
The missions of your projects, with what each mission does now
get_mission
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
SHIP is categorized under Workplace & Productivity and uses a remote streaming HTTP/SSE transport. In contrast, Timebook Cli belongs to Workplace & Productivity using local stdio subprocess. Select SHIP when you need capabilities focused on workplace & productivity and Timebook Cli when you require tools for workplace & productivity.
One mission: its stage, its review and test results, its pull request, its agent runs and the run with the proof. With `view: "full"`, also its events and the outcome of each stage
pause_mission
Hold a mission before its next stage. The stage that runs now finishes
resume_mission
Continue a paused mission. When a checkpoint holds the mission, this approves the result of that stage
stop_mission
Stop a mission and every agent run of it. The pull request stays open
approve_mission_ceiling
Let a mission continue after it stops at its credit limit. The mission then uses more credits
merge_mission
Merge the pull request of a mission, with the merge method of the repository. On a merge conflict, SHIP starts the Builder to fix the conflict and merges later
decline_mission
Close the pull request of a mission without a merge
+59 more tools listed on main page
Timebook Cli Tools (10)
whoami
Current authenticated user (read-only)
list_projects
All projects in scope (read-only)
list_clients
All clients in scope (read-only)
get_active_timer
The running timer, or `null` (read-only)
start_timer
Start a timer on a project
stop_timer
Stop the running timer
log_time
Log a manual entry (`duration` OR `startTime`+`endTime`)
list_entries
Recent entries (default 50, max 500), project + date filters
update_entry
Edit one or more fields on an entry (description, duration, startTime, endTime, project, rate). Token must own the entry.
delete_entry
Delete an entry. Token must own it. Invoiced entries are locked.