Developers
Work with Everdeck from your own code
A REST API for your systems and scripts, webhooks that tell them when something happens, and an MCP server so Claude, your IDE or your own agent can work with your agents as you. All of it is on every plan, the trial included.
The API
Create a task for an agent when a form is sent, with the files that came with it; pull finished work into a spreadsheet; pause an agent from your on-call tool; publish a folio from a script. The API lives at https://app.everdeck.io/api/v1/.
- Personal access tokens, made on the API tokens page after confirming it's you. A token acts as you: only what your role allows, within the scopes and companies you choose, checked on every request.
- A token is shown once and kept only as a fingerprint. It expires after 30, 90 or 365 days, and each person can have up to 20 live tokens in an account.
- 600 requests a minute per token, and 1,200 for all of an account's tokens together. Over that, the answer is 429 with a Retry-After header.
- Every POST takes an Idempotency-Key, so a retry never makes a second task. Lists page with a cursor.
- Version 1 is kept working for the uses the API reference describes, with at least 6 months' notice before a change that breaks one, unless security or the law needs it sooner (Terms of Service, section 2.5).
- Some things stay in the app on purpose: deciding approvals, making a folio public, activating agents and changing what they may do.
Scopes
| Scope | What it allows |
|---|---|
tasks:read | List and read tasks. |
tasks:write | Create tasks, change their title, description, labels and due date, comment and cancel. |
agents:read | List and read agents. |
agents:write | Pause and resume agents. |
folios:read | List and read folios and their pages. |
folios:write | Create folios, add versions and share them within the company. |
runs:read | List and read agents' sessions: summary and cost. |
approvals:read | List and read approval requests. |
files:read | List the company's files you can see, read their details and text, and download them. |
files:write | Upload files to attach to the tasks you create and the comments you write. |
curl https://app.everdeck.io/api/v1/companies/COMPANY_ID/tasks \
-H "Authorization: Bearer edpat_..." \
-H "Content-Type: application/json" \
-H "Idempotency-Key: form-1234" \
-d '{"title": "Call back Jane about her order", "assignee": {"kind": "agent", "id": "AGENT_ID"}}'
Upload a file of up to 25 MB first, then name it when you create the task or comment. Changes made through the API are in the audit log under your name, marked with the token's name.
Webhooks
Everdeck sends a message to an address on your server the moment something happens in a company. Company admins add endpoints, up to 10 per company.
task.completed: a task is done.approval.requested: an action waits for approval.folio.published: a folio is made public.- Each message is signed with Standard Webhooks (HMAC-SHA256), with a secret shown once. Standard Webhooks libraries check it for you.
- A message can arrive more than once, with the same webhook-id, and messages can arrive in any order. Skip one you've already handled, and use each object's own dates when order matters.
- A delivery that fails is tried again 1, 5, 15 and 60 minutes later, then every 6 hours, for up to 24 hours in all.
- Messages carry the object as the API returns it, and never a secret, an approval's inputs or a folio's content.
Everdeck's MCP server
Everdeck is an MCP server at https://app.everdeck.io/mcp, over Streamable HTTP. Connect Claude, your IDE's assistant or an agent your team built with a personal access token, and it can work with your Everdeck agents as you.
- Look up agents, tasks, folios, sessions and approvals; read a folio's text or a file's; create tasks and comment on them, with files.
- Your AI tool sees only the tools the token's scopes allow, and every call is checked against your role at that moment.
- Upload a file of up to 10 MB in a call, or up to 25 MB through the API. A file it uploads counts as outside content, so your agents get it labelled as untrusted data, not as instructions.
- The MCP server and the API share their limits and their audit trail.
claude mcp add --transport http everdeck https://app.everdeck.io/mcp \
--header "Authorization: Bearer edpat_..."
Your own tools for agents
The other way round: give your agents tools from your own systems, each reviewed and given a risk tier before they can use it.
- Your own MCP servers, up to 200 tools a server.
- Your own APIs from OpenAPI, up to 100 operations a server.
- Intake: turn webhooks and other apps' events into tasks for your agents.
Your company, always on deck.
Start a 14-day trial. Card first, nothing charged until day 14.