FeynmanLM Docs

Appearance

Setup MCP Server (Optional) ​

Most people don't need this

The easiest way to use your sources with AI is to drag & drop them directly from Studio into Claude, ChatGPT, Gemini, Grok, or Edison Scientific. The MCP server is an optional upgrade for power users who want a persistent connection — so your AI can search your full library and run Feynman sessions without dragging files each time.

FeynmanLM gives you a stable hosted MCP URL:

text
https://<your-id>.feynmanlm.com/mcp

Keep FeynmanLM open while using an external assistant. The app opens an outbound connection to the relay, which forwards authenticated MCP requests to the app.

Relay privacy

The Cloudflare relay is a trusted relay, not end-to-end encryption. FeynmanLM does not log or store MCP request or response bodies, but FeynmanLM-operated infrastructure forwards them in transit and is technically capable of observing them.

Connect ​

  1. Open FeynmanLM → Settings → External chatbot MCP.
  2. Wait for the status to show Connected.
  3. Copy the URL. Expand OAuth credentials if your client requires a client ID and secret.
  4. Add FeynmanLM to your assistant:

Claude normally needs only the URL and registers its own OAuth client automatically. Leave Claude's advanced OAuth fields blank unless the connection guide says otherwise.

What about Meta AI?

Meta's consumer chat app (meta.ai) does not currently support custom connectors or MCP servers, so FeynmanLM can't connect to it. You can still use Meta's Muse Spark model inside FeynmanLM: add a Meta Model API key under Settings → AI Models → API Keys and pick Meta as your chat or background-tasks provider.

Troubleshooting ​

Your AI says the server is offline: Make sure FeynmanLM is running and your Mac is awake. Open Studio → Connect MCP to verify the server status.

Claude shows {"error":"invalid_client"}: Remove the FeynmanLM connector from Claude and add it again with only the MCP URL. Leave Claude's advanced OAuth fields blank so Claude can use Dynamic Client Registration.

OAuth fails in another client: Double-check that you copied the current OAuth Client ID and OAuth Secret from Connect MCP, and that the OAuth endpoint URLs point at the same domain as your MCP URL.

Gemini OAuth never finishes: Gemini CLI needs to open your local browser and receive the OAuth callback on http://localhost:7777/oauth/callback. This won't work in a headless terminal.