FluidMeet MCP Server
# FluidMeet MCP server
Ask Claude about the meetings you recorded with [FluidVoice](https://github.com/altic-dev/FluidVoice)
(FluidMeet), for example: *"What did we decide in yesterday's call?"* or
*"Summarize the action items from my last meeting."*
This is a small, local, **read-only** [MCP](https://modelcontextprotocol.io) server. It wraps the helper
`fv-serve` that ships inside FluidVoice. It never runs any other command and never reads FluidVoice's
files directly.
> Unofficial community project. Not affiliated with the FluidVoice developers.
## Requirements
- macOS with **FluidVoice** (including FluidMeet) installed, normally in `/Applications`
- In FluidVoice: **FluidMeet settings > Integrations**, then allow agent access. Without this,
every tool returns "meetings not shared yet".
## Install
### Claude Desktop (recommended, one click)
1. Download `fluidmeet.mcpb` from the [latest release](https://github.com/dl6nm/fluid-meet-mcp-server/releases/latest).
2. Double-click it, or in Claude Desktop go to **Settings > Extensions** and drag the file in.
3. Click **Install**. Claude Desktop sets up Python and the dependencies itself.
4. Start a new chat and ask about your meetings.
If FluidVoice is not in `/Applications`, set **Path to fv-serve** in the extension's settings.
#### About the install warning
During installation, Claude Desktop says the extension gets *"access to everything on your
computer"* and that the developer information *"has not been verified by Anthropic"*. Claude Desktop
shows this text for **every** local extension. Extensions have no way to declare narrower
permissions, so the text doesn't describe what this server actually does:
- It only ever starts one program, FluidVoice's `fv-serve` (by default
`/Applications/FluidVoice.app/Contents/Helpers/fv-serve`).
- It only calls `fv-serve`'s read-only subcommands: `meet list|show|summary|search`, `status`,
`skill`. It uses an argument list and no shell, and validates every input.
- Its code writes no files, opens no network connections, and doesn't read FluidVoice's data directly.
- All tools are marked `readOnlyHint` for MCP clients.
The whole server is a single file of about 300 lines,
[`src/fluidmeet_mcp/server.py`](src/fluidmeet_mcp/server.py). Please read it before installing.
The manual config and Claude Code installs below run the same code with the same rights; they just
don't show a dialog.
### Claude Desktop (manual config)
This needs [uv](https://docs.astral.sh/uv/). Add the following to
`~/Library/Application Support/Claude/claude_desktop_config.json`, then restart Claude Desktop:
```json
{
"mcpServers": {
"fluidmeet": {
"command": "uvx",
"args": ["--from", "git+https://github.com/dl6nm/fluid-meet-mcp-server", "fluidmeet-mcp"]
}
}
}
```
If Claude Desktop reports that `uvx` can't be found, replace `"uvx"` with the absolute path that
`which uvx` prints. GUI apps don't always see your shell's `PATH`.
### Claude Code
```sh
claude mcp add fluidmeet -- uvx --from git+https://github.com/dl6nm/fluid-meet-mcp-server fluidmeet-mcp
```
## Tools
| Tool | What it does | fv-serve call |
|---|---|---|
| `meet_list(since?, limit?)` | Meetings, newest first, as JSON | `meet list … --json` |
| `meet_show(id="latest", from_?, to?, json=false)` | Transcript, optionally a time window | `meet show <id> [--from] [--to] [--json]` |
| `meet_summary(id="latest", style?)` | Summaries saved in FluidVoice | `meet summary <id> [--style]` |
| `meet_search(text, since?, limit?)` | Matching lines with timestamps | `meet search … -- <text>` |
| `status()` | Is access granted? How many meetings? | `status --json` |
| `skill()` | FluidVoice's own usage guide | `skill` |
- **Input formats:** `since` is `7d`, `24h` or `YYYY-MM-DD`. `from_`/`to` are `MM:SS`; minutes can
go above 59, e.g. `75:30`. `id` is `latest` or an id prefix from `meet_list`.
- **Long transcripts:** a 1-hour meeting is about 10,000 words. The tool descriptions steer Claude
to `meet_search` and time windows, and output above 50,000 characters is truncated with a hint.
- **Transcript content:** the tool descriptions mark transcript text as data, not instructions.
## Configuration
All settings are optional environment variables:
| Variable | Default | Purpose |
|---|---|---|
| `FLUIDMEET_FV_SERVE` | `/Applications/FluidVoice.app/Contents/Helpers/fv-serve` | Path to `fv-serve` |
| `FLUIDMEET_TIMEOUT` | `30` | Seconds per `fv-serve` call |
| `FLUIDMEET_MAX_CHARS` | `50000` | Output size limit before truncation |
## Troubleshooting
- **"meetings not shared yet":** in FluidVoice open FluidMeet settings > Integrations and add the agent.
- **"command not found":** FluidVoice was moved or removed. Reinstall it, or set `FLUIDMEET_FV_SERVE`.
Then use **Update skill** under FluidMeet settings > Integrations.
- **"No current saved summary":** summaries are created in FluidVoice. Ask Claude to read or
search the transcript instead.
- **Claude Desktop logs:** `~/Library/Logs/Claude/mcp-server-fluidmeet.log`
## Privacy
Everything runs locally. The server only passes along what `fv-serve` prints, and only when Claude
calls a tool. Transcript text that Claude reads becomes part of your conversation with Claude.
## Development
```sh
uv sync
uv run pytest # unit tests, fv-serve is mocked
uv run fluidmeet-mcp # run the server on stdio
npx -y @anthropic-ai/mcpb@2.1.2 pack . dist/fluidmeet.mcpb # build the Claude Desktop bundle
```
Releases follow git flow (`dev` → `release/X.Y.Z` → `main`). Bump `version` in `pyproject.toml`,
`manifest.json` and `src/fluidmeet_mcp/__init__.py`, finish the release, and push `main`. On every push
to `main`, the workflow runs the tests, builds `fluidmeet.mcpb` and publishes GitHub release
`vX.Y.Z` with the bundle attached. It reuses the tag if you pushed it, or creates it otherwise.
## License
MIT, see [LICENSE](LICENSE). FluidVoice itself is GPL-3.0 and is not included here.
TDQS
Scored across 6 tools
The four meet_* tools have clearly separated roles: list for discovery, show for transcript windows, search for locating mentions, and summary for saved summaries. status and skill are meta tools with distinct diagnostic and usage-guide purposes, and the descriptions explicitly guide sequencing and fallbacks.
Core tools consistently follow a meet_ + action/noun pattern: meet_list, meet_show, meet_summary, meet_search. However, status and skill break the prefix pattern with bare nouns, which is a minor inconsistency but still readable.
Six tools is well-scoped for a read-only meeting transcript server. Each tool supports a distinct access path or diagnostic need, with no redundant endpoints.
The surface covers discovery, transcript reading, search, saved summaries, and accessibility diagnostics, which is strong for a read-only integration. Minor gaps include no explicit single-meeting metadata tool beyond list and no way to create or update summaries, though that may be outside the server's scope.