peerforge▌
Sign inTry it free

Paste one line.
It does the rest itself.

Give your assistant the line below. It reads the instructions there, asks you to approve it once in your browser, collects its own key and connects. You do not have to create anything, copy anything or install anything.

Say this to Claude, Cursor, Copilot — whatever you use

Fetch https://app.peerforge.app/agent-setup.md and follow the instructions.
  • Claude Code
  • Cursor
  • GitHub Copilot
  • Windsurf
  • Cline
  • Zed

And anything else that can read a web page and make a request.

What happens when you do.

1It shows you a codeSomething like WXYZ-2468, and asks you to open a page and type it in. That page is on this site, and you will already be signed in or can sign in there.
2You approve it onceThat is the only thing you do. Approving cuts a key for your workspace and hands it straight to the assistant — you never see it, copy it or store it.
3It connects itselfIt adds PeerForge to its own configuration and starts publishing. Nothing was installed, so nothing needs updating later.

You can see every assistant you have connected, and take a key away again, on your API keys page.

What it can do once connected.

Publish a document

It writes the page and gets back a link for you to send round.

Publish a new version

The link never changes. The old version stays where it was, with the comments people left on it.

Read the comments back

Not just the words — the sentence each one was written about, and who wrote it.

Find out what it just broke

When a rewrite removes a sentence somebody commented on, it is told which comments came loose, by name.

Reply, and close a thread

So the person who raised it sees an answer where they raised it.

Change who can see it

Public, unlisted, anyone at your company, or a named list.

If you would rather set it up by hand

The server is hosted, so there is no package to install and nothing to keep up to date. Make a key on your API keys page and point your client at it.

Claude Code

claude mcp add --transport http peerforge https://app.peerforge.app/api/mcp \
  --header "Authorization: Bearer pf_your_key"

Cursor, Windsurf, Cline, Zed, and anything else with a JSON config

{
  "mcpServers": {
    "peerforge": {
      "type": "http",
      "url": "https://app.peerforge.app/api/mcp",
      "headers": { "Authorization": "Bearer pf_your_key" }
    }
  }
}

Eight tools: publish, update, read, get_metadata, list_comments, reply, set_thread_resolved and share. If your client cannot send a header, add ?key=pf_your_key to the URL instead — though a key in a URL ends up in shell history and server logs, so the header is better.

Everything is plain HTTP as well, if MCP is not available to you. The setup document lists every endpoint.