MCP for agents

For agents with shell access, we recommend the CLI for both reading and writing. Start with the skill installation prompt to make your agent aware of it and remember to use it. MCP is an optional read-only connection for clients without shell access, or when you prefer MCP.

The MCP server is part of the loof executable. It communicates through standard input and output. It does not open a network port or send vault data to a hosted service. It is read-only: to create sessions, edit notes, attach source artifacts, or import and transcribe audio, use the CLI.

The MCP tool names retain meeting for compatibility, but they can also return standalone knowledge sessions that have no recording or transcript.

Configure a client

{
  "mcpServers": {
    "loofah": {
      "command": "loof",
      "args": ["mcp"]
    }
  }
}

Use the absolute path to loof if the client cannot find it on PATH. Restart the client after changing its MCP configuration. For exact Claude Desktop, Claude Code, Codex, and Hermes setup commands, see Connect Loofah to Claude, Codex, or Hermes.

For a custom vault path:

{
  "mcpServers": {
    "loofah": {
      "command": "loof",
      "args": ["--vault-path", "/path/to/vault", "mcp"]
    }
  }
}

Recommended order

Start with list_meetings or search_meetings. Pass a returned id to get_meeting. Call get_meeting_transcript only if the meeting detail does not contain enough evidence.

get_meeting_transcript returns the complete transcript as [HH:MM:SS] Speaker: ... lines.

See the MCP reference for exact parameters and resource URIs.