Back to home DETAILED GUIDE

Install the Followr MCP, step by step.

From a clean machine to a working connector in five minutes. Pick the path that matches your comfort with the terminal. The end result is the same: Claude (or any MCP client) talking to your Followr workspace.

01 · PREREQUISITES

Three things before you start.

If any of these are missing the install will fail. Check them now, save yourself five minutes of debugging later.

1

Node.js 20 or newer

Open a terminal and run node --version. If you see v20 or higher, you are set. If the command is missing or the version is older, install the LTS build from nodejs.org and restart your terminal.

2

A Followr plan with API access

API keys are only available on plans that include API access, or on plans with the API key add-on enabled. If your current plan does not include it, the MCP will install fine but every call will return 401. Check or upgrade your plan in your Followr account before you continue.

3

A Followr API key

A long string Followr generates for you. The MCP reads it at startup and uses it to authenticate every call. We walk through generating one in the next section.

02 · API KEY

Generate your API key.

One API key works for every workspace under your account. Generate it once, paste it into your AI client, forget it exists.

  1. 1

    Sign in to Followr.

    Use the account whose workspaces you want to expose to the AI client. The API key will inherit your permissions.

  2. 2

    Click your profile picture in the top-left and select API Keys from the dropdown menu.

    Shortcut: open the API Keys settings directly.

  3. 3

    Click Generate, name it, copy the API key.

    Name it something you will recognize later, like "Claude MCP" or "My laptop". Copy the API key immediately. Followr shows the full string only once.

Treat the API key like a password. Never paste it into a chat, an issue, a screenshot, or a Slack thread. Paste it only into your local terminal or a config file on your own machine. If an API key leaks, revoke it from the same screen and generate a new one.
PICK ONE

The next two sections are alternatives. You only do one.

Pick the option that matches the AI client you actually use. Section 03 (Option A) is for Claude Code (terminal). Section 04 (Option B) is for Claude Desktop (app). Doing both is not necessary and not recommended.

03 · OPTION A recommended

Claude Code (CLI).

If you use Claude Code, this is the option for you. One terminal command, one verification, done. Skip Option B below.

  1. 1

    Open your terminal and paste this command.

    Replace PASTE_YOUR_API_KEY_HERE with the API key you copied. Then press Enter.

    claude mcp add --scope user followr --env 'FOLLOWR_API_TOKEN=PASTE_YOUR_API_KEY_HERE' -- npx -y @followr/mcp
    The single quotes matter. Followr API keys contain a pipe character (|). Without single quotes the shell interprets the pipe as a pipe operator, truncates the API key, and every call returns 401.
  2. 2

    Verify the connection.

    Run this and confirm both lines:

    claude mcp get followr
    • Status: ✓ Connected
    • Scope: User config

    If you see Scope: Local config instead, the MCP is only visible inside the directory where you ran the command. Remove it (claude mcp remove followr) and re-run the install with --scope user.

  3. 3

    Try a real prompt.

    Inside Claude Code, ask "List my Followr workspaces" or "Show me the next scheduled posts". If you get real data back, you are done.

04 · OPTION B alternative

Claude Desktop.

Only follow this option if you did NOT already do Option A above. A JSON config file lives somewhere on your machine. We open it, paste a block, save it, and restart Claude. No terminal required if you use the in-app shortcut.

Step 1. Open the config from inside the app.

  1. 1

    Open Claude Desktop.

    If you don't have it yet, download it from claude.ai/download and sign in with your Anthropic account. The web app at claude.ai cannot run local MCPs, so the desktop app is required for this path.

  2. 2

    Click your profile picture in the bottom-left corner of the Claude window.

    A menu opens.

  3. 3

    Go to Settings → Developer → Edit Config.

    That opens the folder containing claude_desktop_config.json. Double-click the file to open it in your default text editor (TextEdit, Notepad, VS Code, whatever you have). If the file does not exist yet, create one inside that folder with that exact name.

