MCP Server

Remote proxy for Model Context Protocol, allowing local-only clients to connect to remote servers using oAuth

Remote serverstreamable-http

What is the MCP MCP server?

MCP MCP server is a hosted integration for AI assistants that speak the Model Context Protocol. Remote proxy for Model Context Protocol, allowing local-only clients to connect to remote servers using oAuth.

What you get

Connect an MCP Client that only supports local (stdio) servers to a Remote MCP Server, with auth support:

Setting it up

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

What the assistant can call

Once MCP is connected, these are the calls the assistant has available:

  • Flags — You can specify multiple --ignore-tool flags to ignore different patterns. Examples: - delete* - ignores all tools starting with "delete" (e.g
  • CursorOfficial Docs. The configuration file is located at ~/.cursor/mcp.json
  • WindsurfOfficial Docs. The configuration file is located at ~/.codeium/windsurf/mcp_config.json

Configuration and credentials

You will need 7 environment variables: AUTH_TOKEN, AUTH_HEADER, HTTPS_PROXY, NO_PROXY, NODE_EXTRA_CA_CERTS, MCP_REMOTE_CLIENT_ID, MCP_REMOTE_CLIENT_SECRET. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Before you rely on it

  • Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the mcp mcp server does with a few real requests.

Choosing this one

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. MCP's toolset — Flags, Cursor, Windsurf — is a fair guide to whether it matches your workflow. It is maintained by geelen; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Available tools

ToolWhat it does
FlagsYou can specify multiple --ignore-tool flags to ignore different patterns. Examples: - delete* - ignores all tools starting with "delete" (e.g., deleteTask, deleteUser) - *account - ignores all tools ending with "account
Cursor[Official Docs](https://docs.cursor.com/context/model-context-protocol). The configuration file is located at ~/.cursor/mcp.json.
Windsurf[Official Docs](https://docs.codeium.com/windsurf/mcp). The configuration file is located at ~/.codeium/windsurf/mcp_config.json.

How to install the MCP MCP server

{
  "mcpServers": {
    "remote-example": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://remote.mcp.server/sse"
      ]
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
AUTH_TOKENCredential the server authenticates with.Yes
AUTH_HEADERConfiguration value read at startup.Optional
HTTPS_PROXYConfiguration value read at startup.Optional
NO_PROXYConfiguration value read at startup.Optional
NODE_EXTRA_CA_CERTSConfiguration value read at startup.Optional
MCP_REMOTE_CLIENT_IDConfiguration value read at startup.Optional
MCP_REMOTE_CLIENT_SECRETCredential the server authenticates with.Yes

Example prompts to try

  • Use MCP to Flags.
  • Use MCP to Cursor.
  • Use MCP to Windsurf.

Frequently asked questions

It connects MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 3 tools (Flags, Cursor, Windsurf) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with MCP directly.