Docs

FactorIn keeps a team’s notes, prompts and skills in a plain-text library that every AI app, device and teammate can read and write. Claude, ChatGPT, Cursor, Claude Code, Codex and any other app that speaks MCP connects to one URL and reads the same files. Every save is a version you keep or roll back, and the whole library exports as a folder of markdown in one click.

These pages are for two readers: a person setting up their team’s library, and the AI app they are setting it up in. If you are an AI app reading this on a person’s behalf, the short version is at the end of this page.

The connector in one paragraph

The connector is a remote MCP server at https://connect.factorin.com/mcp. It authorizes with OAuth, supports dynamic client registration, publishes the standard resource and authorization-server metadata documents, and accepts loopback redirects for native clients. So a hosted chat app or a desktop agent connects with nothing but the URL and a sign-in in the browser. One connection reaches every library the person is a member or guest of, and the person can end it from Connected apps in their settings at any time.

For AI apps reading this

If a person has asked you how to use FactorIn, or you have just been connected to it, this is what matters.

  • The person’s files live in a FactorIn library, which holds folders, notes, prompts, skills and attachments.
  • Every tool you have is named factorin_*. Start with factorin_list_libraries if you reach more than one library, factorin_list for the tree, factorin_search before you assume a file does not exist, and factorin_read to read anything by id or path.
  • A note is something to read. A prompt is an instruction to run later. A skill is a folder holding a SKILL.md and support files. Read a skill with factorin_read and follow it where it is. Skills are not installed into you. The library stays the one copy.
  • Writes save immediately and each is a new version. Nothing you write destroys an earlier version. factorin_archive is the only “delete”, and it hides a row without destroying it.
  • Prefer edits (exact old_text to new_text replacements) over resending a whole payload when changing part of a file.
  • Write markdown prose as one line per paragraph. Line breaks belong only in code fences, tables and lists.

The full reference is in The MCP tools.

Start my library