rank_providers_for_workflow — agentery MCP Tool
rank_providers_for_workflow
(rank providers for workflow) is one of 19 tools on the
agentery
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call rank_providers_for_workflow from your client
- Claude Code agentery rank_providers_for_workflow run in your project directory
- Claude Desktop agentery rank_providers_for_workflow ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor agentery rank_providers_for_workflow ~/.cursor/mcp.json
- VS Code agentery rank_providers_for_workflow .vscode/mcp.json
- Zed agentery rank_providers_for_workflow ~/.config/zed/settings.json
- Windsurf agentery rank_providers_for_workflow ~/.codeium/windsurf/mcp_config.json
- Cline agentery rank_providers_for_workflow ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI agentery rank_providers_for_workflow ~/.gemini/settings.json
- Grok agentery rank_providers_for_workflow .mcp.json (in your project root)
- ChatGPT agentery rank_providers_for_workflow Settings → Connectors → Advanced → Developer mode
- Claude.ai agentery rank_providers_for_workflow Settings → Connectors → Add custom connector
- LangChain agentery rank_providers_for_workflow pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http agentery https://agentery.com/api/mcp
Other tools on this server
- research_capability
- search_providers
- find_market
- compare_providers
- get_price_index
- price_benchmark
- get_price_index_history
- market_gaps
- suggest_alternatives
- demand_signals
- report_outcome
- get_provider_profile
- get_provider
- market_report
- create_custom_benchmark
- get_custom_benchmark
- update_custom_benchmark
- delete_custom_benchmark
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.