thinking-mcp
Related Servers
Alternatives to thinking-mcp
No user-submitted related servers found.
Related Servers
- AlicenseCqualityAmaintenanceSteers a coding model through a 0→10 step reasoning protocol by injecting a directive into the system prompt before inference, and hooks refusals to retry the request with a reframe and rotate to an open-weight model. Exposes tools, prompts, and resources for traffic-light state, history, health, and configuration over stdio, Streamable HTTP, or a Cloudflare Worker.14MIT
- FlicenseNot gradedqualityBmaintenanceEnables MCP-compliant agents to run deterministic iterative self-critique and reflection loops that autonomously evaluate and revise outputs to repair logic defects, test failures, and hallucinations. It connects via JSON-RPC stdio with no external dependencies, supporting fast local execution and agent integration.7-
- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents to control real interactive shells, REPLs, and TUIs over stdio, supervise other agents, surface approval prompts, and verify outcomes without auto-approving or mistaking timeouts for success.MIT
- AlicenseAqualityAmaintenanceA machine-enforced workflow protocol for AI coding agents that eliminates false progress. Tasks require verifiable evidence to close, while decisions, assumptions, and open questions persist in a versioned reasoning graph for seamless agent handoffs. Designed to keep deep, long-running projects coherent across sessions, agents, and months.3930AGPL 3.0
- AlicenseBqualityAmaintenanceLocal-first Agent OS that wraps Claude Code, Codex CLI, and other coding agents in a replayable Seed → Ledger → Runtime contract, driven by an interview → seed → execute → evaluate → evolve workflow loop.3428,941 PyPI6,291MIT
- AlicenseAqualityAmaintenanceZero-dependency token optimizer, test-failure triage gate, and System 1.5 semantic guardrail for AI coding agents. Intercepts compiler errors, missing dependencies, and doom loops in < 500µs.670 PyPI12MIT
TDQS
Scored across 6 tools
Each tool maps to a distinct step in a session lifecycle (list, open, submit, status, verify, verify_submit), and descriptions clearly separate think (build scaffold) from think_verify (independent refutation). The only real overlap is think_submit vs think_verify_submit, both of which accept JSON, but their pairing with the parent tool is spelled out.
All tools use snake_case with a consistent think_ prefix and a predictable verb_noun shape (think_list_templates, think_submit, think_status, think_verify, think_verify_submit). The single bare 'think' is the primary entry action and does not break readability.
Six tools is well-scoped for a thinking-session protocol: one entry point plus list, submit, status, verify, and verify_submit. Each tool earns its place with no redundancy.
The lifecycle is largely covered: discovery, session creation, submission, inspection, independent verification, and verdict submission. Minor gaps exist, e.g. no explicit session abort/close or list-sessions operation, but agents can work around these.