Every droid gets its own identity, its own GitHub scopes, its own Jira reach, its own Slack channels. Every PR comment, every Jira update, every commit lands in an append-only audit log. If a droid goes off the rails, one click stops every credential it had.
The AgentValet CLI signs you in via your browser, generates an RS256 keypair, registers your Droid as an agent, and writes ~/.factory/mcp.json (user-scoped, every project on this machine). No copy-paste, no IDs.
# In your project directory npx @agentvalet/register # Browser opens. Sign in. Done. # The CLI writes: # ~/.factory/mcp.json - MCP entry, user-scoped # CLAUDE.md - governance instructions # With --project, it scaffolds the whole droid instead: # .factory/mcp.json - MCP entry, project-scoped # .factory/droids/agentvalet.yaml - governance droid # .factory/commands/av-status.md - /av-status slash command # .factory/commands/av-register.md - /av-register slash command
npx @agentvalet/register in your project directory./av-status if you set up with --project), then approve platforms in the AgentValet dashboard. Droid agents can now call GitHub, Jira, Slack, and more, all scoped and logged.Full walkthrough in the docs →
/av-status, /av-register slash commands scaffolded into this repo instead of a global config? Run npx @agentvalet/register --project.The CLI is the recommended path. If you'd rather edit the config yourself, here's the equivalent .factory/mcp.json:
{
"mcpServers": {
"agentvalet": {
"command": "npx",
"args": ["-y", "@agentvalet/register", "mcp-server"]
}
}
}
Factory Droid engineering agents can access GitHub, Jira, Slack, and other platforms without credentials stored in project config.
One command. The browser does the rest. Free to start, no credit card.