mcpbeat Sign in

note1.ai MCP Server

answering

note1.ai is answering right now. Last checked 2 min ago.

Search meetings, export summaries and transcripts, and manage recordings from any AI tool.

Uptime history 33 days of history
33 days agonow
100.0%
Uptime 24h
93 of 93 checks
Tools
hidden behind auth
553 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check note1.ai every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 2 min ago.

run in your terminal
claude mcp add mcp --transport http https://api.note1.ai/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://api.note1.ai/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.mcp]
url = "https://api.note1.ai/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://api.note1.ai/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://api.note1.ai/mcp"
    }
  }
}

This endpoint answered with an authorization challenge — the server is running, but you need an API key or OAuth to use it.

Endpoints

URLTransportStateLatencyChecked
https://api.note1.ai/mcp streamable-http needs key 550 ms 2 min ago

Alternatives to note1.ai

same job, measured the same way
Zoom Meetings
by zoom

Zoom Meetings server for meeting search, recordings, transcripts, summaries, and meeting assets.

answering
T
Memo AI – meeting assistant
by memoai

Search transcripts and summaries of your meetings, calls, and recordings in Memo AI

16 installs/wk local only
Fireflies.ai
by fireflies

Search and analyze meeting transcripts, summaries, soundbites and analytics from Fireflies.ai

answering
Fathom MCP Server
by agencyenterprise

Connect Claude to Fathom meeting recordings, transcripts, and summaries

answering
Laxis
by laxis-tech

Search and read your Laxis meeting transcripts, AI summaries, and participants from Claude.

answering
Gilbert MCP
by hugof1234

Gilbert meetings: list, search, and fetch transcripts & summaries via MCP.

71 installs/wk local only
Clipy
by clipy

Read your Clipy screen recordings: search, transcripts, AI summaries, and key moments with frames.

116 installs/wk local only
A
MyGhosts
by myghosts

Send AI bots to attend meetings on your behalf. Get recordings, transcripts, and summaries.

answering

note1.ai — questions

Answers built from our own checks of this server.

Why is there no tool list for note1.ai?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is note1.ai working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 93 of 93 checks got a reply (100.0%), average response time 553 ms. The bar chart above shows every period we have measured.
How do I connect note1.ai?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to note1.ai?
No API key is involved. note1.ai answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is note1.ai?
It answers our handshake in 553 ms on average, which is faster than 28% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.