us_equivalent — FineRx MCP Prompt

us_equivalent is one of 3 prompts on the FineRx MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke us_equivalent from your client

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

Other prompts on this server

• price_and_card
• prescription_help

FineRx also offers 5 resources — data you attach as context, where a prompt is something you run.

Read from the server itself, by connecting to it and calling prompts/list on 24 September 2026. A listing does not declare its prompts, 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 prompt's arguments.