Step 2. Paste the Followr block.

If the file is empty, paste exactly this:

{
  "mcpServers": {
    "followr": {
      "command": "npx",
      "args": ["-y", "@followr/mcp"],
      "env": {
        "FOLLOWR_API_TOKEN": "PASTE_YOUR_API_KEY_HERE"
      }
    }
  }
}

If the file already has other MCPs configured, only add the "followr" block inside "mcpServers", separated by a comma from the previous block:

{
  "mcpServers": {
    "some-other-mcp": {
      "command": "...",
      "args": ["..."]
    },
    "followr": {
      "command": "npx",
      "args": ["-y", "@followr/mcp"],
      "env": {
        "FOLLOWR_API_TOKEN": "PASTE_YOUR_API_KEY_HERE"
      }
    }
  }
}
The comma is required. If you forget it between MCP blocks the JSON becomes invalid and Claude won't load any connector, not just Followr. When in doubt paste the whole file into jsonlint.com.

Step 3. Paste your API key and save the file.

Replace PASTE_YOUR_API_KEY_HERE with the API key you copied from Followr. Keep the double quotes around it. The result looks like:

"FOLLOWR_API_TOKEN": "1234|abcdEFGHijklMNOP..."

Save the file with Cmd+S (macOS) or Ctrl+S (Windows).

Step 4. Fully close Claude Desktop. Then open it again.

Closing only the window is NOT enough. Claude keeps running in the background and will not reload the config file until it's fully closed. After closing the window, follow the instructions for your OS below, then open the app again from scratch.
  • macOS: Menu bar → Claude → Quit Claude (or press Cmd+Q). Then reopen from the Dock or Spotlight.
  • Windows: Right-click the Claude icon in the system tray (next to the clock) → Quit. Then open Claude again from the Start menu.
  • Linux: Close the app fully, kill any lingering process if needed, then open it again.

Step 5. Confirm the MCP is connected.

Inside a new chat, click the tools or plug icon below the message box. You should see followr listed. The first time the connector loads, expect a 5 to 10 second delay while npx downloads @followr/mcp. Subsequent launches are instant.

Alternative: locate the config file manually.

If the in-app shortcut doesn't work for any reason, the file lives at one of these paths. Open it directly with your editor.

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json
  • Linux: ~/.config/Claude/claude_desktop_config.json

On macOS, the fastest way to reach that folder is Finder → Go → Go to Folder (Cmd+Shift+G), then paste ~/Library/Application Support/Claude/.

05 · TROUBLESHOOTING

Common errors and fixes.

Every call returns 401 Unauthorized.

Either the API key was truncated by the shell (missing single quotes on Claude Code), there is an extra space when you pasted it, or your plan does not include API access. Re-check the API key character by character and verify your plan inside Followr.

The followr connector doesn't appear in Claude Desktop.

Almost always invalid JSON. Paste the full file into jsonlint.com. The most frequent cause is a missing comma between MCP blocks. Also confirm you fully quit Claude (Cmd+Q on macOS, system tray on Windows), not just closed the window.

"command not found: npx".

Node.js is not installed or not on your PATH. Install LTS from nodejs.org, restart your terminal, restart your AI client, try again.

First call hangs for several seconds.

Normal on first run. npx is downloading the package (~25 MB cached in ~/.npm/_npx/). Every launch after the first is instant. To pre-warm, run npx -y @followr/mcp --version || true in your terminal.

claude.ai (web) does not list local MCPs.

Expected. The browser version of claude.ai only supports remote HTTP connectors, not local stdio servers. For now, use Claude Desktop, Claude Code, or any other client listed on the home page.

API key leaked. What now?

Open the API Keys settings, revoke the leaked API key, generate a new one, update your config file or rerun claude mcp add, restart your AI client.

All set. What next?

Open Claude and ask it to list your next scheduled posts. If it answers with real data, the connector is live.

Want to peek at the API behind it? Community docs →