border_debug_my_cors_error — Border MCP Prompt
border_debug_my_cors_error
is one of 1 prompt on the
Border
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke border_debug_my_cors_error from your client
- Claude Code Border Prompt/border_debug_my_cors_error run in your project directory
- Claude Desktop Border Prompt/border_debug_my_cors_error ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Border Prompt/border_debug_my_cors_error ~/.cursor/mcp.json
- VS Code Border Prompt/border_debug_my_cors_error .vscode/mcp.json
- Zed Border Prompt/border_debug_my_cors_error ~/.config/zed/settings.json
- Windsurf Border Prompt/border_debug_my_cors_error ~/.codeium/windsurf/mcp_config.json
- Cline Border Prompt/border_debug_my_cors_error ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Border Prompt/border_debug_my_cors_error ~/.gemini/settings.json
- Grok Border Prompt/border_debug_my_cors_error .mcp.json (in your project root)
- ChatGPT Border Prompt/border_debug_my_cors_error Settings → Connectors → Advanced → Developer mode
- Claude.ai Border Prompt/border_debug_my_cors_error Settings → Connectors → Add custom connector
- LangChain Border Prompt/border_debug_my_cors_error pip install langchain-mcp-adapters
Border also offers 2 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 14 November 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.