agentsync

Install

Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.

npx agentmarket install connector/jarmstrong158-agentsync

About

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list and install config. Checked Oct 25, 2026.

Tools

1 read · 6 write · 0 delete · 2 not yet classified

Secrets

None asked for

Install scripts

Not scanned yet

Runs as

Python package

Tools (9)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

• add_collaborator

  Invite one or more people as collaborators on the shared repo so they can push to it. Use this when the repo already exists and you just want to grant partners access (provision() does this too, but only as part of first-time setup). This is how you build a team of more than two. github_username : one or more GitHub users, comma- or space-separated (e.g. "jarmstrong158" or "alice, bob, carol"). permission : pull | triage | push | maintain | admin (default push). Each invited user must accept the GitHub invitation before they can push. Requires the `gh` CLI authenticat…

• check_conflicts

  Detect conflicts between your branch and your partners' branches. Reports two levels: claim_overlap : set intersection of touched files (intent level) merge_conflict : a real dry-run merge via `git merge-tree` (textual) against_branch lets you check one specific branch; default checks every branch named in a peer's active claim. Your own branch is taken from your current claim. claim_overlap is intent-level, so it only exists where intent was declared. If against_branch names a branch no active claim mentions, claim_overlap is reported as an explicit {"status": "unknown"} object naming…

• claim

  Stake a claim on a unit of work, so a partner cannot start the same files underneath you. When to use this instead of the alternatives: claim : you are about to START work. Call it BEFORE editing, not after — a claim taken afterwards cannot prevent the collision it was meant to catch. survey : just look at who holds what, changing nothing. check_conflicts : you already hold a claim and want to know whether your branch now collides with a peer's. update_status : you already hold this claim and only the sta…

• finish

  Close the loop: mark your claim done AND open a GitHub pull request from your claimed branch into the default branch, so your work lands in review. note : PR body (falls back to your claim's existing note). title : PR title (falls back to your claim's task). draft : open the PR as a draft. Your branch must already be pushed. If a PR for the branch already exists, its URL is returned instead of erroring. Requires the `gh` CLI. The claim is marked done (with auto-captured `changed_files`) after the PR is opened.

• history

  The coordination timeline: who claimed, finished, or released what, and when — read from the git history of claims.json. Newest first. `limit` caps how many events are returned. Useful for 'what has my partner been doing?' without needing them online.

• provision

  Create the shared GitHub repository if it doesn't exist yet, then leave both collaborators ready to use the claim protocol. Run this ONCE, by one person, before anyone calls survey()/claim(). It is idempotent — safe to re-run; each step is skipped if already done. What it does, in order: 1. Ensure AGENTSYNC_REPO is a local git repo with at least one commit (creates the directory + a starter README if empty). 2. Create the repo on GitHub via `gh` (private unless private=False) and wire up the 'origin' remote, or reuse an existing remote/repo. 3. Push the default branch. 4. Se…

• release

  Abandon your current claim WITHOUT marking it done, freeing the files you were holding so a partner can take them over. Use this when you're dropping the task or stepping away — otherwise a crashed or abandoned claim blocks those files indefinitely (the only other exits are 'done' or manual git surgery). Pushes immediately. note : optional free text recording WHY you are dropping the claim, e.g. "blocked on the API rewrite, not started" or "handing over to Sam". It replaces the claim's existing note and is what a partner reads in history() when deciding whether to pick th…

• survey

  Pull the latest coordination state and report what every *other* agent has claimed: task, files touched, dependencies, branch, status, timestamp. Works for any number of collaborators, not just one. Each partner entry is annotated with `age_hours` and a `stale` flag (an in-progress claim older than AGENTSYNC_STALE_HOURS, default 24h) so you can spot a partner who may have crashed or wandered off still holding files. Call this before planning and again after finishing work.

• update_status

  Update your own claim's status (e.g. 'in-progress' -> 'done') and optionally attach a note for your partner. Pushes immediately. On 'done' the claim is auto-annotated with `changed_files` (your branch's diffstat vs the default branch). To drop a claim without finishing it, use release(); to finish AND open a PR, use finish().

Signals

Stars

0

Forks

0

Open issues

0

Weekly downloads

53

Last commit

Aug 6, 2026 (2 months ago)

Last release

Aug 2, 2026 (2 months ago)

Last package publish

Aug 2, 2026 (2 months ago)

From GitHub (fetched Oct 24, 2026) and the package registry.

Details

Registry name

io.github.jarmstrong158/agentsync

Version

0.2.0

Auth

No auth

Packages

pypi agentsync-mcp

License

PolyForm-Noncommercial-1.0.0

Repository

github.com/jarmstrong158/agentsync

First seen

Oct 24, 2026

Last checked

Oct 24, 2026

Source

Official MCP Registrygithub-graphql