create_deadline_tracker — compliance radar MCP Tool Mutating
create_deadline_tracker
(create deadline tracker) is one of 4 tools on the
compliance radar
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call create_deadline_tracker from your client
- Claude Code compliance radar create_deadline_tracker run in your project directory
- Claude Desktop compliance radar create_deadline_tracker ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor compliance radar create_deadline_tracker ~/.cursor/mcp.json
- VS Code compliance radar create_deadline_tracker .vscode/mcp.json
- Zed compliance radar create_deadline_tracker ~/.config/zed/settings.json
- Windsurf compliance radar create_deadline_tracker ~/.codeium/windsurf/mcp_config.json
- Cline compliance radar create_deadline_tracker ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI compliance radar create_deadline_tracker ~/.gemini/settings.json
- Grok compliance radar create_deadline_tracker .mcp.json (in your project root)
- ChatGPT compliance radar create_deadline_tracker Settings → Connectors → Advanced → Developer mode
- Claude.ai compliance radar create_deadline_tracker Settings → Connectors → Add custom connector
- LangChain compliance radar create_deadline_tracker pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http compliance-radar https://compliance.dropwatchhq.com/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.