Skip to main content

Connect any other MCP client (manual setup: Zed, Devin, Gemini CLI, servers)

Server address, sign-in details and API key setup for MCP clients without their own guide, CI jobs and servers.

Written by Thomas Lucy

Any MCP client that supports remote servers over Streamable HTTP can use Enrow. Point it to https://mcp.enrow.io/mcp: a client that supports sign-in (OAuth) finds everything else on its own. Where sign-in isn't possible, such as in CI jobs, on servers or in Gemini CLI, use your Enrow API key.

You find these details in Enrow too: go to Integrations in the left menu, click the MCP tab, then click Configure on the Manual setup card.

Server

  • Server URL: https://mcp.enrow.io/mcp

  • Transport: Streamable HTTP

Sign-in (OAuth)

Enrow follows the MCP authorization specification, with dynamic client registration. Apps on your computer sign in through a redirect to 127.0.0.1, localhost or [::1], on any port.

  • Discovery: https://mcp.enrow.io/.well-known/oauth-protected-resource

  • Authorization server: https://api.enrow.io

  • Client registration: https://api.enrow.io/register

  • PKCE: S256

Zed

Add this to your Zed settings, then click Authenticate next to enrow in the Agent Panel settings.

"context_servers": {
  "enrow": {
    "url": "https://mcp.enrow.io/mcp"
  }
}

Devin (Desktop and CLI)

Devin Desktop and the CLI share the same configuration. Add Enrow from a terminal:

devin mcp add enrow https://mcp.enrow.io/mcp

Then sign in. Your browser opens: sign in to Enrow if asked, then click Allow.

devin mcp login enrow

API key (CI jobs and servers)

Where sign-in isn't possible, send your Enrow API key in this header. The server also reads it from the x-enrow-api-key header.

Authorization: Bearer <your API key>

To test it, run this command. The answer shows your credit balance, at no cost.

curl -sS https://mcp.enrow.io/mcp -H "Authorization: Bearer <your API key>" -H "Content-Type: application/json" -H "Accept: application/json, text/event-stream" -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"get_account_info","arguments":{}}}'

On the Manual setup page, these blocks already contain your API key. Click the eye icon to show it, or the copy icon to copy the block with your key.

The API key block of the Manual setup page, with its show and copy icons

The API key requires a paid plan. Keep it secret: anyone who has it can spend your credits. A connection made with the API key is not listed in Profile > Applications. To cut it, reset your API key on the API page. Everything else that uses the key will then need the new one.

Gemini CLI

Gemini CLI requires an iss parameter that Enrow doesn't send yet, so it connects with your API key:

gemini mcp add --scope user --transport http --header "Authorization: Bearer <your API key>" enrow https://mcp.enrow.io/mcp

In a team

If you belong to an Enrow team and you are not its owner, connect the apps on your computer with your team's API key, as shown above. Admins see the key on the API page. Members see it once the owner or an admin has given them API access. Only the team owner can reset it.

Related articles

Did this answer your question?