Toggl MCP
Capped at 70: no passing tool call yet; the tests add up to 93. Why scores are capped
Test points add up to 93; the score is capped at 70 until a tool call passes. Not a quality or security rating. Methodology
Test points before the cap (93/100)
- Install20/20
- Handshake30/30
- Maintenance25/25
- Docs15/15
- License3/10
Tested @togglhq/mcp 1.13.121 (npm, published by Toggl's @togglhq scope). License field is UNLICENSED and we found no public source repo, so license and maintenance come from npm only.
Transport (tested 2026-10-31): stdio
Score 70/100 · Tools 54 · Token cost ~27,874 · Compare · Last tested 2026-10-31 · Version tested 1.13.121 · Package @togglhq/mcp
Summary: Toggl MCP completed an MCP handshake without credentials and exposed 54 tools.
Evidence summary
- Handshake
- pass
- Tools listed
- 54
- Context cost
- 27,874 model-visible tokens (name, description, inputSchema; tiktoken cl100k_base)
Extra payload (sent by the server, usually not read by the model): 1,693 tokens; raw tools/list total 29,567. Clients differ in what they forward. ranking · add up your servers' context cost - API key
- No key to connect (handshake passed)
- Tested
- 2026-10-31
Test results
| Test | Result | Points | Evidence |
|---|---|---|---|
| install | pass | 20 | npm install @togglhq/mcp (Node 20, Linux) succeeded in 3s. |
| handshake | pass | 30 | MCP initialize + tools/list over stdio succeeded with no credentials; 54 tools listed in 2.3s. |
| maintenance | pass | 25 | Latest release published 0 days before test. |
| docs | pass | 15 | README over 3,000 chars; install instructions present; mcpServers config example present. Automated check of the package's own README (README shipped in npm package). |
| license | partial | 3 | License not machine-detected as OSI (UNLICENSED). |
Local-model readiness
Schema context cost: ~27,874 tokens for 54 tools (119,333 bytes) · about 340% of an 8k context. Method: tiktoken cl100k_base over compact JSON of name+description+inputSchema (approximate).
Small-model friendly (schema heuristic, not a model result): unknown.
Small-model task runs: Not yet tested.
What we tested and what we didn't
Tested on 2026-10-31
- Install from the registry
- We connected with no credentials and asked for its tool list: it listed 54 tools (Method details: MCP
initializethentools/list) - Maintenance signals (last push, archived/deprecated status)
- Docs (README length, install and config example)
- License (OSI-approved or not)
- Tool-schema token cost (estimate)
Not tested
- Security: not audited (no code review, no permission or data-flow analysis)
- Real tasks (no functional task runs yet)
- Behaviour with real credentials or a real account
- Performance, rate limits or load
- Correctness of results beyond the listed tasks
Methodology: how we test. A high score means it installs and responds, not that it is safe to give it access to your data.
Known security issues
Not yet checked.
Monthly roundup: MCP security issues, October 2026.
Tool list changes
Baseline recorded from the 2026-10-31 test run; changes appear after the next test.
Snapshot hash (fingerprint of the tool list)
16829dffcc93: SHA-256 of the canonical tool names, descriptions and input schemas. If it changes, the tool list changed.
Raw test record (JSON)
{
"name": "@togglhq/mcp",
"version": "1.13.121",
"registry": "npm",
"status": "working",
"tested": "2026-10-31",
"tools_count": 54,
"tools_schema_tokens_est": 27874,
"deprecated": false,
"archived": null,
"tests": {
"install": [
"pass",
20,
"`npm install @togglhq/mcp` (Node 20, Linux) succeeded in 3s."
],
"handshake": [
"pass",
30,
"MCP `initialize` + `tools/list` over stdio succeeded with no credentials; 54 tools listed in 2.3s."
],
"maintenance": [
"pass",
25,
"Latest release published 0 days before test."
],
"docs": [
"pass",
15,
"README over 3,000 chars; install instructions present; `mcpServers` config example present. Automated check of the package's own README (README shipped in npm package)."
],
"license": [
"partial",
3,
"License not machine-detected as OSI (UNLICENSED)."
]
}
}Install
npx -y @togglhq/mcp
Tools listed
workspace-list, workspace-switch, profile-list, profile-switch, profile-remove, auth, logout, ai, alerts, archived-clients, archived-projects, archived-tasks, archived-time-entries, attachments, audit-log, capacities, clients, projects, tasks, custom-fields, customreports, designations, goals, milestones, organization, public-holidays, publicsharedreports, rates, recurring-budget-suggestions, reports, reportschedules, saved-views, search, sharedreports, statuses, subscriptions, tags, time-entries, time-off, timesheets
Quick config
{
"mcpServers": {
"toggl-mcp": {
"command": "npx",
"args": [
"-y",
"@togglhq/mcp"
]
}
}
}Add to config Opens the config generator with this server selected.
Setup
- Install. Run
npm install @togglhq/mcp(Node 20). This is the exact command we ran on 2026-10-31. - Configure. Add the mcpServers entry below to your MCP client config.
- Verify. Restart the client and check that tools/list returns tools (54 in our test).
{
"mcpServers": {
"toggl-mcp": {
"command": "npx",
"args": [
"-y",
"@togglhq/mcp"
]
}
}
}Test history
No dated events yet.
FAQ
Is Toggl MCP deprecated?
No. @togglhq/mcp was not deprecated or archived when we last tested it on 2026-10-31.
What replaces Toggl MCP?
Nothing; Toggl MCP is not deprecated as of 2026-10-31.
Does Toggl MCP need an API key?
No. It completed an MCP handshake with no credentials and listed 54 tools.
Embed the badge
Every tested server gets a free embeddable badge. It shows the current score and test date and expires after 90 days. Testing is free; payment never changes a score.