MCP

Connect with the Claude connector

Alt is listed in the Claude connector directory, so most people never touch the endpoint below. In Claude, open Customize → Connectors, search for Alt, and select Connect.

• Approve access on Alt's own consent screen, and pick the content the connector may read — your personal notes, or a single channel.
• Nothing to paste and no API key to create. Claude registers itself over OAuth.
• Requires an Alt account on a paid plan. Free accounts reach the consent screen but get a plan_required error when they approve.
• Read-only by design: it lists notes and reads transcripts and summaries, and never writes. Revoke it any time in the account console.

1. Connect with OAuth (recommended)

Add the endpoint without headers. Your client discovers Alt's authorization server, registers itself, and opens the browser consent screen.

• Alt supports Dynamic Client Registration and PKCE, so compatible clients configure OAuth automatically.
• Review the requested read-only scopes and workspace in the browser before approving access.
• Connecting requires an Alt account on a paid plan. Free accounts reach the consent screen but get a plan_required error when they approve.

2. Connect your client

Use the URL-only setup for OAuth. No OAuth client ID or secret is required; use an API key only when your client cannot complete OAuth.

https://mcp.altalt.io/mcp

Claude / Claude Desktop / Cowork

Use a custom connector only to reach a different Alt environment: open Customize → Connectors → Add custom connector, enter the endpoint above, and leave the OAuth client ID and secret empty.

Claude Code

claude mcp add --transport http alt https://mcp.altalt.io/mcp

After adding the server, open /mcp in Claude Code, select Alt, and complete browser authentication.

Codex CLI

codex mcp add alt --url https://mcp.altalt.io/mcp
codex mcp login alt

# ~/.codex/config.toml
[mcp_servers.alt]
url = "https://mcp.altalt.io/mcp"

Adding the server normally completes browser authentication. If authentication does not start, run codex mcp login alt.

Cursor

One-click URL-only install. In Cursor's MCP settings, select Connect or Needs authentication and approve the browser consent screen.

Other clients and API-key fallback

Start with the URL-only OAuth config. If a client does not support MCP OAuth, use the Bearer API-key config instead.

{
  "mcpServers": {
    "alt": {
      "url": "https://mcp.altalt.io/mcp"
    }
  }
}

{
  "mcpServers": {
    "alt": {
      "url": "https://mcp.altalt.io/mcp",
      "headers": { "Authorization": "Bearer alt_live_..." }
    }
  }
}

API keys remain supported for automation and older clients. Create one in the account console, grant only the scopes you need, keep it out of shared config, and see Security for key handling.

3. Tools

Four read-only tools, mirroring the REST API and enforcing the same scopes.

• list_notes — List the notes visible to the key, with cursor pagination and an updated_after filter (notes:read).
• get_note — Fetch one note's metadata: title, transcript/summary readiness, timestamps (notes:read).
• get_note_transcript — Fetch the full transcript as timed, speaker-labeled segments (transcripts:read).
• get_note_summary — Fetch the AI summary as Markdown (summaries:read).

Notes appear once a recording has ended or a summary has been generated — memo-only notes are not exported. Before content is ready the tools return transcript_not_ready / summary_not_ready, so agents know to retry later.