report_bug — DNIT: Identificação de Condutor Infrator MCP Tool
report_bug
(report bug) is one of 7 tools on the
DNIT: Identificação de Condutor Infrator
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call report_bug from your client
- Claude Code DNIT: Identificação de Condutor Infrator report_bug run in your project directory
- Claude Desktop DNIT: Identificação de Condutor Infrator report_bug ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor DNIT: Identificação de Condutor Infrator report_bug ~/.cursor/mcp.json
- VS Code DNIT: Identificação de Condutor Infrator report_bug .vscode/mcp.json
- Zed DNIT: Identificação de Condutor Infrator report_bug ~/.config/zed/settings.json
- Windsurf DNIT: Identificação de Condutor Infrator report_bug ~/.codeium/windsurf/mcp_config.json
- Cline DNIT: Identificação de Condutor Infrator report_bug ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI DNIT: Identificação de Condutor Infrator report_bug ~/.gemini/settings.json
- Grok DNIT: Identificação de Condutor Infrator report_bug .mcp.json (in your project root)
- ChatGPT DNIT: Identificação de Condutor Infrator report_bug Settings → Connectors → Advanced → Developer mode
- Claude.ai DNIT: Identificação de Condutor Infrator report_bug Settings → Connectors → Add custom connector
- LangChain DNIT: Identificação de Condutor Infrator report_bug pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http dnit_identificacao_condutor-mcp https://api.mcp.ai/p_dnit_identificacao_condutorOther 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.