get_provider — r4ck MCP Tool Read-only

get_provider (get provider) is one of 23 tools on the r4ck MCP server. Connect the server and your client discovers it on the handshake.

by client

How to call get_provider from your client

Claude Code r4ck get_provider run in your project directory
Claude Desktop r4ck get_provider ~/Library/Application Support/Claude/claude_desktop_config.json
Cursor r4ck get_provider ~/.cursor/mcp.json
VS Code r4ck get_provider .vscode/mcp.json
Zed r4ck get_provider ~/.config/zed/settings.json
Windsurf r4ck get_provider ~/.codeium/windsurf/mcp_config.json
Cline r4ck get_provider ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
Gemini CLI r4ck get_provider ~/.gemini/settings.json
Grok r4ck get_provider .mcp.json (in your project root)
ChatGPT r4ck get_provider Settings → Connectors → Advanced → Developer mode
Claude.ai r4ck get_provider Settings → Connectors → Add custom connector
LangChain r4ck get_provider pip install langchain-mcp-adapters

Fastest route

claude mcp add --transport http r4ck https://r4ck.dev/mcp

Other tools on this server

search_servers
cheapest
parse_query
get_server
compare_servers
facets
list_providers
deals
stats
save_search
saved_searches
delete_saved_search
redeem_code
list_invites
create_invite
list_webhooks
create_webhook
update_webhook
delete_webhook
test_webhook
rotate_webhook_secret
webhook_deliveries

This list was read from the server itself, by connecting to it and calling tools/list on 11 November 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.

r4ck MCP server