submit_sipflow_feedback — Sipflow MCP Tool
submit_sipflow_feedback
(submit sipflow feedback) is one of 22 tools on the
Sipflow
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call submit_sipflow_feedback from your client
- Claude Code Sipflow submit_sipflow_feedback run in your project directory
- Claude Desktop Sipflow submit_sipflow_feedback ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Sipflow submit_sipflow_feedback ~/.cursor/mcp.json
- VS Code Sipflow submit_sipflow_feedback .vscode/mcp.json
- Zed Sipflow submit_sipflow_feedback ~/.config/zed/settings.json
- Windsurf Sipflow submit_sipflow_feedback ~/.codeium/windsurf/mcp_config.json
- Cline Sipflow submit_sipflow_feedback ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Sipflow submit_sipflow_feedback ~/.gemini/settings.json
- Grok Sipflow submit_sipflow_feedback .mcp.json (in your project root)
- ChatGPT Sipflow submit_sipflow_feedback Settings → Connectors → Advanced → Developer mode
- Claude.ai Sipflow submit_sipflow_feedback Settings → Connectors → Add custom connector
- LangChain Sipflow submit_sipflow_feedback pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http sipflow https://mcp.sipflow.dev/mcp
Other tools on this server
- search_sip_docs
- lookup_response_code
- lookup_sip_header
- detect_sip_stack
- detect_sip_vendor_from_config
- minimize_sip_trace
- render_sip_ladder
- sip_ladder_example
- lint_sip_request
- parse_sip_message
- diff_sip_messages
- review_sip_config
- webrtc_sip_checklist
- parse_sdp
- compare_sdp_offer_answer
- validate_stir_shaken_identity
- stir_attestation_explainer
- validate_e164_number
- troubleshoot_response_code
- dns_diagnose_sip_target
- fetch_sipflow_share
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.