Skip to content
Changelog

Docs, starting with MCP

  • Docs
  • MCP
  • AI
  • Website

Parahuman has docs, at parahuman.co/docs. The first guide is the one people ask for most: how to connect an AI agent over MCP, from your client's menus through to what it can reach once it is in.

Those instructions used to live in a changelog entry. An entry is a good place to announce something and a poor place to keep it right, because it is dated, it is not meant to change, and it goes stale the first time a client moves a menu. The guide is maintained in one place now, and the announcement points at it.

Setup for the client you actually use

Claude, Claude Code, ChatGPT, Codex, Cursor, VS Code, Zed and Goose each get their own steps, with a copy button on every command and config block. Anything else that speaks streamable HTTP and OAuth gets the server address and what to do with it.

The rest of the page is the part that is hard to find elsewhere: what an agent can reach, what it cannot, what each of the six permissions grants before you approve it, and how to disconnect one. There is a set of prompts worth trying once you are connected, and an FAQ.

Hand the page to your assistant

The button at the top of a page copies it as markdown, hands you a link to that markdown, or opens it in a tab. Beside those, Claude and ChatGPT open the page in a new conversation with the question already written, for you to read and change before you send it.

Only those two are listed. A chat earns a place there by having an address that takes a written question, and an editor has none, so Cursor gets a one-click install button in its own section instead. The docs are in llms.txt too, for an assistant that goes looking on its own.

One page is not a documentation set

MCP is what people are setting up right now, so it went first. More pages follow as they earn their place, rather than a nav full of stubs.

  • MCP The rate limit on the server is doubled on every plan. One question to an agent fans out into a workspace lookup, a keyword list, an analytics call and several pages of mentions within seconds, which left a trial account one follow-up away from the old ceiling
  • MCP A request arriving with an Origin that names a site other than ours is refused before the token is read. Hosted clients send no Origin at all, so Claude, Cursor and Claude Code are untouched
  • Auth An unverified app name on the approval screen now shows a neutral seal instead of an orange warning triangle. Every AI client registers itself and none of them can prove a name, so the alarm fired on the ordinary case. Orange is kept for the permissions that change things, where it marks a real difference
  • Auth The note under an unverified name asks something you can answer. For a website it says to check the address. For a desktop app it says to allow this only if you just asked that app to connect, because the address there is a port on your own machine and any program can use it
  • Support Our address is hello@parahuman.co everywhere, including the downgrade request on the billing page
  • Website The button back into the product reads Open app rather than Dashboard

  • Docs Reopening a link to a section left you wherever you last were, because the browser restores that position and it overrides the address. The page moves to the named section once it has loaded, and again after the font settles
  • Accessibility A trackpad flick at the top of a page flashed the skip link, which sat just above the pinned header. Nothing above the header can be dragged into view now, and the link still appears in full on the first tab
  • Mobile Long inline code wraps instead of pushing the page sideways, and the docs bar stays on one line
  • Billing The pricing cards fit a narrow window