# Border

> Border is a free MCP server for developer tools. Checks a cross-origin API call the way Chrome does and returns the headers that fix CORS. It runs as a hosted remote server, so there is nothing to install locally.

- **Kind:** MCP server
- **Pricing:** Free
- **Platforms:** Web, API
- **Website:** https://border.clawhard.com
- **MCP Registry name:** com.clawhard/border
- **Categories:** developer tools
- **Listing updated:** 2026-11-14

## About

When a request works in Postman or curl but fails in the browser, Border sends the real OPTIONS preflight to your API and applies the CORS rules as Chrome does. It reports whether a preflight is needed and why, then checks Access-Control-Allow-Origin, Allow-Credentials, the 2xx status, allowed methods and headers in order, and returns Chrome's exact error and the response headers to send. The site says its verdicts matched Chrome 156 on 56 test cases.

It is safe to aim at a live API: only OPTIONS plus GET and HEAD are sent for real, and key or cookie values are never sent, only their names. For localhost or staging, you paste curl -i output and use the headers-only check. It also flags servers that trust any origin with cookies and lists usual causes such as auth middleware rejecting OPTIONS, a redirect on the preflight, or a header added twice by the app and a proxy.

Two tools are exposed, and a JSON API with an OpenAPI description is available. No account or key is needed.

## Features

- **Real preflight:** Sends the actual OPTIONS request your browser would send.
- **Chrome-matched verdicts:** Applies Fetch standard rules as Chrome implements them.
- **Fix headers:** Gives the exact preflight and response headers to add for your origin.
- **Pasted curl mode:** Reads curl -i output when the API is on localhost or staging.
- **Credential safety:** Sends only names of auth headers, never key or cookie values.

## Good for

- Find why a browser blocks an API call that works in curl
- Fix auth middleware that rejects OPTIONS
- Check a wildcard origin that conflicts with cookies
- Let a coding agent verify its CORS fix on a live endpoint

## Install

### Claude Code (Terminal)

```sh
claude mcp add --transport http border https://border.clawhard.com/mcp
```

### Claude Desktop (Settings → Connectors → Add custom connector)

```sh
https://border.clawhard.com/mcp
```

### Cursor (~/.cursor/mcp.json)

```json
{
  "mcpServers": {
    "border": {
      "url": "https://border.clawhard.com/mcp"
    }
  }
}
```

### VS Code (.vscode/mcp.json)

```json
{
  "servers": {
    "border": {
      "type": "http",
      "url": "https://border.clawhard.com/mcp"
    }
  }
}
```

### Windsurf (~/.codeium/windsurf/mcp_config.json)

```json
{
  "mcpServers": {
    "border": {
      "serverUrl": "https://border.clawhard.com/mcp"
    }
  }
}
```

### Other clients (your client's MCP settings (most use this shape))

```json
{
  "mcpServers": {
    "border": {
      "type": "http",
      "url": "https://border.clawhard.com/mcp"
    }
  }
}
```

## Tools

- `border_check_cors`: Use when the user hits a CORS error ("blocked by CORS policy", "No 'Access-Control-Allow-Origin' header", "preflight", "Failed to fetch" from a frontend) or is about to call a public API from browser code (React, Next.js, Vue, a browser extension page) and asks whether it will work (signals: "CORS", "works in Postman but not in the browser", "preflight 401/404", "Access-Control-Allow-Headers", "wi
- `border_check_cors_headers`: Use when a CORS problem involves a server Border cannot reach (localhost, a dev or staging server, a private network, a custom port) or a POST, PUT, PATCH or DELETE whose real response needs checking, and the raw response headers are available from curl -i or the browser DevTools Network tab (signals: "here is the OPTIONS response", "my local API returns these headers", "CORS works on localhost bu

## FAQ

### Does it need an account?

No account, key or login is needed.

### Can I test localhost?

Yes, by pasting the status line and headers from curl -i, since Border cannot reach your machine.

### Will it send my API key?

No. Names of headers are enough and values are never sent.

### Why does preflight fail with 401 or 404?

Browsers do not send cookies or Authorization on OPTIONS, so servers must answer it before the auth check.

### Is Border free?

Yes. Border is free to use.

### How do I add Border to Claude Code?

Run this command in your terminal: claude mcp add --transport http border https://border.clawhard.com/mcp

### What are the best alternatives to Border?

The closest alternatives to Border are REA, Codebase Memory, GitHub, Serena MCP: the IDE for your agent and XERJ.

## Alternatives

- [REA](https://ai-powered.com/mcp/rea): REA is an open-source MCP server for developer tools.
- [Codebase Memory](https://ai-powered.com/mcp/codebase-memory): Codebase Memory is an open-source MCP server for knowledge and memory.
- [GitHub](https://ai-powered.com/mcp/github-2): GitHub is an open-source MCP server for developer tools.
- [Serena MCP: the IDE for your agent](https://ai-powered.com/mcp/serena-mcp-the-ide-for-your-agent): Serena MCP: the IDE for your agent is an open-source MCP server for developer tools.
- [XERJ](https://ai-powered.com/mcp/xerj): XERJ is an open-source MCP server for knowledge and memory.
- [Ouroboros](https://ai-powered.com/mcp/ouroboros): Ouroboros is an open-source MCP server for developer tools.
- [Claude Code Ultimate Guide](https://ai-powered.com/mcp/claude-code-ultimate-guide): Claude Code Ultimate Guide is an open-source MCP server for ai models and llm tooling.
- [Concord MCP](https://ai-powered.com/mcp/concord-mcp): Concord MCP is a freemium MCP server for developer tools.

---
Source: https://ai-powered.com/mcp/border
