Ghosty Notes ships a local MCP server called meeting-mcp. Point your coding agent at it and the agent can search your meetings, read transcripts, and pull out action items while you work.

It talks over stdio. There is no port, no socket and no server to sign in to. Your agent starts the process, reads from it, and stops it again. Nothing is sent anywhere.

This works on every plan, including Free.

Before you start, record at least one meeting. An empty vault gives your agent nothing to find. See your first recording.

The two values you need

Every setup below needs the same two strings.

1. The path to the server binary. It sits inside the app bundle:

/Applications/Ghosty Notes 0.2.3.app/Contents/MacOS/meeting-mcp

The version number is part of the folder name, so yours may differ. Get the exact path for your install from the file described next.

2. The path to your vault. By default:

/Users/YOUR-NAME/Library/Application Support/ghosty-notes

If you moved your notes folder in Settings, use that folder instead.

Let the app fill both in for you

On every start, Ghosty Notes writes an AGENTS.md file to the top of your vault with both paths already filled in for your machine. Open it and copy from there rather than typing paths by hand:

open "$HOME/Library/Application Support/ghosty-notes/AGENTS.md"

If you wrote your own AGENTS.md in that folder, the app leaves it alone and writes nothing. Only a file the app itself created is ever refreshed.

Claude Code

One command. Substitute your own two paths:

claude mcp add meeting-notes -- \
  "/Applications/Ghosty Notes 0.2.3.app/Contents/MacOS/meeting-mcp" \
  "/Users/YOUR-NAME/Library/Application Support/ghosty-notes"

Both paths contain spaces, so the quotes are required.

Check it registered:

claude mcp list

You should see meeting-notes. Start a session and ask it something like “search my meetings for the auth rewrite”.

To scope the server to one project instead of your whole account, put a project config file named .mcp.json at the project root:

{
  "mcpServers": {
    "meeting-notes": {
      "command": "/Applications/Ghosty Notes 0.2.3.app/Contents/MacOS/meeting-mcp",
      "args": ["/Users/YOUR-NAME/Library/Application Support/ghosty-notes"]
    }
  }
}

Cursor

Cursor reads the same shape of file. Use ~/.cursor/mcp.json for every project, or a mcp.json inside the project’s own .cursor folder for just that one:

{
  "mcpServers": {
    "meeting-notes": {
      "command": "/Applications/Ghosty Notes 0.2.3.app/Contents/MacOS/meeting-mcp",
      "args": ["/Users/YOUR-NAME/Library/Application Support/ghosty-notes"]
    }
  }
}

Restart Cursor. The server appears under Settings, MCP. If it shows a red dot, open troubleshooting.

Codex

Codex keeps its MCP servers in ~/.codex/config.toml:

[mcp_servers.meeting-notes]
command = "/Applications/Ghosty Notes 0.2.3.app/Contents/MacOS/meeting-mcp"
args = ["/Users/YOUR-NAME/Library/Application Support/ghosty-notes"]

Other agents

The app’s own MCP settings screen (Settings, AI, MCP) carries ready-made blocks for Claude Desktop, ChatGPT, Hermes Agent and Grok Build. Those blocks are generated by the same code that writes AGENTS.md, so the two can never disagree.

Any other MCP host works too. It is a standard stdio server: give it the binary as the command and the vault path as the single argument.

Some hosts ask for one command line rather than separate command and argument fields. In that case use both paths, each in quotes, on one line:

"/Applications/Ghosty Notes 0.2.3.app/Contents/MacOS/meeting-mcp" "/Users/YOUR-NAME/Library/Application Support/ghosty-notes"

What your agent can now do

Seven tools. Five only read. Two can write, and both stop to ask you first.

See the full tool reference, or jump to prompts that work.

After an app update

The binary path contains the app version, so a config you saved under an older version can point at a folder that no longer exists. If MCP stops working right after an update, open your vault’s AGENTS.md again, copy the new path, and update your config.

Running from source

If you build the app yourself, the bundled binary is not there. Build it and use the compiled path:

cargo build --release -p meeting-mcp

Then use target/release/meeting-mcp as the command.