Provides tools to generate prefilled Google Meet links with the note1 recording bot pre-invited and to schedule or manage recordings for Google Meet meetings.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@note1 MCP Server What did we decide about the launch date in last week's meetings?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Query 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, manage topic trackers, 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 (automatic browser consent) or Personal Access Tokens
Tool | Description |
| Search meetings by keyword and meaning. Mode |
| Browse meetings by status and date range, paginated. |
| One meeting's summary, sections, participants, status, recurring series (previous and next occurrence), and link. |
| Speakers with talk-time share, questions asked and answered, topics with time ranges, topic-tracker mentions, or highlights. Use instead of the transcript for "who spoke most" or "what was asked". |
| Full summary and/or speaker-attributed transcript as paste-ready markdown or structured JSON. |
| Tracked action items for a meeting or the team, with status, owner, meeting, date and page; |
| Create an action item under a meeting or with none, for you, a named person, or nobody. |
| Edit text, description or owner, or mark open, completed or dismissed. |
| Topic trackers you can see and where their phrases came up recently, with quotes. |
| Create a tracker: a named set of phrases watched across meetings. Personal by default; team trackers take an admin. |
| Rename a tracker or add and remove its phrases. |
| Delete a tracker. |
| A meeting's personal notes and shared agenda, each block with a ref. |
| Change the notes block by block, or replace them with markdown. Personal by default; the shared agenda needs edit access. |
| Calendar events with per-event recording status. |
| Prefilled calendar link (Google Meet / Teams) with the note1 bot pre-invited — create the event in your own calendar with recording pre-wired. |
| Send note1's recording bot to an existing calendar event or any meeting link at a given time. |
| Edit title, bot time/link, summary style, language, or video — optionally for a recurring series. |
| Call off the bot for a meeting or its series. |
Related MCP server: Notes MCP Server
You need a note1 account (note1.ai). For token-based setups, create a Personal Access Token under Account → API tokens (shown once — copy it).
Claude Settings → Connectors → Add custom connector
Name: note1 — URL: https://api.note1.ai/mcp — leave the OAuth fields empty
Add, then approve access on the note1 consent page
npx @note1ai/mcp{
"mcpServers": {
"note1": {
"command": "npx",
"args": ["-y", "@note1ai/mcp"],
"env": { "NOTE1_API_TOKEN": "n1_YOURTOKEN" }
}
}
}claude mcp add note1 --transport http https://api.note1.ai/mcp \
--header "Authorization: Bearer n1_YOURTOKEN"{
"mcpServers": {
"note1": {
"url": "https://api.note1.ai/mcp",
"headers": { "Authorization": "Bearer n1_YOURTOKEN" }
}
}
}Workspaces connected to note1 get zero-config access: open a DM with Slackbot → Apps → add note1. Slack identifies you by your workspace email.
"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?"
"Who spoke the most in yesterday's standup, and which questions went unanswered?"
"What are my open action items? Mark the deck one as done."
"Start tracking mentions of pricing across our meetings"
"Record my 3pm meeting: https://meet.google.com/abc-defg-hij"
"Summarize all my meetings with the design team this month"
The hosted MCP server lives at https://api.note1.ai/mcp. This package (@note1ai/mcp) is a thin stdio bridge for clients that launch MCP servers as commands: it wraps mcp-remote with the note1 URL and your NOTE1_API_TOKEN. Clients with native remote support (claude.ai, Cursor) can connect to the URL directly and skip it.
Tokens are shown once at creation and stored only as SHA-256 hashes server-side. Revoke anytime under Account → API tokens.
OAuth connections appear under Connected apps with one-click revocation.
Write tools (schedule/update/cancel) are annotated so clients prompt for confirmation; read tools are marked read-only.
note1 holds no calendar write permissions — scheduling tools control note1's recording bot only and never create or modify calendar events.
note1 — product
MCP server docs — full setup guide and troubleshooting
Model Context Protocol — the standard
MIT
This server cannot be deployed
Search meetings, export summaries and transcripts, and manage recordings from any AI tool.
Let AI assistants record meetings and work with notes, transcripts, contacts, and Drive.
Search recordings, summarize meetings, create clips, and automate workflows from your AI assistant.
AI access to your aNotepad online notes: read, search, write, and organize via 22 tools.
