note1 MCP Server

Connect your AI tools to note1 and work with your meetings from anywhere: search past conversations, pull summaries and transcripts, check your calendar, and schedule recordings — directly from Claude, Cursor, Slackbot, or any MCP-compatible client.

What is MCP?

Model Context Protocol (MCP) is an open standard that lets AI applications securely connect to external tools and data. The note1 MCP Server exposes your meetings as tools your AI assistant can call — always with your own note1 permissions, so private meetings stay private.

Server details

The note1 MCP Server is available at:

https://api.note1.ai/mcp

It supports two authentication methods:

OAuth — the browser-consent flow used by claude.ai. No setup needed; you'll be asked to log in to note1 and approve access.
Personal Access Token (PAT) — a long-lived API token for clients that send auth headers (Claude Desktop, Claude Code, Cursor).

Related resources:

GitHub: note1-ai/note1-mcp — connector source and setup examples
npm: @note1ai/mcp — npx -y @note1ai/mcp stdio bridge for command-based MCP clients
MCP Registry: ai.note1/mcp — official registry listing

Create a Personal Access Token

Sign in to your note1 account.
Go to Account → API tokens.
Enter a name (for example, "Claude Desktop") and select Create token.
Copy the token immediately — it is shown only once.

Tokens act as you, with your exact meeting permissions. You can revoke them anytime from the same page.

Configuration by platform

Claude (web)

Claude connects via OAuth — no token needed:

Open Claude Settings → Connectors.
Select Add custom connector.
Name it note1 and enter the URL: https://api.note1.ai/mcp.
Leave the OAuth Client ID and Secret fields empty — registration is automatic.
Select Add. Your browser opens a note1 consent page — select Allow.

You can revoke Claude's access anytime under Account → API tokens → Connected apps.

Claude Desktop

Add the following to your claude_desktop_config.json (Settings → Developer → Edit Config), replacing n1_YOURTOKEN with your Personal Access Token:

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

Restart Claude Desktop after saving. Node.js is required. The @note1ai/mcp package (source) is a thin bridge to the hosted server — clients with native remote support can use the URL directly instead.

Claude Code

claude mcp add note1 --transport http https://api.note1.ai/mcp \
  --header "Authorization: Bearer n1_YOURTOKEN"

Cursor

Add to ~/.cursor/mcp.json (or a project's .cursor/mcp.json):

{
  "mcpServers": {
    "note1": {
      "url": "https://api.note1.ai/mcp",
      "headers": { "Authorization": "Bearer n1_YOURTOKEN" }
    }
  }
}

Slackbot

If your Slack workspace is connected to note1 (Team → Integrations), no token is needed — Slack identifies you automatically by your Slack email:

Open a DM with Slackbot.
Select the Apps button in the Slackbot toolbar.
Add note1 from the list.
Ask Slackbot things like "what meetings did I have this week?"

Your Slack email must match your note1 account email in the connected workspace.

Available tools

Tool	Description
`note1_search_meetings`	Search your meetings. Mode `search` returns ranked source snippets; mode `analysis` returns an AI answer with cited sources.
`note1_list_meetings`	Browse meetings without a query — filter by status and date range, paginated.
`note1_get_meeting`	Fetch one meeting: summary overview, sections, participants, status, and the dashboard link.
`note1_export_meeting`	Export a meeting's summary and/or full speaker-attributed transcript as paste-ready markdown or structured JSON.
`note1_get_calendar`	List your calendar events with recording status.
`note1_get_scheduling_link`	Get a prefilled calendar link (Google Meet or Teams) with note1 pre-invited — the human-in-the-loop way to set up a recorded meeting.
`note1_schedule_recording`	Send note1's recording bot to an existing calendar event or any meeting link at a given time. Does not create calendar events.
`note1_update_meeting`	Edit a note1 meeting: title, bot time or link, summary style, language, video — optionally for a whole recurring series.
`note1_cancel_recording`	Call off the recording bot for a meeting or its series.

Read tools run without confirmation prompts; scheduling, updating, and cancelling ask for approval in clients that support it (like Slackbot).

Example prompts

"What did we decide about pricing in last week's meetings?"
"Export the transcript of yesterday's standup as markdown"
"Which of my meetings tomorrow are being recorded?"
"Record my 3pm meeting — here's the link: https://meet.google.com/..."
"Set up a meeting for Thursday at 2pm" (returns a scheduling link to click)
"Cancel the recording for Friday's 1:1, this week only"

Permissions and privacy

Every tool acts as you: search results, transcripts, and calendar data follow your note1 permissions. Meetings you can't see in the dashboard don't appear in tool results either.
OAuth connections and tokens are managed under Account → API tokens; revoking cuts access immediately.
note1 holds no calendar write permissions — scheduling tools control note1's recording bot only and never create or modify calendar events. For creating events, note1_get_scheduling_link returns a link you open in your own calendar.

Troubleshooting

401 / authentication errors

Check the token is passed as Authorization: Bearer n1_... and hasn't been revoked (Account → API tokens shows last-used times).
For claude.ai, reconnect the connector — OAuth access may have been revoked.

A recently added tool doesn't appear

AI clients cache tool lists per session. Start a new conversation, or disconnect and reconnect the server (Claude Desktop: restart the app).

"This meeting has no transcript file"

The meeting may still be processing, or it never recorded. Check its status on the meeting page.

Slackbot doesn't offer note1

The workspace connection may predate MCP support: a team admin should reconnect Slack from Team → Integrations, then re-add note1 in Slackbot's Apps tab.