feedform_normalize_feed — Ouro Tools MCP Tool
feedform_normalize_feed
(feedform normalize feed) is one of 19 tools on the
Ouro Tools
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call feedform_normalize_feed from your client
- Claude Code Ouro Tools feedform_normalize_feed run in your project directory
- Claude Desktop Ouro Tools feedform_normalize_feed ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Ouro Tools feedform_normalize_feed ~/.cursor/mcp.json
- VS Code Ouro Tools feedform_normalize_feed .vscode/mcp.json
- Zed Ouro Tools feedform_normalize_feed ~/.config/zed/settings.json
- Windsurf Ouro Tools feedform_normalize_feed ~/.codeium/windsurf/mcp_config.json
- Cline Ouro Tools feedform_normalize_feed ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Ouro Tools feedform_normalize_feed ~/.gemini/settings.json
- Grok Ouro Tools feedform_normalize_feed .mcp.json (in your project root)
- ChatGPT Ouro Tools feedform_normalize_feed Settings → Connectors → Advanced → Developer mode
- Claude.ai Ouro Tools feedform_normalize_feed Settings → Connectors → Add custom connector
- LangChain Ouro Tools feedform_normalize_feed pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http ouro-tools https://ouro.tools/mcp
Other tools on this server
- droplink_publish_document
- droplink_read_document
- droplink_delete_document
- hookbox_create_inbox
- hookbox_read_inbox
- hookbox_delete_inbox
- chartlink_create_chart
- chartlink_get_chart
- cleanread_read_page
- sourcecheck_check_sources
- printkit_create_pdf
- tablelift_extract_tables
- collect_create_form
- collect_read_form
- collect_submit_response
- collect_read_responses
- collect_close_form
- collect_delete_form
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.