Connect Muse

Muse, Meta's AI assistant, can read your SummitScribe meetings through a custom connector. Once it's connected you can ask Muse what was decided in a meeting or who owns a follow-up. Muse can only read. It can't change, delete or share anything in SummitScribe.

Before you start

You need a SummitScribe access token. Tokens are made on the website.

Sign in at summitscribe.app and open Account settings (from your profile menu), then Developer & agents.
Create a token named Muse so you can find it later. Pick the shortest expiry that works for you (30 days is the shortest). You can make a new token when it runs out.
Give it mcp:read plus the data you want Muse to read: meetings:read, notes:read, transcripts:read, actions:read and search:read.
Copy the token. SummitScribe shows it only once.

Add the connector

Muse has no settings screen for connectors. You set one up by asking Muse in a chat.

Start a chat with Muse and send:

Create a custom connector named SummitScribe. Transport: Streamable HTTP. URL: https://summitscribe.app/api/mcp. It needs a bearer token; ask me for it with the secure credential prompt.

Muse shows a secure credential prompt. Paste your token there. Don't paste the token into the chat itself.
Try it: "What did we decide in yesterday's planning meeting?"

What Muse sees

When Muse calls SummitScribe, the meeting content it reads (notes, transcripts, action items) goes to Meta and is handled under Meta's terms. Meta doesn't review custom connectors. Only give the token the scopes you're comfortable sharing.

Revoke access

Open Account settings, then Developer & agents, on the website and revoke the Muse token. Muse loses access right away. If a token ever ends up in a chat message, revoke it and make a new one.

For other assistants (Claude Code, Cursor, Gemini CLI, VS Code and more), see SummitScribe for AI agents.