Factory Droid + AgentValet — Governed MCP for autonomous engineering agents

Configuration

Two ways to add AgentValet

Use the droid mcp add command or create the config file manually.

via CLI (recommended)

droid mcp add agentvalet https://api.agentvalet.ai/mcp/v1/YOUR_OWNER_ID

or create the config file

.factory/mcp.json

{
  "mcpServers": {
    "agentvalet": {
      "url": "https://api.agentvalet.ai/mcp/v1/YOUR_OWNER_ID",
      "transport": "streamable-http"
    }
  }
}

Setup

Get connected in 3 steps

1

Run npx @agentvalet/register — generates an RS256 keypair, records your agent in the registry, and outputs your OWNER_ID.

2

Add via droid mcp add agentvalet https://api.agentvalet.ai/mcp/v1/… — or create .factory/mcp.json with the config above.

3

Approve platforms in the AgentValet dashboard. Droid agents can now call GitHub, Jira, Slack, and other platforms — all scoped and logged, no credentials in project config.

What changes

Engineering agents with governed platform access

Factory Droid engineering agents can access GitHub, Jira, Slack, and other platforms without credentials stored in project config.

No credentials in config

Droid project configs contain no API keys or tokens. Credentials live in AgentValet's HSM-encrypted vault, decrypted only at call time.

Per-platform scoping

Droid gets GitHub repo access but not org admin. Jira read but not delete. Scopes are enforced at the proxy, not just declared.

Full call-level audit

Every GitHub PR comment, Jira ticket update, or Slack message logged with agent ID, timestamp, and outcome.

Instant revocation

Suspend a Droid agent or remove a platform in one click. No need to rotate keys across every project config.

AgentValet for Factory Droid

Two ways to add AgentValet

Get connected in 3 steps

Engineering agents with governed platform access

Ready to connect Factory Droid?