# Codellyson Passalong MCP server

Source: https://glimind.com/server/mcp-registry%2Fio.github.codellyson%2Fpassalong
Registry id: `mcp-registry/io.github.codellyson/passalong`
Status: live (checked 2026-11-22T15:12:07.501Z)

## Measurements (30 days)

- Uptime: 99.89%
- Checks: 426
- Outages (90 days): 1

## Install

```json
{
  "mcpServers": {
    "codellyson-passalong-mcp-server": {
      "type": "http",
      "url": "https://passalong.dev/v1/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http codellyson-passalong-mcp-server https://passalong.dev/v1/mcp
```

## Tools (17)

- `accounts`: Manage multiple accounts on this machine.
- `add_file`: Put a picture or any other file into Passalong and get back the markdown line that points at it. With `file` (a file the user gave you, filled in by the client)
- `ask`: You need the person's answer before you can go on. Ask one clear question, with the context it needs to be answered without opening your conversation. You keep 
- `create_work`: Write down work someone must still do (one piece, or several at once): a plan broken into steps, or every defect a test run turned up, each its own item so each
- `delete_document`: Delete one document, with its earlier versions. It cannot be brought back, so do it only when the person asked for that document to go; to change what it says, 
- `delete_file`: Delete one file from a project. It cannot be brought back, so do it only when the person asked for that file to go.
- `find_projects`: With `id`, one project: its documents, files and the projects inside it. With `query`, the projects whose name, description or any document mentions those words
- `find_work`: READ work without taking it. With `id`, that piece of work: its markdown, read only; work over 20,000 characters comes back as an outline unless you ask for `se
- `hand_in`: Finished here, with proof. IT IS FINAL: the work goes to Done with what you showed, and nobody reviews it after you (anyone can reopen it with a reason). So SHO
- `pass`: Not yours to do, or you are stuck: give it back with the reason. It is open again, and the reason goes to whoever is next: say why, or they start where silence 
- `progress`: Say you are still on what you hold, with a one-line note the hub shows. 30 minutes without one marks it stalled. If the answer says you no longer hold it, stop.
- `read_document`: One document's Markdown and its `version`, which save_document needs. `history: true` lists its earlier versions, newest first; `version` returns that version's
- `read_file`: Read a picture or a small text file kept in a project into this conversation. Other files stay downloads in the hub.
- `save_document`: Write what someone needs to know into a project. With no `document`, a new one: `name` and `body`. With `document`, change it: `body` with the `version` read_do
- `save_project`: With no `id`, make a project, after find_projects shows none fits: a `title` and a short `description`, and its `repo` when it has one, or `repos` when it is bu
- `take`: Say you are doing it, and get it. With `id`, that piece of work. With no id, the next thing waiting for `repo`: always a new one, never what you hold. While you
- `update_work`: Change work that exists, when the person asks or when you wrote it. `status`: ready (whoever it is for may take it), draft (held for a person to read), or archi

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.
