sync-agents-mcp
Bridge MCP local do sync-agents: roda na máquina de quem conecta, lê o .git da pasta do projeto e conversa com o servidor sync-agents por HTTP. O repositório git onde o chat foi aberto define em qual projeto a IA escreve.
Rodar
uvx sync-agents-mcp
Não é pra rodar na mão: o app de IA (Claude Code, Cursor, Claude Desktop, VS Code, Codex) executa esse comando como servidor MCP stdio.
Variáveis de ambiente
| Variável | Pra quê |
|---|---|
SYNC_AGENTS_URL |
endereço do servidor (padrão http://127.0.0.1:8787) |
SYNC_AGENTS_TOKEN |
token pessoal, emitido por quem administra o servidor |
SYNC_AGENTS_REPO |
caminho do repositório, só pra app que não abre pasta de projeto (Claude Desktop). Também vale --repo <caminho> |
Configuração passo a passo por app: CONECTAR_MCP.md.
Metadata
Release files for sync-agents-mcp 0.3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| sync_agents_mcp-0.3.0.tar.gz | 14.3 kB | With provenance | Details for sync_agents_mcp-0.3.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| sync_agents_mcp-0.3.0-py3-none-any.whl | Python 3 | none | any | Details for sync_agents_mcp-0.3.0-py3-none-any.whl |
Total release size: 29.3 kB
Release files / sync_agents_mcp-0.3.0.tar.gz
| Download URL | sync_agents_mcp-0.3.0.tar.gz |
|---|---|
| Size | 14.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ed9f51cfe9044bd4d93330f1d9e188d04c4f53af0076108bca0863933f25aefd
|
|
BLAKE2b-256 checksum How to use checksums |
1f6fe6202dc3b460b24624a29eadf5cc39908231bb1be3e1e63a8abb1e520398
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 19, 2026.
Transparency logRelease files / sync_agents_mcp-0.3.0-py3-none-any.whl
| Download URL | sync_agents_mcp-0.3.0-py3-none-any.whl |
|---|---|
| Size | 15.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
579f468111caa3f1fa12a792b84bdd073d8f985c0c5e3de7b681269a487908d5
|
|
BLAKE2b-256 checksum How to use checksums |
f209b0ec069604b8e1de3ab72bfcc6896f1928cdf14dc9b1c2a89b1f669c7b12
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 19, 2026.
Transparency logSecurity for sync-agents-mcp 0.3.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for sync_agents_mcp-0.3.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 19, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.