MCP configuration

MCP (Model Context Protocol) lets NoteGen call external tools and resources through a standard protocol. Enabling MCP does not authorize every server automatically; enable a server and select it in the conversation.

Connection types

Local command (stdio)

Desktop only. Enter a command, space-separated arguments, and optional JSON environment variables:

{
  "API_KEY": "your-key"
}

You may enter a full launcher such as npx @modelcontextprotocol/server-filesystem in Command. When Arguments is empty, NoteGen separates the first word from the remaining arguments.

HTTP service

Available on desktop and mobile. Enter a service URL and optional JSON headers:

{
  "Authorization": "Bearer your-token"
}

Mobile cannot launch local stdio processes, so new mobile configurations offer HTTP only.

Add and import

• Add a server with its name, type, and connection parameters.
• Disable a server without deleting its configuration.
• Import JSON accepts common mcpServers structures and skips duplicates.
• Test a temporary configuration before saving. Enabled servers attempt to connect after save.

Runtime environment

Local commands often require Node.js, Python, uv, or another launcher. Check Environment shows detected versions and missing runtimes. On supported platforms, guided installation runs only after you confirm the command, displays logs, and can be cancelled.

Browse and use tools

The tool browser shows connected tools, descriptions, and parameters. In Chat or Agent, open MCP in the toolbar and select the servers for the current conversation. Tool calls still follow Agent approval rules.

Security

• Commands run programs with your user permissions; use trusted configurations only.
• Environment variables and headers may contain secrets. Do not share screenshots or exports containing them.
• Send remote MCP servers only the context needed for the task.
• Deleting a server does not revoke its third-party token.