report-badge-problem — Noonlaunch MCP Tool
report-badge-problem
(report badge problem) is one of 10 tools on the
Noonlaunch
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call report-badge-problem from your client
- Claude Code Noonlaunch report-badge-problem run in your project directory
- Claude Desktop Noonlaunch report-badge-problem ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Noonlaunch report-badge-problem ~/.cursor/mcp.json
- VS Code Noonlaunch report-badge-problem .vscode/mcp.json
- Zed Noonlaunch report-badge-problem ~/.config/zed/settings.json
- Windsurf Noonlaunch report-badge-problem ~/.codeium/windsurf/mcp_config.json
- Cline Noonlaunch report-badge-problem ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Noonlaunch report-badge-problem ~/.gemini/settings.json
- Grok Noonlaunch report-badge-problem .mcp.json (in your project root)
- ChatGPT Noonlaunch report-badge-problem Settings → Connectors → Advanced → Developer mode
- Claude.ai Noonlaunch report-badge-problem Settings → Connectors → Add custom connector
- LangChain Noonlaunch report-badge-problem pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcp https://noonlaunch.com/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 29 October 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.