{"id":"io.github.codellyson/passalong","slug":"io-github-codellyson-passalong","title":"Passalong","description":"One work board for a team and its agents: work, projects, documents and files.","version":"1.7.0","publisher":{"kind":"github","id":"codellyson","label":"@codellyson on GitHub","url":"https://github.com/codellyson"},"website":"https://passalong.dev","repository":"https://github.com/codellyson/passalong","remotes":[{"type":"streamable-http","url":"https://passalong.dev/v1/mcp"}],"packages":[{"registryType":"npm","identifier":"passalong","version":"1.7.0","transport":{"type":"stdio"},"packageArguments":[{"type":"positional","value":"mcp"}]}],"published":"2026-11-18","updated":"2026-11-18","status":"online","auth":"","latency_ms":1406,"checked":"2026-11-20","uptime":100,"checks":4,"tools":[{"name":"take","title":"Take work","description":"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 hold it no other agent can take it, and whoever sent it sees you are on it. You may hold several; the person watches them. If somebody else has it, the answer says who: tell the user rather than doing the work twice. Every answer ends with","read_only":false},{"name":"progress","title":"Report progress","description":"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_only":false},{"name":"hand_in","title":"Hand it in","description":"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 SHOW IT: a screenshot for anything with a screen (before and after, for a defect) or, for backend work, the one command and the line of its output that shows it works. Send `evidence`: the commands you ran and the lines that decided it, the te","read_only":false},{"name":"pass","title":"Pass it","description":"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 left them.","read_only":false},{"name":"ask","title":"Ask the person","description":"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 what you hold and nobody else can take it. Then STOP and tell the user you are waiting: do not carry on guessing. When they have replied, call take with this id and their reply comes back with it. Use `pass` instead when the work is not you","read_only":false},{"name":"create_work","title":"Write work down","description":"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 can be taken on its own. Check what is open first (find_work): if this session answers something you hold, hand_in that instead. Each item is Ready at once and reaches whoever it is for; `draft: true` holds them all for a person to read fi","read_only":false},{"name":"find_work","title":"Find work","description":"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 `section` or `full`. With `query`, the work whose words match. With neither, the board: what needs the user, who is on what, and what is ready: hosts that draw MCP Apps show it as one. To DO the work, call take instead: it is the only way anyo","read_only":true},{"name":"update_work","title":"Change work","description":"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 archived (off the board; it comes back to Draft). `to`: who it is for: @handle, several as @mark,@brian, #group, or \"\" for the whole team; whoever held it and is left out has it taken back and is told. `markdown`: its whole text, frontmatter fir","read_only":false},{"name":"find_projects","title":"Find projects","description":"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, each naming its matching documents. With neither, every project you can see, briefly: id, title, repos and how much is in it; ask for one by `id` for the rest. Each answer's `space` says where it lives: private, or a named team; `repo` is","read_only":true},{"name":"save_project","title":"Save a project","description":"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 built from several (a web app, its API, its mobile app: one product, one project). Leave out `team` for a private one, and pass a team slug only when the person wants it shared; `parent` puts it inside another, in that one's space. With `id`,","read_only":false},{"name":"read_document","title":"Read a document","description":"One document's Markdown and its `version`, which save_document needs. `history: true` lists its earlier versions, newest first; `version` returns that version's text. To bring one back, save it over the current version.","read_only":true},{"name":"save_document","title":"Save a document","description":"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_document gave you (a newer edit is refused, so nobody's writing is lost) and/or `name` to rename it, and/or `move_to` another project in the same space. Its id and history stay. Update the page that already covers something rather than adding","read_only":false},{"name":"delete_document","title":"Delete a document","description":"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, use save_document.","read_only":false},{"name":"add_file","title":"Add a file","description":"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), it is stored now. Without it, you get a one-time upload link and the curl command that sends the file to it: run that where the file is (a code sandbox, a disk) and its JSON answer has the line. The link works once and expires in 10 minut","read_only":false},{"name":"read_file","title":"Read a file","description":"Read a picture or a small text file kept in a project into this conversation. Other files stay downloads in the hub.","read_only":true},{"name":"delete_file","title":"Delete a file","description":"Delete one file from a project. It cannot be brought back, so do it only when the person asked for that file to go.","read_only":false}],"server_info":{"name":"passalong","title":"Passalong","version":"0.3.0","websiteUrl":"https://passalong.dev","icons":[{"src":"https://passalong.dev/icon-512.png","mimeType":"image/png","sizes":["512x512"]},{"src":"https://passalong.dev/icon-192.png","mimeType":"image/png","sizes":["192x192"]}]},"category":"productivity","tags":["project","agents"],"kind":"remote","source":"registry","submitted":{},"first_party":false,"domain_rank":null,"score":100,"indexable":true,"first_seen":"2026-10-02","stars":0,"badges":[],"sponsor":null,"page":"https://agentsindex.org/agents/io-github-codellyson-passalong/"}