nearwire
FREE TOOL

MCP config generator

Paste a remote MCP server URL, choose how it authenticates, and copy ready-to-use config for Claude, Claude Code, VS Code, Cursor, Codex, Gemini CLI or Windsurf. Everything runs in your browser.

Authentication
  1. Run the command, then start Claude Code, run /mcp, select the server and choose Authenticate.
  2. To share it with your team, commit the .mcp.json version instead. Each person signs in separately.
Terminal
claude mcp add --transport http nearwire https://nearwire.dev/mcp
.mcp.json (project scope)
{
  "mcpServers": {
    "nearwire": {
      "type": "http",
      "url": "https://nearwire.dev/mcp"
    }
  }
}

How remote MCP servers connect

A remote MCP server is a single HTTPS endpoint that speaks the Model Context Protocol over Streamable HTTP. Every client needs the same two things: the URL, and a way to authenticate. What differs is where each client keeps its config and what it calls the fields. Claude Code and VS Code use type: "http" with url, Cursor uses url alone, Gemini CLI uses httpUrl, Windsurf uses serverUrl, and Codex uses TOML.

Servers that implement MCP authorization let clients sign in with OAuth: the client discovers the server's authorization endpoints, registers itself, and opens a browser for you to approve access. That's why the OAuth snippets contain only a URL. For servers that use API keys, each client has its own way to read the key from an environment variable so it stays out of config files you might commit.

Troubleshooting

  • 405 or "SSE" errors: the server only supports Streamable HTTP. Make sure the client is set to HTTP rather than SSE, and that the URL doesn't end in /sse.
  • 401 Unauthorized: with OAuth, re-run the client's authenticate step. With an API key, check that the environment variable is set in the shell or app that starts the client. GUI apps often don't see variables set only in your terminal profile.
  • The server doesn't appear: config files are strict JSON, so check for trailing commas, and merge new servers into an existing mcpServers or servers object rather than adding a second one. Restart or reload the client afterwards.

FAQ

What's the difference between OAuth sign-in and an API key?

With OAuth, the client opens a browser window, you sign in to the server and approve access, and the client stores and refreshes the token. No secret goes in a config file. With an API key, you send a static Authorization header. That suits scripts, CI and clients without a browser, but you have to store and rotate the key yourself.

Does this work with local (stdio) MCP servers?

No. This generator is for remote servers reached over Streamable HTTP, which is how hosted MCP servers are usually offered. Local servers that you start with a command such as npx use a different config format with command and args.

Where should I keep the API key?

In an environment variable or your client's secret storage, not in a file you commit. The snippets reference an environment variable for every client that supports it, and VS Code prompts for the key and stores it securely.

Is anything I type sent to Nearwire?

No. The configs are generated in your browser, and the server URL and names you enter aren't sent anywhere.

The default URL is Nearwire's news search MCP server. See the MCP server docs for its tools, or the guide to adding live news search to Claude.