tier_selector — agent ready kit MCP Tool
tier_selector
(tier selector) is one of 26 tools on the
agent ready kit
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call tier_selector from your client
- Claude Code agent ready kit tier_selector run in your project directory
- Claude Desktop agent ready kit tier_selector ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor agent ready kit tier_selector ~/.cursor/mcp.json
- VS Code agent ready kit tier_selector .vscode/mcp.json
- Zed agent ready kit tier_selector ~/.config/zed/settings.json
- Windsurf agent ready kit tier_selector ~/.codeium/windsurf/mcp_config.json
- Cline agent ready kit tier_selector ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI agent ready kit tier_selector ~/.gemini/settings.json
- Grok agent ready kit tier_selector .mcp.json (in your project root)
- ChatGPT agent ready kit tier_selector Settings → Connectors → Advanced → Developer mode
- Claude.ai agent ready kit tier_selector Settings → Connectors → Add custom connector
- LangChain agent ready kit tier_selector pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http agent-ready-kit https://mudko.com/api/mcp
Other tools on this server
- start_agent_ready_setup
- scan_site
- detect_platform
- run_site_audit
- validate_x402_endpoint
- verify_deployment
- analyze_business_vertical
- recommend_tool_names
- summarize_scan_for_humans
- request_quote
- refine_quote
- clarifying_questions
- verify_credentials
- create_proposal
- request_invoice
- get_pricing_tiers
- list_payable_apis
- start_checkout
- generate_files
- get_customer_files
- get_citation_report
- submit_lead
- create_bazaar_listing
- get_bazaar_listing_kit
- check_bazaar_listing
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.