check_commitment — knowledge base MCP Tool Read-only
check_commitment
(check commitment) is one of 17 tools on the
knowledge base
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call check_commitment from your client
- Claude Code knowledge base check_commitment run in your project directory
- Claude Desktop knowledge base check_commitment ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor knowledge base check_commitment ~/.cursor/mcp.json
- VS Code knowledge base check_commitment .vscode/mcp.json
- Zed knowledge base check_commitment ~/.config/zed/settings.json
- Windsurf knowledge base check_commitment ~/.codeium/windsurf/mcp_config.json
- Cline knowledge base check_commitment ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI knowledge base check_commitment ~/.gemini/settings.json
- Grok knowledge base check_commitment .mcp.json (in your project root)
- ChatGPT knowledge base check_commitment Settings → Connectors → Advanced → Developer mode
- Claude.ai knowledge base check_commitment Settings → Connectors → Add custom connector
- LangChain knowledge base check_commitment pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http knowledge-base https://api.tunnelpowered.com/api/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.