Agents

Give your agent access to the work, not the whole company.

Springroll exposes payroll and workforce tools through MCP and REST. Each agent key belongs to one organization and only exposes the scopes you grant.

Use the harness you already have

Springroll uses a remote HTTP MCP server, so you can connect it to Codex, Claude Code and other MCP-compatible clients. Create an agent key in the Springroll dashboard first. Use that key as the bearer credential when you configure the connection.

Codex
codex mcp add springroll --url https://mcp.springroll.sh/mcp

# Then configure your Springroll agent key as the MCP bearer credential
# using your Codex credential or plugin configuration.
Claude Code
claude mcp add --transport http springroll https://mcp.springroll.sh/mcp

# Then configure the Springroll agent key as the Authorization bearer
# credential for this remote MCP server.
Other MCP clients
URL: https://mcp.springroll.sh/mcp
Authorization: Bearer spr_live.akey_...

Scopes decide what an agent can do

A key can be read-only or allowed to make specific changes. Payroll approval is separate from payroll calculation. Time and expense review have their own permissions. Revoking a key cuts off both MCP and REST access.

AreaExamples
PeopleRead workers, add workers, update workforce records.
Time and expensesRead entries, submit new entries, approve or reject reviews.
PayrollRead runs, calculate a run, approve a run when tax data is complete.
OnboardingRead company setup and update onboarding context.

REST is available too

If your automation does not use MCP, call the agent API at https://api.springroll.sh/agent/v1. The same agent key and scopes apply. The OpenAPI document is available at api.springroll.sh/openapi.json.

Payroll still has a compliance boundary.

Springroll does not invent withholding. A payroll run cannot be approved until validated tax data is present. Payment and tax providers stay separate so you can choose the services you want to use.

Agent platform references