Integration status: The production endpoint and OAuth metadata are available. Muse-specific OAuth configuration and end-to-end acceptance testing are pending. This guide does not claim that the connector is already approved or available in the Muse directory.
1Connection details
| Setting | Value |
|---|---|
| Connection type | Existing remote MCP over HTTPS |
| Hosted MCP endpoint | https://mindclip-mcp.switchbot.net/mcp |
| Protected resource / OAuth audience | https://mindclip-mcp.switchbot.net/mcp |
| Required scope | mcp:mindclip:read |
| Authentication | OAuth authorization code with PKCE S256 |
| Access model | Read-only access to the authorized account’s MindClip data |
2Account and access requirements
- A SwitchBot account with MindClip data is needed to retrieve meaningful results. Recordings and generated outputs must already exist in the account.
- The user signs in and authorizes the client through SwitchBot OAuth. Do not ask users to paste their account password, access token, or OpenAPI Token/Secret into an AI conversation.
- Available data depends on the account, devices, recordings, and generated content. An absent transcript or recap must not be treated as an existing result.
- Subscription requirements, supported account regions, and rate or usage limits are pending confirmation. This guide does not promise free access, worldwide availability, or unlimited usage.
3OAuth configuration
The following values were read from the public production metadata on 28 October 2026. Integrators should use metadata discovery and verify the current declarations during setup.
| Setting | Value |
|---|---|
| Protected resource metadata | https://mindclip-mcp.switchbot.net/.well-known/oauth-protected-resource |
| Authorization server metadata | https://account.api.switchbot.net/.well-known/oauth-authorization-server |
| Issuer | https://account.api.switchbot.net |
| Authorization endpoint | https://sp.oauth.switchbot.net/login |
| Token endpoint | https://account.api.switchbot.net/merchant/v1/oauth21/token |
| Response type | code |
| Grant types | authorization_code, refresh_token |
| PKCE challenge method | S256 |
| Token endpoint authentication method | none |
| Bearer token delivery | Authorization: Bearer <access_token> header |
mcp:mindclip:read. The metadata currently does not advertise a dynamic client registration endpoint or Client ID Metadata Document support. Do not assume those registration methods are available.Muse setup is pending confirmation of its exact redirect URI and supported client configuration. Register the confirmed redirect URI with the appropriate SwitchBot OAuth client before authorization. Do not reuse another platform’s client ID or callback without an explicit compatible configuration. The declared token authentication method is none; a shared client secret is not part of that declared token exchange.
Client implementation outline
- Configure the endpoint and registered OAuth client.
- Perform authorization with PKCE and request the MindClip read scope.
- Send the resulting bearer token to the MCP endpoint.
- Initialize an MCP session and discover tools.
- Invoke tools using the authenticated session.
Use a compatible MCP client library for protocol negotiation and transport handling. Complete platform-specific testing before describing this flow as working in Muse.
4Read-only tool reference
Tool names below match the current exposed MindClip tool declarations. Discover tools/list in the connected environment for the authoritative input schema, validation rules, and any version-specific changes. Parameters marked optional may be omitted; undocumented defaults and maximums are not assumed here.
| Tool | Purpose and inputs |
|---|---|
mindclip_list_recordings | List recording metadata. Optional: device_id, folder_id, start_time_ms, end_time_ms, page, page_size. When device_id is omitted, the only MindClip device can be selected automatically; multiple devices require an exact device ID. |
mindclip_get_recording | Retrieve one recording’s metadata and details. Required: recording_id. Optional: language. |
mindclip_get_transcript | Retrieve normalized transcript text. Required: recording_id. Optional: max_chars. Check the truncated flag; a limited result may not contain the full transcript. |
mindclip_get_summary | Retrieve an existing recording summary. Required: recording_id. Use the transcript tool when transcript text is needed. |
mindclip_list_todos | List existing extracted to-dos. Optional: completed, category, file_id, device_id, start_time_ms, end_time_ms, page, page_size. Categories: 0 any, 1 work, 2 life, 3 hobby, 4 holiday, 5 other. |
mindclip_get_daily_assistant | Retrieve an existing daily assistant result. Optional: date in YYYY-MM-DD format; omission uses the server default. |
mindclip_get_weekly_assistant | Retrieve an existing weekly assistant result. Optional: week in ISO YYYY-Www format; omission uses the server default. |
mindclip_get_urgent_todos | Retrieve urgent to-dos. Optional: date in YYYY-MM-DD format; omission uses the server default. |
list_todos is named file_id. These tools do not create, edit, complete, or delete to-dos; upload or delete recordings; or generate new recap content.5Usage examples
completed=false and category=1.Example MCP tools/call payload after initialization and OAuth authorization. Replace the placeholder with an actual recording ID returned for the authorized account. This is a request example, not a captured production response or Muse-specific configuration file.
{
"jsonrpc": "2.0",
"id": 2,
"method": "tools/call",
"params": {
"name": "mindclip_get_summary",
"arguments": {
"recording_id": "<recording_id_from_list_recordings>"
}
}
}6Validation and troubleshooting
- For an authorization failure, verify the client registration, exact redirect URI, requested scope, PKCE settings, and current metadata. Use the configured OAuth flow to reconnect when needed.
- For expired access, use the supported refresh flow where available; reconnect if refresh fails. Do not insert credentials into prompts or application logs.
- For empty results, verify that the account contains the requested content and that device, recording, date, week, and filter values are correct.
- For a truncated transcript, disclose that only part of the transcript was returned. A larger
max_charsvalue remains subject to the server’s schema and limits. - For throttling or service errors, follow the server’s returned guidance and use bounded retry/backoff. Exact rate thresholds and a complete error-code catalog are pending confirmation.
- Before release, test account authorization, all eight tools with non-sensitive sample data, empty results, unauthorized access, token refresh, and reconnection in the target client. Muse acceptance results remain pending.
7Data use, support, and policies
Tool requests can include recording or device identifiers, filters, dates, and pagination parameters. Responses can contain private recording metadata, transcript text, summaries, to-dos, and recap content. Only retrieve content needed for the user’s request, and handle returned content as private account data. This guide does not assert additional retention or training commitments beyond the published policies.
8Integration items pending confirmation
- Muse OAuth redirect URI, client configuration requirements, and end-to-end compatibility.
- Required subscription or plan, supported account regions, and rate or usage limits.
- Review test account, non-sensitive sample IDs and dates, and platform-specific acceptance results.
