border_check_cors_headers — Border MCP Tool
border_check_cors_headers
(border check cors headers) is one of 2 tools on the
Border
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call border_check_cors_headers from your client
- Claude Code Border border_check_cors_headers run in your project directory
- Claude Desktop Border border_check_cors_headers ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Border border_check_cors_headers ~/.cursor/mcp.json
- VS Code Border border_check_cors_headers .vscode/mcp.json
- Zed Border border_check_cors_headers ~/.config/zed/settings.json
- Windsurf Border border_check_cors_headers ~/.codeium/windsurf/mcp_config.json
- Cline Border border_check_cors_headers ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Border border_check_cors_headers ~/.gemini/settings.json
- Grok Border border_check_cors_headers .mcp.json (in your project root)
- ChatGPT Border border_check_cors_headers Settings → Connectors → Advanced → Developer mode
- Claude.ai Border border_check_cors_headers Settings → Connectors → Add custom connector
- LangChain Border border_check_cors_headers pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http border https://border.clawhard.com/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 14 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.