Connect any MCP server to Audiee
Feature · 2026-09-13
Audiee has been an MCP server since the start: your meetings, notes and connected services as tools for Claude Code, Cursor and Claude Desktop. As of 0.1.47 it is also an MCP client. Any server that speaks the protocol — Linear, HubSpot, a filesystem server, the internal tool your team wrote — can be plugged in from Settings, and its tools become available to Audiee's assistant alongside everything it already knows about your meetings.
How it works
- Open Settings → MCP servers and add one: a remote URL (Streamable HTTP or SSE, with an optional bearer token) or a local command such as
npx -y @modelcontextprotocol/server-filesystem ~/Documents. - Audiee connects lazily on first use, lists the server's tools and caches them; idle connections close after ten minutes and everything is torn down on quit. The configuration lives in
~/.audiee/mcp-servers.json. - The tools appear to the assistant as a virtual skill named
mcp:<id>. Ask in Chat: "file today's three action items as Linear issues" and the assistant reads the meeting, drafts the issues, and holds for your go-ahead before anything is created.
What it is for
- Meeting to system of record. The action items from a call become issues, tickets or CRM notes without copy-paste, with the meeting cited.
- Your own tools in the conversation. An internal server that knows your deployments or your customers can be asked about in the same Chat as your meetings.
- Filesystems and databases the assistant can read from when a question spans a meeting and a document that is not in Knowledge.
The safety model
Results from external servers are untrusted content. Audiee's assistant runs a provenance gate: text that arrived from a tool cannot issue instructions to the assistant, and any action that writes somewhere (creating an issue, sending a message) is held for your explicit go-ahead. External tools get the same treatment as Audiee's own Gmail or Slack tools — no more, no less. Tokens you enter are stored on your Mac, not on our servers.
Limits
- MCP clients have tool budgets; a server that exposes hundreds of tools will be truncated. Prefer focused servers.
- Authentication is a bearer token or nothing; servers that need a browser OAuth dance are not handled yet.
- Calls time out after 60 seconds; connection after 20.
Available in 0.1.47 on every plan. Calls to external servers are not metered. The developer page covers what Audiee itself exposes over MCP.