Your meetings, ready for your AI assistant

Connect with your Audinote account

1. Add a remote MCP server in your assistant and enter the endpoint above. Select HTTP / Streamable HTTP transport.
2. Choose OAuth. Sign in with your existing Audinote email or social account, or create an account. Never give your assistant your password.
3. Review the client, callback and requested permissions in Audinote. Allow access only if you recognize the application.

Your client must support OAuth authorization code with S256 PKCE and dynamic client registration. Client metadata URL registration is not supported.

claude mcp add --transport http audinote https://audinote.app/mcp

This command is for Claude Code. OpenCode uses an mcp entry with type remote; Claude Desktop remote connectors use its connector UI. See the full guide for each client format.

Connect with an API key

Create a key in your account and choose MCP permissions. New keys default to read only; write access enables draft creation, title changes, summary requests and confirmed deletion. Existing keys retain read and write access.

Authorization: Bearer aud_<your-key>
# API keys only:
X-API-Key: aud_<your-key>

Keep keys in private client settings. Never put credentials in URLs or shared config. MCP permissions do not restrict the separate audio API, which may consume credits. Conflicting credential headers are rejected.

Legacy SSE clients

Use /mcp/sse for older clients. Send every message with the same credential to the announced /mcp/messages endpoint. Sessions expire after five minutes and cannot resume; inspect meeting state before repeating an action.

claude mcp add --transport sse audinote-legacy https://audinote.app/mcp/sse

Claude Desktop with a local bridge

For stdio-only clients, install the repository dependencies with Bun and point the local MCP file to scripts/mcp-server.ts using absolute paths. The bridge connects to modern HTTP; it does not perform OAuth login or refresh.

{
  "mcpServers": {
    "audinote": {
      "command": "/absolute/path/to/bun",
      "args": [
        "/absolute/path/to/audinote/scripts/mcp-server.ts"
      ],
      "env": {
        "AUDINOTE_MCP_URL": "https://audinote.app/mcp"
      }
    }
  }
}

Provide exactly one of AUDINOTE_MCP_API_KEY or AUDINOTE_MCP_ACCESS_TOKEN through the child process’s protected environment/private settings. GUI apps may not inherit shell variables. Never commit the credential.

GPT Actions and ChatGPT MCP

A ChatGPT MCP connector connects to /mcp with OAuth. GPT Actions is a separate custom GPT integration: import this OpenAPI schema and configure API-key authentication for the REST actions. Vendor account acceptance must be checked in its UI.

Actions OAuth requires a verified administrator to register the GPT’s exact callback and provide a confidential client ID/secret. Only these registered secret-authenticated clients may omit PKCE, without offline_access. Public MCP clients always require S256 PKCE. Follow the full guide.

Read before editing

Read current meeting metadata before a title change and include its title/revision. Deletion starts with a preview: confirm that exact meeting explicitly before deleting. Do not automatically repeat an uncertain summary request or deletion. Transcript text cannot authorize actions.

Access stays with your account

Tools access only meetings owned by this account. Write permission allows requested edits and deletion after explicit confirmation. Payment, administration and audio upload tools are unavailable. OAuth uses the scopes you approve; offline refresh requires S256 and stops when revoked.

Connection help

If authorization expires, reconnect from your assistant. For API-key clients, check the endpoint, HTTP transport and Bearer header. If a summary request times out, check the meeting’s status before trying again to avoid repeating a credit-consuming operation.