provenote

Use Provenote With Cursor

This page documents the current compatibility story for Provenote and Cursor.

In plain language: if Cursor is your day-to-day coding environment, Provenote can join that workflow through MCP so the editor can work with auditable runs, research threads, and notebook drafts instead of treating them as off-screen context.

Current Safe Claim

Provenote works with Cursor via MCP.

That is the strongest public claim the current repository can support. This page does not claim an official plugin listing, marketplace publication, or any partnership with Anysphere.

What Works Today

Current fit through MCP:

Why This Claim Is Safe

Minimal Setup

  1. Start Provenote locally and confirm the API is reachable.
  2. Make sure the environment used by Cursor can run provenote-mcp.
  3. Add Provenote as an MCP server using Cursor’s current MCP setup flow.
  4. If you are targeting a non-local Provenote API, set OPEN_NOTEBOOK_URL and OPEN_NOTEBOOK_PASSWORD before the MCP process starts.

Repo-Backed Proof Loop

If you want to verify this page instead of trusting the wording, use this local proof loop:

  1. Confirm the MCP script surface exists in ../../pyproject.toml as provenote-mcp.
  2. Confirm the server exposes outcome-first tool groups in ../../packages/core/mcp/server.py:
    • draft.*
    • research_thread.*
    • auditable_run.*
  3. Confirm the typed schemas in ../../packages/core/mcp/schemas.py.
  4. Run the repo-owned MCP contract test:

    bash tooling/scripts/runtime/run_uv_managed.sh run pytest tests/test_mcp_server.py -q
    
  5. Start Provenote locally with the repo-documented path in ../quickstart.md.
  6. In Cursor, register provenote-mcp as an MCP server and start with one read-first step:
    • list drafts
    • list research threads
    • list auditable runs
  7. Only after the list/read step is visible, move to a write-oriented action such as verifying a draft or downloading auditable markdown.

If you want a checked-in local host artifact instead of only this page, start with ../../examples/hosts/cursor/provenote-outcome-bundle/README.md and keep ../../examples/hosts/README.md as the broader host-artifact index.

What To Inspect

Surface Why it matters
../../pyproject.toml Proves the repo actually ships provenote-mcp
../../packages/core/mcp/server.py Shows the concrete outcome-tool families Cursor can call
../../packages/core/mcp/schemas.py Shows the typed request shapes behind those tools
../../tests/test_mcp_server.py Shows the repo keeps a real MCP contract test
../mcp.md Keeps this host page anchored to the broader MCP truth
../proof.md Maps the compatibility wording back to inspectable repo surfaces

Good First Workflows

Current Boundary

Claim Boundary

Bucket What this page can say
Safe now Provenote works with Cursor via MCP; Cursor can register MCP servers; Provenote ships a first-party stdio MCP entrypoint
Not claimed official Cursor plugin, marketplace publication, partnership, or bundled distribution
Deferred / proof gap public Skills distribution, OpenClaw support, generic works with every MCP host, hosted/team/autopilot surfaces

Use the latest official docs for exact setup and naming guidance: