Toolcape · Wispr Flow

Toolcape + Wispr Flow

Toolcape connects a company’s existing AI to its systems through one MCP entry point, with account connections, group and individual permissions, and audit logs. This documentation describes a product prototype; it is not evidence that a live server or account is connected.

The connection

Wispr Flow: Meeting information, transcripts and notes from Wispr Flow Notetaker.
MCP server · connected through Toolcape
Provider sign-in (OAuth). Confirm whether the configured connection acts as the user or uses application permissions.

Typical actions

- Read: Read meetings, transcripts and notes
This connected source is for reading Notetaker information. It does not control dictation on someone’s computer.

Setup

1. IT verifies the MCP server address, provider and supported sign-in method.
2. Provider sign-in (OAuth). Confirm whether the configured connection acts as the user or uses application permissions.
3. Make the service available in Toolcape. Set Everyone, group and individual rules for the actions actually needed. Adding a service does not grant access.
4. Connect the approved AI client to the actual Toolcape MCP address and sign in. Start with a harmless read-only task and check the audit log.

Permissions

For personal delegated access, the provider account, approved app scopes and Toolcape rules must all permit the action. Shared accounts and application permissions may have other limits. Toolcape combines Everyone and group grants; a personal exception replaces inherited access for that service. Reading can disclose confidential information. Sharing, sending and deletion need separate consideration.

Calling an operation

First discover which tools the connected Toolcape server actually exposes. If it offers search → describe → execute, find the relevant operation, inspect its input schema and permissions, then call it with validated inputs. Tool names vary by server; do not invent names, arguments, URLs or successful outcomes. Without connected tools, give setup guidance instead of claiming to perform actions.

Operation reference

Catalog snapshot: 16 September 2026. Verify the current schema before calling.
- getCalendarEvent — Get calendar event
MCP

- getUpcomingMeeting — Get upcoming meeting
MCP

- listUpcomingMeetings — List upcoming meetings
MCP

- getAccountInfo — Get account info
MCP

- searchMeetings — Search meetings
MCP

- getMeeting — Get meeting
MCP

- getMeetingAttendeeEmails — Get meeting attendee emails
MCP

- resolveShareLink — Resolve share link
MCP

- searchScratchpadNotes — Search notes
MCP

- getScratchpadNote — Get note
MCP

- searchCalendarEvents — Search calendar events
MCP

- resolveCalendarLink — Resolve calendar link
MCP

- getMeetingByCalendarId — Get meeting for calendar event
MCP

- listMeetingSeries — List recurring meeting occurrences
MCP

A useful first question

Find the decisions recorded in yesterday’s meeting notes.

If it fails

Check the account, expired authorization, app approval, provider scopes and Toolcape permissions. Share only redacted errors with support. Never paste passwords, tokens or client secrets into an AI conversation.

Markdown