ProtoNote

io.protonotePublished by protonote.ioOfficial publisherv1.1.0Updated Oct 24, 2026

Share prototypes for team review: publish HTML, reviewers pin notes, pull feedback back to apply.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

ProtoNote is a remote MCP server for sharing HTML prototypes with a team, collecting pinned reviewer notes, and pulling that feedback back to apply.

What you can do
Publish HTML prototypes so team members can review them in place. Collect reviewer feedback as notes pinned to specific parts of a prototype. Pull the gathered feedback back into the assistant's workflow so it can be applied.
When to use it
Useful when you build HTML prototypes and want an assistant to share them for team review, then bring the reviewers' pinned comments back to act on.
Requirements
A remote MCP endpoint at protonote.io, connected over streamable HTTP. OAuth authentication is required, so a ProtoNote account and sign-in are needed. No environment variables or headers are declared.
Before you install
Reviewers' feedback is stored and shared through ProtoNote's service, so prototype content and comments go to a third party. Publishing a prototype makes it visible to reviewers; check who can access it before sharing.

Installation

In SourceWeft

  1. Open ProtoNote in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.protonote%2Fprotonote/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "protonote": {
      "type": "http",
      "url": "https://protonote.io/api/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.1.0LatestSep 16, 2026

Score

56% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.