---
title: Connect Claude Code to MyFeedIn
description: One command in your terminal
url: https://myfeedin.co/documentation/mcp/claude-code
type: agent-setup
source: MyFeedIn
---

# Connect Claude Code to MyFeedIn

No key to paste. The first time Claude Code calls MyFeedIn, your browser opens, you sign in and choose the account it may use and what it may do: read only, read and draft, or full access.

## 1. Add the server

Run this from any directory. Local keeps it to you in the current project, Project writes a `.mcp.json` your team shares through git, User follows you into every project.

**Local**

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

**Project**

```
claude mcp add --transport http --scope project myfeedin https://mcp.myfeedin.co
```

**User**

```
claude mcp add --transport http --scope user myfeedin https://mcp.myfeedin.co
```

`--transport http` matters: without it Claude Code expects a local process, not a remote server.

## 2. Sign in when asked

Inside Claude Code, run `/mcp`, pick `myfeedin` and choose Authenticate. Your browser opens on myfeedin.co: sign in and approve. From a plain shell, `claude mcp login myfeedin` does the same.

## Check it worked

```
claude mcp list
```

`myfeedin` should show as connected. Or ask Claude something only your account can answer: "list my last 5 LinkedIn posts". `claude mcp get myfeedin` explains a failed connection and `claude mcp remove myfeedin` undoes the setup.

## Troubleshooting

**/mcp shows "Needs authentication"**

Select the server in `/mcp` and authenticate again. Over SSH, use `claude mcp login myfeedin --no-browser` and open the printed link on your machine.

**I added it with an Authorization header**

Remove the header. With a header set, Claude Code does not fall back to the sign-in flow and reports a failed connection.

---

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