Connecting Voicenotes as a custom MCP server lets Glean Assistant and Glean Agents search notes, list notes by date or tag, and pull full transcripts directly from Voicenotes. Setup takes about ten minutes and is done once by a Glean admin. After that, each team member authorizes their own Voicenotes account on first use.
Before you start
You need admin access to your Glean tenant (Admin console).
Each team member needs their own Voicenotes account. Glean uses per-user OAuth tokens, so nobody's credentials are shared.
Remote MCP servers are fully supported in Glean Assistant. MCP servers inside Glean Agents are currently in beta.
1. Open Vendor Provided Tools
In the Glean Admin console, go to Platform, then Tools, then open the Vendor Provided Tools (via MCP) tab. Click Add in the top right.
2. Choose Import tools from MCP server
In the Add tools dialog, stay on the Vendor provided tools (via MCP) tab and select Import tools from MCP server.
3. Enter the Voicenotes server configuration
Fill in the configuration with these exact values:
Field | Value |
MCP server name | Voicenotes |
Description | Search and retrieve notes, transcripts, and meeting memos from Voicenotes |
MCP server URL | |
Transport | Streaming HTTP (Streamable HTTP) |
Authentication | OAuth with Dynamic Client Registration |
For authentication, leave the client ID and client secret blank. Voicenotes supports Dynamic Client Registration, and Glean uses PKCE for public clients, so no manual credentials are needed. Voicenotes does not offer an API-key or service-account auth method.
4. Connect and discover tools
Click Connect to server so Glean can fetch the list of tools Voicenotes exposes. This admin connection is discovery only; it does not authorize any end user's Voicenotes account.
5. Enable tools and set access
Glean discovers four tools from Voicenotes. Each tool can be enabled for Glean Assistant, Glean Agents, or both, with optional role-based access for selected teammates.
Tool | What it does | Recommended for initial rollout |
| Semantic search across a user's notes | Enable |
| List notes with date and tag filters | Enable |
| Fetch the full transcript of a note | Enable |
| Create a new note (write access) | Leave off until write access is needed |
For the three read tools, keeping Run without user confirmation set to Yes gives a smooth experience. If you later enable create_text_note, Glean supports human-in-the-loop confirmation for write tools, so turn it on there for extra safety.
How per-user authorization works
The first time a team member runs a Voicenotes tool in Glean, their browser opens a Voicenotes OAuth prompt. They sign in and approve access themselves. The token Glean stores is tied to that person, so any query they run only ever reaches their own Voicenotes account. There is no shared workspace credential to manage or rotate.
Need Help?
If you have any questions or encounter any issues, please reach out to us at [email protected].