Skip to main content
Claude Desktop talks to MCP servers via stdio. Since MagicPost MCP is HTTP, we use the open-source mcp-remote bridge to convert stdio ↔ HTTP locally.

​
Prerequisites

  • macOS, Windows or Linux with Claude Desktop installed
  • Node.js 18+ available on your PATH (npx needs it)
  • A MagicPost API key — see creating a key

​
Configure

1

Locate the config file

2

Add the MCP server block

Open the file (create it if missing) and add a mcpServers entry:
When you create the key from Settings → API & MCP, the dialog includes a copy-paste-ready version of this exact snippet with the token already filled in.
3

Fully quit and relaunch Claude Desktop

On macOS, Cmd+Q (not just close window). MCP servers are only loaded at startup.

​
Verify

After relaunch, open a new conversation and click the tools indicator in the input bar. You should see magicpost listed with 25 tools available. Try:
Claude will call list_my_posts and read back what’s coming up.

​
Troubleshooting

  1. Open the Claude Desktop logs (Preferences → Developer → Open log directory)
  2. Look for mcp.log or claude_mcp.log
  3. Common causes:
    • JSON syntax error in claude_desktop_config.json — validate it with python -m json.tool claude_desktop_config.json
    • npx not on PATH — install Node via nvm or homebrew
    • Network blocked — confirm you can curl https://mcp.magicpost.in/.well-known/oauth-protected-resource
The PAT is invalid or revoked. Generate a new one from Settings → API & MCP and replace it in the config.
The MCP bridge might have crashed silently. Restart Claude Desktop. If the issue persists, run the bridge manually to see its output:

​
Privacy

mcp-remote runs on your machine and forwards calls to mcp.magicpost.in. Your token never leaves your machine via a third party. The MagicPost MCP server validates it and acts on your behalf.