Note1

What note1 MCP server does

note1 MCP server gives an AI client access to meeting information and recording-related actions in note1. Its documented scope covers three areas: finding meetings, exporting meeting summaries and transcripts, and managing meeting recordings.

This makes the server relevant for workflows where an agent needs to locate prior conversations, retrieve written meeting output, or perform supported actions on recordings. The available material does not specify additional note1 objects, external integrations, or operations beyond meetings, summaries, transcripts, and recordings.

Tools and capabilities

The note1 MCP server is described as providing capabilities for:

• Searching meetings stored in note1.
• Exporting meeting summaries.
• Exporting meeting transcripts.
• Managing meeting recordings.

The source description does not provide the individual MCP tool names, argument formats, return schemas, search filters, export formats, or recording-management actions. Developers should verify those details in the note1 MCP documentation before building a client workflow around a specific operation.

How it works

An MCP-compatible AI client can use the server as an interface to note1 meeting content. The client can request meeting searches, ask for summaries or transcripts to be exported, and use the available recording-management functionality. MCP provides the agent-facing protocol, while note1 remains the system containing the meetings and recordings.

The supplied material does not identify whether the server uses standard input/output, streamable HTTP, or another transport. It also does not describe authentication, permissions, pagination, filtering syntax, export destinations, or whether recording management includes actions such as updating or deleting recordings. Those details are necessary for implementation and should be confirmed in the linked documentation.

Setup and configuration

The provided listing does not include installation commands, client configuration examples, required environment variables, authentication steps, or runtime dependencies. Consult the note1 MCP documentation for the supported setup procedure and the configuration required by your MCP client.

No client-specific setup is identified in the supplied material. Compatibility should therefore be confirmed against the MCP client and the transport documented by note1.

Limitations and notes

The available description establishes the server’s high-level purpose but not its complete API surface. It does not state which meeting fields can be searched, how exports are produced, what recording operations are available, or which permissions are required. Treat the note1 MCP server as a meeting-search, export, and recording-management interface until the detailed documentation confirms more specific behavior.