MCP server

A. They depend on your plan and the MCP client. As a guide at present, roughly 100 requests per minute on average across all tools. The limits may change. Note that the free plan covers only notes from the last 30 days.

A. Where the AI tool says it cannot access your meeting notes or cannot use the tools, re-authenticate first. Disconnecting and reconnecting often restores it.

A. Where it should be connected but no tools appear, reconnect the connector on Claude's side to reset the connection state.

1. Open Claude's connector settings on the web. This has to be done on the web even if you use the desktop app.
2. Choose the Pulse connector.
3. Open the three-dot menu at the top right.
4. Choose “Disconnect”.
5. Without reloading the page or navigating away, choose “Connect” and complete authentication.

If you are on an organisational plan in Claude, you may need to ask your Claude workspace administrator to do this.

A. If this appears after completing OAuth sign-in, you may have authenticated with an address other than the one registered in Pulse.

Your Pulse account's email address is shown under your profile picture at the top left when you open settings in the app (⌘ + , on macOS, Ctrl + , on Windows). When reconnecting MCP, sign in on the OAuth screen with that address.

A. Where you expect meetings but get no results, the connected account, or the workspace within that account, may not be the one you expect.

First ask the AI tool “which Pulse account am I connected as?”. That calls the account information tool and returns the connected email address and the selected workspace. Then:

• If the email address is right but the workspace is wrong: click the workspace name at the top left of the desktop app and switch to the workspace you want. MCP follows the selected workspace, so it applies from the next query.
• If the email address itself is wrong: follow “If you signed in with the wrong account” below to disconnect and reconnect with the right account.

A. Using Claude as the example:

1. Open a private browsing window and sign in to claude.ai.
2. Settings → Connectors and disconnect Pulse.
3. Reconnect while still in the private window. You will be asked to sign in; sign in with the email address of the Pulse account you want.
4. Once connected, go back to your normal browser. It will now work with the right account.

The reason disconnecting and reconnecting in a normal window does not fix it is that your Pulse session is still valid and the sign-in step is skipped. A private window forces sign-in again, letting you choose the account.

A. No. You can use separate accounts. When authenticating, sign in with the Pulse account you want the AI tool to access. Your Pulse account's email address is shown under your profile picture at the top left when you open settings in the app (⌘ + , on macOS, Ctrl + , on Windows).

A. First check which scope applies to you.

• Free plan: personal notes from the last 30 days
• Personal and Team plans: personal notes and public notes
• Enterprise plan: the scopes your administrator has set

The personal notes scope covers notes you own, notes shared directly with you, and notes in private folders shared with you. Note that it does not cover every private note in the workspace. The public notes scope covers notes everyone in the workspace can see, including those in the team space.

MCP also returns only notes belonging to the selected workspace. Notes created in another workspace are not returned from the current one, even if you can see them in Pulse.

You can check the connected account and workspace by asking the AI tool “which Pulse account am I connected as?”.

A. Immediately. The additional tools and relaxed rate limits apply from your next query.

A. Not for a standard browser OAuth connection. MCP connections use Dynamic Client Registration (DCR), so credentials are handled automatically. There is no client ID or client secret to generate or enter.

If a third-party platform such as Composio shows fields for a client ID and client secret, leave them blank. The platform registers automatically when connecting.

EMA is different. When the IdP creates a managed connection it may ask for a Client ID at resource. Enter the URL of the MCP client's Client ID Metadata Document there. With an existing MCP client such as Claude, use the URL that client provides. You do not need to create one, and no client secret is required.

If you build your own confidential client, you create and host its Client ID Metadata Document yourself. That document's URL becomes the client ID, and the client authenticates with its own private key rather than a secret issued by UNCHAIN, Inc..

A. Yes. Any tool implementing the MCP client specification over the Streamable HTTP transport can connect. Authentication can be browser OAuth, or EMA where the tool supports the EMA extension and your IdP supports it. If you run into difficulty implementing it, contact tharada@the-unchain.com.

A. Yes. Administrators set the scopes permitted to workspace members.

1. Settings → Workspace → General.
2. Apps & connectors, find MCP access for members.
3. Click “Manage”.
4. Choose “personal notes”, “public notes”, both, or neither.

A. It depends on the workspace's MCP settings. With neither scope enabled, members cannot use MCP until an administrator enables personal notes or public notes.

A. Settings → Workspace → General → Apps & connectors → MCP access for members. Every member of an Enterprise workspace can view this setting, but only administrators can change it. To have a different scope enabled, ask your workspace administrator.

A. No. This setting controls what non-administrator workspace members can see through MCP. Enterprise administrators can access both personal and public notes through MCP.