Developers
Pilla MCP server and API
Connect an approved AI client or integration to Pilla. The MCP server exposes role-scoped tools for operational workflows while the REST API provides versioned HTTP endpoints.
Connect through MCP
Paste this URL into an AI app as a custom MCP server. The app should sign in through Pilla when asked. Deliberate API integrations can instead send a Pilla API key as a bearer token.
https://yourpilla.com/api/mcpAuthorization: Bearer pk_live_...- ChatGPT. Settings, then Connectors. Add a custom connector with the URL above and sign in when asked.
- Claude. Customize, then Connectors. Add the URL and sign in when asked.
- Grok. Add the URL as an HTTP MCP server, then sign in from the MCP servers list.
- Cursor. MCP settings. Add the URL as an HTTP server and sign in when asked.
- Perplexity. Connectors. Add a custom connector, choose Streamable HTTP, and sign in when asked.
- API key. If the app cannot sign in, create a key in Pilla and send
Authorization: Bearer pk_live_...on every request.
Build against the REST API
The current stable base URL is https://yourpilla.com/api/v1. Most REST endpoints use a Pilla API key as a bearer token. The API-key management endpoints use the signed-in Pilla web session because they create and revoke credentials.
Send a unique Idempotency-Key with requests that change data. Reusing it for the exact same request safely replays the first response for 24 hours. Reusing it for different request data returns 409.
POST to /reports/workflow-runs or /reports/workflow-steps to report on a date range, with optional team, tag and status filters. These requests are read-only and return a fresh report each time. They do not use an Idempotency-Key.
Backward-compatible additions stay in v1. A breaking contract uses a new versioned base path. Deprecated operations will be marked in OpenAPI and carry Deprecation and Sunset response headers before removal.
When to use Pilla
- Show me overdue workflows and the teams responsible for them
- Summarise the evidence recorded in this workflow run
- Find a workflow template for a recurring operational process
- Show recent workflow activity for my teams
Available domains
- workflow management
- workflow runs
- workflow evidence
- teams
- team communication
- activity log
- workflow templates
Permissions and safety
API keys linked to a user inherit that user's role and team access. Account-level keys are available to administrators and carry account-level access. Workflow reports require an API key linked to an active user.
Tool descriptions and annotations identify read-only, destructive, open-world and idempotent behaviour. Clients should show the exact action and obtain confirmation before consequential writes.
Pilla is ai work management for deskless teams. It does not provide shift scheduling, payroll, HR management or leaderboards.
Pilla also registers a small set of public, read-only WebMCP tools as a progressive enhancement for compatible browser agents. WebMCP is experimental and does not replace the authenticated MCP server.
Machine-readable resources
- OpenAPI 3.1https://yourpilla.com/openapi.json
- Interactive API referencehttps://yourpilla.com/api-docs
- Agent guidehttps://yourpilla.com/agents.md
- ARD manifesthttps://yourpilla.com/.well-known/ard.json
- MCP server cardhttps://yourpilla.com/.well-known/mcp/server-card.json