Jobctl vs Timebook Cli
A side-by-side look at the Jobctl and Timebook Cli MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Jobctl for workplace & productivity work over a hosted endpoint; choose Timebook Cli for workplace & productivity as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Jobctl when
- You need dedicated capabilities in the Workplace & Productivity domain.
- You prefer a remote HTTP/SSE transport.
- You have the keys it needs:
JOBCTL_TOKEN. - You want tools like
add_application, list_applications, get_application.
Choose Timebook Cli when
- You need dedicated capabilities in the Workplace & Productivity domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
TIMEBOOK_API_URL, TIMEBOOK_WEB_URL. - You want tools like
whoami, list_projects, list_clients.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Workplace & Productivity | Workplace & Productivity |
| Quality signal | 52/100 · Good | 56/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars |
Tools & capabilities
Jobctl tools 10
add_applicationCreate an application from structured fields or a raw string ("Bosch, Tech Lead, prio A, due friday") with deterministic parsing and duplicate detectionlist_applicationsFilter by status, priority, text query and saved viewsget_applicationFull detail: timeline, contacts, interviews, attachmentsupdate_applicationStatus, priority, salary, next action and moreadd_noteAppend a note to the application timelinelog_interviewSchedule or debrief interviews with attendees and linksget_dueOverdue and upcoming next actionsget_plannedAgenda for today / tomorrow / this weekattach_analysisAttach a single replaceable company-analysis markdown (max 100 kB)attach_fileAttach CV or cover letter files (base64)
Timebook Cli tools 10
whoamiCurrent authenticated user (read-only)list_projectsAll projects in scope (read-only)list_clientsAll clients in scope (read-only)get_active_timerThe running timer, or `null` (read-only)start_timerStart a timer on a projectstop_timerStop the running timer
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Jobctl
{
"mcpServers": {
"dmytrorybka-jobctl": {
"url": "https://app.jobctl.app/mcp"
}
}
}
Timebook Cli
{
"mcpServers": {
"squidcode-timebook-cli": {
"command": "npx",
"args": [
"-y",
"@squidcode/timebook"
],
"env": {
"TIMEBOOK_API_URL": "YOUR_TIMEBOOK_API_URL_HERE",
"TIMEBOOK_WEB_URL": "YOUR_TIMEBOOK_WEB_URL_HERE"
}
}
}
}
Frequently asked questions
Jobctl is categorized under Workplace & Productivity and uses a remote HTTP/SSE transport. Timebook Cli belongs to Workplace & Productivity and uses a local stdio subprocess. Pick Jobctl for workplace & productivity work and Timebook Cli for workplace & productivity.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Jobctl has no declared pricing — check the project's own site. Timebook Cli has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add dmytrorybka-jobctl and squidcode-timebook-cli as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Jobctl has a quality signal of 52/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Timebook Cli has 56/100 (Good) with 2 views, 0 installs and 2 GitHub stars.