Bridge MCP local do sync-agents: liga a IA de quem conecta ao canal de alinhamento, escopado pelo repositório git
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"sync-agents-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# sync-agents-mcp Bridge MCP local do [sync-agents](https://github.com/AsaGeki/sync-agentes): 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 ```bash 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`](https://github.com/AsaGeki/sync-agentes/blob/main/CONECTAR_MCP.md).
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.