Dev Workflow MCP Server (programinglive)
Capped at 70: no passing tool call yet; the tests add up to 100. Why scores are capped
Test points add up to 100; the score is capped at 70 until a tool call passes. Not a quality or security rating. Methodology
Test points before the cap (100/100)
- Install20/20
- Handshake30/30
- Maintenance25/25
- Docs15/15
- License10/10
Tested npm @programinglive/dev-workflow-mcp-server 1.32.0 (MIT; the repo link in package metadata returned HTTP 404 on 2026-11-17 UTC and 2026-11-18 UTC; on 2026-11-19 UTC GitHub redirects it to the renamed repo programinglive/dev-workflow, which we link). Installed pinned with scripts off (npm --ignore-scripts) and launched: initialize and tools/list over stdio succeeded with no credentials and listed 58 tools (no tool annotations). Real calls: 0 of 2 real function calls passed. Calls need Sentry and task-tracker configuration. Core tools not tested: 70 cap.
Tool-call test (2026-11-18 UTC, direct MCP stdio client, no LLM): fail. 0 of 2 real function calls passed. Calls need Sentry and task-tracker configuration. Evidence: local test run, Nov 18, 2026 UTC.
Transport (tested 2026-11-18 UTC): stdio
Token cost (estimate): approx. 8736 tokens, cl100k estimate (58 tools, measured 2026-11-18 UTC, version 1.32.0). This is an estimate from our testing of the tool names, descriptions and input schemas, counted with cl100k_base.
Permissions: 11 read, 15 write (state-changing), 32 unclassified · Auth: API key · Rate limit: unknown · Pricing unit: unknown
Auth: API key. Rate limit: unknown. Pricing unit: unknown.
acknowledge_handover— unclassifiedacknowledge_instructions— unclassifiedacquire_release_lock— unclassifiedbuild_estimate— unclassifiedbuild_report— unclassifiedcheck_ready_to_commit— write (state-changing)checkpoint_task— unclassifiedcommit_and_push— write (state-changing)complete_focus— unclassifiedcomplete_task— unclassifiedcontinue_workflow— unclassifiedcreate_documentation— write (state-changing)create_feature_flow— write (state-changing)create_tests— write (state-changing)drop_task— write (state-changing)fetch_task— readforce_complete_task— unclassifiedget_current_focus— readget_integration_status— readget_sentry_issue— readget_workflow_status— readget_zettly_task_context— readhandoff_task— unclassifiedinventory_sentry_issues— write (state-changing)link_sentry_issue— write (state-changing)link_task_to_focus— unclassifiedlink_zettly_drawing— unclassifiedlist_active_sessions— readlist_sentry_issues— readmark_bug_fixed— write (state-changing)mark_dod_item— unclassifiedmark_plan_step— unclassifiednext_steps— unclassifiedperform_release— unclassifiedproject_summary— unclassifiedproject_summary_data— unclassifiedproject_summary_db— unclassifiedrecommend_mcp_tools— unclassifiedrecord_deployment— unclassifiedrefine_with_ai— write (state-changing)release_release_lock— unclassifiedreport_build_status— readrerun_workflow— unclassifiedresume_session— write (state-changing)run_full_workflow— unclassifiedrun_tests— unclassifiedsearch_project— readsecurity_audit— unclassifiedset_definition_of_done— write (state-changing)set_focus— write (state-changing)set_plan— write (state-changing)skip_release— unclassifiedskip_tests— unclassifiedstart_task— write (state-changing)sync_zettly_task— unclassifiedview_history— readwaive_documentation— unclassifiedwaive_dod_item— unclassified
listing-flags calls_need_key or auth_kind
Score 70/100 · Tools 58 · Token cost approx. 8,736 tokens · Compare · Last tested 2026-11-18 UTC · Version tested 1.32.0 · Package @programinglive/dev-workflow-mcp-server · Repo programinglive/dev-workflow
Summary: Dev Workflow MCP Server (programinglive) completed an MCP handshake without credentials and exposed 58 tools.
Evidence summary
- Handshake
- pass
- Tools listed
- 58
- Context cost
- approx. 8736 tokens, cl100k estimate (58 tools, measured 2026-11-18 UTC, version 1.32.0; an estimate) ranking · add up your servers' context cost
- API key
- Connects without a key; tool calls need one
- Tested
- 2026-11-18 UTC
Test results
| Test | Result | Points | Evidence |
|---|---|---|---|
| install | pass | 20 | npm install @programinglive/dev-workflow-mcp-server --ignore-scripts (Node v24.22.1, Linux) succeeded in 3s. |
| handshake | pass | 30 | MCP initialize + tools/list over stdio succeeded with no credentials; 58 tools listed in 2.5s. |
| maintenance | pass | 25 | Latest release published 2 days before test. |
| docs | pass | 15 | README over 3,000 chars; install instructions present; mcpServers config example present. Check of the package's own README (README shipped in npm package). |
| license | pass | 10 | MIT (OSI-approved). |
Local-model readiness
Token cost (estimate): approx. 8736 tokens, cl100k estimate for 58 tools · about 107% of an 8k context. This is an estimate from our testing (counted with cl100k_base).
Small-model friendly (schema heuristic, not a model result): unknown.
Not tested
Small-model task runs: Not yet tested.
What we tested and what we didn't
Tested on 2026-11-18 UTC
- Install from the registry
- We connected with no credentials and asked for its tool list: it listed 58 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)
- 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 giving it access to your data carries no risk.
Known security issues
Not yet checked.
Monthly roundup: MCP security issues, October 2026.
Tool list changes
Baseline recorded from the 2026-11-18 UTC test run; changes appear after the next test.
Snapshot hash (fingerprint of the tool list)
52ddce7d49d5: SHA-256 of the canonical tool names, descriptions and input schemas. If it changes, the tool list changed.
Raw test record (JSON)
{
"name": "@programinglive/dev-workflow-mcp-server",
"version": "1.32.0",
"registry": "npm",
"status": "working",
"tested": "2026-11-18",
"tools_count": 58,
"deprecated": false,
"archived": null,
"tests": {
"install": [
"pass",
20,
"`npm install @programinglive/dev-workflow-mcp-server --ignore-scripts` (Node v24.22.1, Linux) succeeded in 3s."
],
"handshake": [
"pass",
30,
"MCP `initialize` + `tools/list` over stdio succeeded with no credentials; 58 tools listed in 2.5s."
],
"maintenance": [
"pass",
25,
"Latest release published 2 days before test."
],
"docs": [
"pass",
15,
"README over 3,000 chars; install instructions present; `mcpServers` config example present. Check of the package's own README (README shipped in npm package)."
],
"license": [
"pass",
10,
"MIT (OSI-approved)."
]
},
"testedAt": "2026-11-18T04:17:50.629Z"
}Install
npx -y @programinglive/dev-workflow-mcp-server
Pin the version we tested
npx -y --ignore-scripts @programinglive/dev-workflow-mcp-server@1.32.0
tested 2026-11-18 UTC. Newer versions may differ and were not tested by us.
{
"mcpServers": {
"dev-workflow-mcp-server-programinglive": {
"command": "npx",
"args": [
"-y",
"@programinglive/dev-workflow-mcp-server@1.32.0"
]
}
}
}Tools listed
Showing 40 of 58 names: get_current_focus, set_focus, link_task_to_focus, complete_focus, get_zettly_task_context, inventory_sentry_issues, get_integration_status, list_sentry_issues, get_sentry_issue, link_zettly_drawing, link_sentry_issue, security_audit, search_project, start_task, refine_with_ai, set_definition_of_done, mark_dod_item, waive_dod_item, set_plan, mark_plan_step, resume_session, checkpoint_task, handoff_task, acknowledge_handover, fetch_task, mark_bug_fixed, acknowledge_instructions, create_feature_flow, create_tests, skip_tests, run_tests, create_documentation, waive_documentation, check_ready_to_commit, commit_and_push, perform_release, record_deployment, acquire_release_lock, release_release_lock, skip_release.Show all 58 names
get_current_focus, set_focus, link_task_to_focus, complete_focus, get_zettly_task_context, inventory_sentry_issues, get_integration_status, list_sentry_issues, get_sentry_issue, link_zettly_drawing, link_sentry_issue, security_audit, search_project, start_task, refine_with_ai, set_definition_of_done, mark_dod_item, waive_dod_item, set_plan, mark_plan_step, resume_session, checkpoint_task, handoff_task, acknowledge_handover, fetch_task, mark_bug_fixed, acknowledge_instructions, create_feature_flow, create_tests, skip_tests, run_tests, create_documentation, waive_documentation, check_ready_to_commit, commit_and_push, perform_release, record_deployment, acquire_release_lock, release_release_lock, skip_release, complete_task, next_steps, force_complete_task, drop_task, get_workflow_status, view_history, continue_workflow, rerun_workflow, run_full_workflow, project_summary, project_summary_data, project_summary_db, list_active_sessions, build_report, build_estimate, sync_zettly_task, recommend_mcp_tools, report_build_status
Quick config
{
"mcpServers": {
"dev-workflow-mcp-server-programinglive": {
"command": "npx",
"args": [
"-y",
"@programinglive/dev-workflow-mcp-server"
]
}
}
}Add to config Opens the config generator with this server selected.
Setup
- Install. Run
npm install @programinglive/dev-workflow-mcp-server --ignore-scripts(Node v24.22.1). This is the exact command we ran on 2026-11-18 UTC. - Configure. Add the mcpServers entry below to your MCP client config.
- Verify. Restart the client and check that tools/list returns tools (58 in our test).
{
"mcpServers": {
"dev-workflow-mcp-server-programinglive": {
"command": "npx",
"args": [
"-y",
"@programinglive/dev-workflow-mcp-server"
]
}
}
}Test history
- 2026-11-18 UTC: New
FAQ
Is Dev Workflow MCP Server (programinglive) deprecated?
No. Dev Workflow MCP Server (programinglive) was not deprecated or archived when we last tested it on 2026-11-18 UTC.
What replaces Dev Workflow MCP Server (programinglive)?
Nothing; Dev Workflow MCP Server (programinglive) is not deprecated as of 2026-11-18 UTC.
Does Dev Workflow MCP Server (programinglive) need an API key?
It connects and lists 58 tools without a key, but its tool calls need one.
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.