This page explains the current MCP truth for Provenote.
In plain language: Provenote already exposes a first-party MCP server, so coding-agent hosts can work with the same notebooks, drafts, research threads, and auditable runs that exist in the local workbench.
If your starting problem is still “I have a long messy conversation, note dump, or copied web thread,” start with Long Context To Structured Notes first. MCP is the carry-forward surface for those outcome objects, not the product’s first doorway.
If you want a direct terminal/operator path instead of a host integration, use runbooks/operator-cli.md. That runbook covers the first-party CLI surface without pretending MCP and CLI are the same thing.
Use the MCP server when you want a coding agent to:
The current product center is still Provenote’s source-grounded outcome path. MCP is the integration surface, not the brand center.
This page does not claim that Provenote is:
Vendor names on the linked integration pages are descriptive compatibility targets only.
| Surface | What it is today | What it is not |
|---|---|---|
| MCP | the host-facing integration layer for Provenote outcome objects | not the product center and not a partnership claim |
| Operator CLI | the terminal-facing first-party operator surface | not a renamed MCP server or plugin package |
| Public Skills language | a boundary question, not a shipped public product line | not a catalog or marketplace surface today |
| OpenClaw | public-ready OpenClaw-compatible bundles and a ClawHub submission pack live under examples/hosts/openclaw |
not an official listing that is already live |
| Official MCP Registry | the official registry already returns a live websiteUrl-backed entry for provenote-mcp, while no supported public package or public remote-server artifact from this repo is published yet |
not a package-backed public artifact or a broader marketplace-live claim beyond that entry |
| Plugin / marketplace / directory | a separate publication question even when repo-owned starter bundles exist | not implied by the current MCP server |
If you need the full boundary map before opening a host-specific page, start with project-status.md and distribution.md.
The repository ships a first-party MCP entrypoint:
provenote-mcp
It is exposed through pyproject.toml and implemented in ../packages/core/mcp/server.py.
The current outcome-first tool groups include:
draft.*research_thread.*auditable_run.*Those outcome groups are wired through dedicated API-client helpers and repo CI coverage so the MCP surface stays aligned with the same draft, research-thread, and auditable-run routes used by the local workbench.
The server also keeps a few controlled utility surfaces such as knowledge.search, chat.run, model.inspect, settings.mutate, ui_test.control, and computer_use.control.
If you want the narrowest host-specific verification loop instead of a generic overview, start with Use Provenote with OpenCode. That page now links the host setup step back to the repo-owned MCP entrypoint and the concrete outcome-tool families.
OpenClaw now has a stronger repo-owned rung even though it still sits below listing-live truth. The repo ships public-ready OpenClaw-compatible bundles plus a ClawHub submission pack under ../examples/hosts/README.md, but that still does not mean a ClawHub listing is already live.
The same honesty rule applies to the official MCP Registry:
provenote-mcpprovenote-mcplive registry entry: yes, package-backed public artifact: no, and other host marketplace listing: noprovenote-mcp.OPEN_NOTEBOOK_URL and OPEN_NOTEBOOK_PASSWORD according to the current runtime contract.The fastest repo-documented local path still starts at quickstart.md.
If you want checked-in host artifacts instead of only setup pages, inspect ../examples/hosts/README.md. That index now includes public-ready starter bundles for Claude Code, Codex, Cursor, and OpenCode local MCP usage alongside the OpenClaw-compatible bundles and the ClawHub submission pack.
If you specifically want the repo-owned OpenClaw install path, use Use Provenote with OpenClaw-compatible bundles. That page is intentionally scoped to public-ready bundle distribution and submission-ready materials, while keeping listing-live wording deferred.
If you want the current submission packs for official discovery surfaces, start with:
| Surface | Current truth | Not claimed |
|---|---|---|
host pages under docs/integrations/ |
compatibility through the first-party MCP server, with repo-backed starter bundles where available | official partnership, bundled integration, plugin, marketplace, or directory status |
provenote-mcp |
the repo-owned stdio MCP entrypoint | a universal guarantee across every host/runtime mode |
provenote |
the first-party terminal/operator surface for outcome inspection and narrow outcome workflows | a host plugin, marketplace package, or MCP replacement |
| public skills surface | tracked public-ready skill packets now exist under ../public-skills/ for host-specific submission flows |
a public skills catalog, live marketplace listing, or host-specific skills program endorsement |
| OpenClaw | public-ready bundles and a repo-owned submission pack exist | an official ClawHub listing that is already live |
| plugin / marketplace / directory presence | external-only or intentionally not-live today | shipped listing-live truth |
Before you treat any host page as a real compatibility claim, verify the same three layers:
provenote-mcp as the tracked entrypoint.Run the repo-owned MCP contract check:
bash tooling/scripts/runtime/run_uv_managed.sh run pytest tests/test_mcp_server.py -q
That keeps host guides in the compatibility through MCP bucket instead of drifting into bundled integration, plugin, or marketplace wording.
If you want to see why this MCP surface matters beyond setup syntax, read MCP research context for coding agents.
Provenote’s first-party MCP entrypoint runs over stdio.
That keeps the repository-side truth simple:
Host-specific MCP setup formats change over time, so follow the official host docs linked on each integration page for the exact configuration syntax.