Back to home

Guide

Connect Muninn to Claude and ChatGPT

A five-minute setup for the Model Context Protocol

Muninn is a private notes workspace that speaks the Model Context Protocol (MCP) — the open standard AI assistants use to reach outside tools and data. Once you authorize Muninn as a remote MCP server, Claude and ChatGPT can read, search, and write your notes as you, without you copy-pasting content between apps.

This guide walks through both clients. It takes about five minutes and requires nothing on your local machine — Muninn is a remote MCP server, so there is no config file to edit and no proxy to run.

What is an MCP server?

The Model Context Protocol is an open specification (introduced by Anthropic in late 2024) that describes how AI assistants talk to external "tools" — a note store, a database, a calendar, a repo. An MCP server is any service that exposes tools over that protocol; the assistant is the MCP client. Muninn ships a hosted MCP server at your personal workspace URL, so any MCP-compatible client can connect over HTTPS after you sign in.

Before you start

  • A Muninn account. If you don't have one yet, sign up on the homepage.
  • Claude Desktop (macOS or Windows), or ChatGPT with connectors enabled.
  • About five minutes.

Step 1 — Copy your Muninn MCP URL

  1. Sign in at muninn.ferbutech.no.
  2. Open Connect an AI assistant from the sidebar.
  3. Copy the MCP endpoint URL shown at the top of that page — it looks like https://muninn.ferbutech.no/mcp. This is what you paste into Claude or ChatGPT.

The endpoint is public but every request is authorized through OAuth against your Muninn account, so tools only ever act as you.

Step 2 — Add Muninn to Claude Desktop

  1. Open Claude Desktop and go to Settings → Connectors.
  2. Click Add custom connector (Claude also calls this "Add remote MCP server" in some builds).
  3. Paste your Muninn MCP URL and give the connector a name — for example, "Muninn notes."
  4. Claude opens a browser window for OAuth. Sign in to Muninn and click Approve on the consent screen. Claude stores the token; you won't be asked again on this machine.
  5. Back in Claude, the connector shows the tools it discovered — search_notes, create_note, list_collections, and a few more. Enable the ones you want available in chats.

Step 3 — Add Muninn to ChatGPT

ChatGPT's MCP support is available on plans that expose the Connectors surface (Plus / Team / Enterprise at time of writing — check the ChatGPT settings screen for the current availability on your plan).

  1. In ChatGPT, open Settings → Connectors → Add.
  2. Choose Custom MCP server.
  3. Paste your Muninn MCP URL and give it a display name.
  4. ChatGPT opens Muninn's OAuth consent screen in a browser tab. Sign in and approve.
  5. The connector appears in your ChatGPT sidebar. Toggle it on in a new chat to let the model use its tools.

Step 4 — Verify the connection

Try one of these prompts in a new chat:

  • "List the last five notes in my Muninn workspace."
  • "Create a note in Muninn titled 'MCP is working' with today's date."
  • "Search my Muninn notes for anything about the Model Context Protocol."

The assistant should describe the tool call it wants to make, run it, and show the result. If it asks a follow-up first, that's normal — MCP tools are just capabilities; the model still decides when to use them.

Other MCP clients

Any client that implements the Streamable HTTP MCP transport can use Muninn — Codex, Cursor, Continue, Zed, and self-hosted agents work the same way. Point them at your Muninn MCP URL and complete OAuth once.

Troubleshooting

  • OAuth window closes with no result. Make sure you're signed in to Muninn in the same browser and retry — the consent flow needs a live Muninn session to attach the token to your account.
  • Claude / ChatGPT says "tool call failed." Open the connector's log in the client. A 401 means the token expired — remove the connector and add it again. A 4xx from Muninn usually means the tool arguments didn't match; try rephrasing.
  • The assistant doesn't seem to use the tools. Confirm the connector is toggled on for the current chat. Some clients scope tools per-conversation.

Privacy

Muninn's MCP server acts strictly as your signed-in account. Row- level security means an assistant can only see notes you can see, and tool calls are logged against your session. Muninn does not train on your content — see the Privacy Notice for the full details.

Questions or something broken? Head back to the homepage or contact support from your workspace.