note1

note1 MCP Server

Upload recordings and work with your meeting notes, transcripts, and action items from Claude, ChatGPT, Cursor, or any MCP client.

note1 is an AI meeting notetaker that joins your calls, records them, and turns every meeting into a searchable summary with action items. This MCP (Model Context Protocol) server connects AI tools directly to that meeting data — search across conversations with cited sources, read who spoke how much and what was asked, export summaries and speaker-attributed transcripts, list, create and complete action items (and close their linked tickets in GitHub, Linear, Jira and more), manage topic trackers, connect and configure team integrations, read and update your meeting notes, check which calendar events are being recorded, and schedule or manage recordings, all from a conversation.

Every tool acts with the authenticated user's own permissions: private meetings stay private, and results match exactly what the user sees in the note1 dashboard.

• Server URL: https://api.note1.ai/mcp (Streamable HTTP)
• Registry: ai.note1/mcp in the official MCP Registry
• Docs: note1.ai/docs/mcp-server
• Auth: OAuth 2.1 (sign in to note1 in your browser) or a personal access token

Connect without this package

Clients that support remote MCP servers can connect to https://api.note1.ai/mcp directly and sign in to note1 in the browser. You need neither this package nor a token.

• Claude and ChatGPT: add note1 from the Claude Connectors Directory or the ChatGPT plugin directory once listed, or add a custom connector with the URL https://api.note1.ai/mcp. Then sign in to note1 and approve access. Custom connectors depend on your plan.
• Claude Code: install the note1 plugin (server plus skills) with /plugin install note1 --marketplace note1-ai/note1-mcp, or add only the server with claude mcp add --transport http note1 https://api.note1.ai/mcp. Then run /mcp and sign in.
• Cursor and VS Code: add the URL as a remote MCP server and sign in when asked.
• Slack (Slackbot): workspaces connected to note1 get zero-config access. Open a DM with Slackbot, choose Apps, and add note1. Slack identifies you by your workspace email.

Setup with this package

You need a note1 account (note1.ai). Every client below runs the same command, npx -y @note1ai/mcp. Requires Node.js 18 or newer.

The first time the server starts, the package opens note1 in your browser. Sign in and approve access. The sign-in is saved in ~/.mcp-auth on your computer, so you do not repeat it every time.

Claude Desktop

Add to claude_desktop_config.json:

{

"mcpServers": { "note1": { "command": "npx", "args": ["-y", "@note1ai/mcp"] } } }

Cursor

Add to ~/.cursor/mcp.json (or .cursor/mcp.json in a project). Cursor can also connect directly; use this package if Cursor's own sign-in fails.

{

"mcpServers": { "note1": { "command": "npx", "args": ["-y", "@note1ai/mcp"] } } }

VS Code

Add to .vscode/mcp.json:

{

"servers": { "note1": { "type": "stdio", "command": "npx", "args": ["-y", "@note1ai/mcp"] } } }

Claude Code

claude mcp add note1 -- npx -y @note1ai/mcp

Any other MCP client

Configure a stdio server with command npx and arguments -y @note1ai/mcp.

Use a token instead

Browser sign-in needs a browser on the same computer as the MCP client. Over SSH, in CI or in a container, or to skip the sign-in, set NOTE1_API_TOKEN to a personal access token (starts with n1_). Create one at note1.ai/dashboard/account/tokens. It is shown once, so copy it.

{

"mcpServers": { "note1": { "command": "npx", "args": ["-y", "@note1ai/mcp"], "env": { "NOTE1_API_TOKEN": "n1_YOURTOKEN" } } } }

With Claude Code:

claude mcp add note1 --env NOTE1_API_TOKEN=n1_YOURTOKEN -- npx -y @note1ai/mcp

Configuration

The token is passed to mcp-remote through its environment, not on the command line, so it does not show up in process lists. Extra arguments given to the command are forwarded to mcp-remote. The server URL is fixed to https://api.note1.ai/mcp.

Tools

The upload card also calls note1_app_start_recording_upload, note1_app_renew_recording_transfer, and note1_app_complete_recording_upload. They are visible only to the card, not to the model, and need meetings:write.

Upload an existing recording

Recording uploads require meetings:write and the user's approval. One private meeting holds one immutable original audio/video recording; uploads never launch a meeting bot. Use note1_get_recording_upload_options first to check the current workspace limit (initially 2,000,000,000 bytes). It also returns connectivityCheckUrl (https://api.note1.ai/health/status).

Pick the path before reserving anything:

• Direct transfer when the assistant can read the file and reach note1, for example a chat attachment in Claude's code-execution sandbox. First GET connectivityCheckUrl from the place that will send the bytes; continue only if it responds.
• Upload card (note1_open_recording_upload) when the assistant cannot read the file or the connectivity check fails. In MCP Apps hosts (Claude web and desktop) it shows a card where the user picks or drops an audio/video file, checks the meeting title, transcription language (defaults to the workspace's language, or automatic detection), and summary type (default general), and selects Upload. The assistant can pre-fill these with the optional title, language (a la