get_provider_info_widget — Clutch.co MCP Resource
get_provider_info_widget
is one of 4 resources on the
Clutch.co
MCP server. Connect the server and your client can attach it as context.
by client
How to attach get_provider_info_widget from your client
- Claude Code Clutch.co Resource/get_provider_info_widget run in your project directory
- Claude Desktop Clutch.co Resource/get_provider_info_widget ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Clutch.co Resource/get_provider_info_widget ~/.cursor/mcp.json
- VS Code Clutch.co Resource/get_provider_info_widget .vscode/mcp.json
- Zed Clutch.co Resource/get_provider_info_widget ~/.config/zed/settings.json
- Windsurf Clutch.co Resource/get_provider_info_widget ~/.codeium/windsurf/mcp_config.json
- Cline Clutch.co Resource/get_provider_info_widget ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Clutch.co Resource/get_provider_info_widget ~/.gemini/settings.json
- Grok Clutch.co Resource/get_provider_info_widget .mcp.json (in your project root)
- ChatGPT Clutch.co Resource/get_provider_info_widget Settings → Connectors → Advanced → Developer mode
- Claude.ai Clutch.co Resource/get_provider_info_widget Settings → Connectors → Add custom connector
- LangChain Clutch.co Resource/get_provider_info_widget pip install langchain-mcp-adapters
Other resources on this server
Read from the server itself, by connecting to it and calling resources/list on 24 September 2026.
A listing does not declare its resources, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each resource's type and contents.