Connect OneMira to Cursor by running the local OneMira MCP server over stdio, registering that exact command in Cursor, inspecting the exposed tools, and testing a read-only query against a known local note. Do not paste a remote token into a local server configuration unless the documented tool actually requires it.

Version note. Cursor and MCP interfaces change. This guide was checked against Cursor’s official MCP/CLI documentation and the MCP security guidance available on 16 July 2026. The OneMira commands must match the installed desktop release.

What are you connecting?

MCP separates the AI host from a server that exposes tools or resources. Cursor is the host/client side. The OneMira server is a local process that reads the bounded OneMira note store and returns structured results. The model does not receive the entire folder automatically; it receives the result of a tool call approved and dispatched by the host.

The official MCP architecture supports local servers through stdio. The security guidance recommends stdio for local servers where practical because it limits access to the launching client, while warning that a local server still runs with the client’s operating-system privileges.

What should you verify before adding Cursor?

  1. Install the supported OneMira desktop app and complete the documented C1 sync.
  2. Open the local notes directory and identify one non-sensitive test note.
  3. Run the OneMira diagnostic or MCP-list command shown by the installed release.
  4. Confirm the executable path with command -v or an absolute path.
  5. Review the command: it should launch OneMira’s known local server, not an unreviewed npx package or shell pipeline.

The current OneMira documentation is the source of truth for command names: see MCP setup and CLI reference. A blog article should not freeze an installer path that differs across macOS and Windows releases.

How do you add the local server in Cursor?

Cursor supports MCP servers and its CLI exposes commands to list servers and inspect tools. Use Cursor’s MCP settings to add a local stdio server, then enter the exact OneMira executable and arguments from the installed OneMira documentation. A conceptual configuration has this shape: 

{
  "mcpServers": {
    "onemira": {
      "command": "/absolute/path/to/onemira",
      "args": ["mcp", "serve"],
      "env": {
        "ONEMIRA_NOTES_ROOT": "/absolute/path/to/OneMira"
      }
    }
  }
}

This is a shape, not a promise that every release uses those exact argument names. Copy the command from the installed docs or app, then keep the notes root as narrow as possible. Do not set it to ~ or the entire drive.

Detailed model render of the OneMira C1 side control and clip
Physical capture and MCP retrieval are separate boundaries. Adding Cursor does not change how C1 records or transfers audio.

How do you verify the connection objectively?

Cursor’s official CLI reference lists cursor-agent mcp list and cursor-agent mcp list-tools <identifier>. Use them when available in your installed version: 

cursor-agent mcp list
cursor-agent mcp list-tools onemira

Then run a four-part test:

  1. Discovery: Cursor shows the OneMira server as connected.
  2. Surface check: tool names and parameters match the OneMira documentation; no unexpected shell, network, or whole-filesystem tool appears.
  3. Known-answer read: search for a unique phrase in the test note and confirm the returned excerpt and source path.
  4. Negative scope test: ask for a file outside the configured notes root and confirm the server refuses or cannot access it.

Record the server version, Cursor version, configuration path, tool list, and test result. A green “connected” indicator alone does not prove that the right data is reachable or that scope is enforced.

What data can cross the boundary?

There are two hops. The local MCP tool reads a note and returns text to Cursor. Cursor may then send that returned text to the model selected in Cursor according to Cursor’s and the model provider’s terms. A local MCP server limits how context is retrieved; it does not guarantee that retrieved context stays on the computer.

Use progressive disclosure:

  • search metadata and short excerpts first;
  • retrieve a full note only when it is relevant;
  • exclude sensitive folders by default;
  • prefer read-only tools unless a write is explicitly needed;
  • review any agent-generated file change as a diff.

How do you troubleshoot failures?

Symptom Check Do not do
Server will not start Absolute executable path, permissions, quoting, app version Replace it with an unknown package
Connected, no tools Server logs, protocol handshake, installed feature version Add broad filesystem permissions
Tool returns no notes Notes root, sync state, known test phrase, path case Point the root at the whole home folder
Windows path error JSON escaping and absolute path form Copy a macOS path literally
Unexpected tool call Cancel, inspect tool description and arguments Approve because the server is “local”

How do you remove access cleanly?

Disable or delete the OneMira server entry in Cursor, restart the host, and verify it no longer appears in the MCP list. Remove any environment credentials that were added specifically for the server. The notes remain ordinary local files; removing MCP access does not delete them.

For the broader context design, read From conversation to context. For MCP’s risk boundary, follow the official security sources below.

Sources and further reading