---
title: Connect Any MCP client to MyFeedIn
description: The generic configuration
url: https://myfeedin.co/documentation/mcp/any
type: agent-setup
source: MyFeedIn
---

# Connect Any MCP client to MyFeedIn

MyFeedIn is a remote MCP server over Streamable HTTP with OAuth sign-in (dynamic client registration). Any client that supports that only needs the URL.

## 1. Use the server URL

Transport: Streamable HTTP (sometimes labelled HTTP). Authentication: OAuth, no API key.

```
https://mcp.myfeedin.co
```

## 2. Pick your client's config shape

The key that holds the URL changes from one client to the next.

**Windsurf**

`mcp_config.json`
```
{
  "mcpServers": {
    "myfeedin": { "serverUrl": "https://mcp.myfeedin.co" }
  }
}
```

**Gemini CLI**

```
gemini mcp add --transport http myfeedin https://mcp.myfeedin.co
```

**Zed**

`settings.json`
```
"context_servers": {
  "myfeedin": { "url": "https://mcp.myfeedin.co" }
}
```

**stdio only**

```
{
  "mcpServers": {
    "myfeedin": {
      "command": "npx",
      "args": ["mcp-remote", "https://mcp.myfeedin.co"]
    }
  }
}
```

Raycast and n8n use a form: choose HTTP (n8n: HTTP Streamable) and OAuth with dynamic registration, then paste the URL. Use the stdio entry for clients that can only start a local process; it needs Node 18 or later.

## 3. Sign in when the client asks

Your browser opens on myfeedin.co. Sign in, choose the account or workspace to connect and the access level to grant.

## Check it worked

Ask your assistant to call the `get_connection_info` tool: it answers with the MyFeedIn account it is connected to.

## Troubleshooting

**mcp-remote keeps an old sign-in**

Delete `~/.mcp-auth` and restart your client to sign in again.

**Test the server without a client**

Run `npx @modelcontextprotocol/inspector`, choose Streamable HTTP and paste the URL.

---

Canonical version: https://myfeedin.co/documentation/mcp/any
Published by MyFeedIn (https://myfeedin.co). Cite the canonical URL.