Docs

What you can ask Statey to do.

Statey exposes its capabilities to your agent as MCP tools. You don't call them directly; you describe what you want in plain language and the agent selects the tool. This page lists the available tools, what each one does, and example requests that map to them.

Connecting a client

Add the Statey MCP endpoint to any MCP client (Claude, Claude Code, Cursor). Two starter templates, Tasks and Tickets, are available when you create your first collection.

mcp add mcp.statey.ai

Getting your bearings

Two tools provide context: one lists what exists in the workspace, the other returns the schema for a single collection.

get_workspace_overview

Returns your collections, record counts, schema versions, active triggers, actors, and the calling agent's permissions.

Example requests

what's in my workspace?

give me the lay of the land

describe_collection

The full schema for one collection: every field and its description, relations, sample records, and available indexes.

Example requests

what fields does Tasks have?

how are tickets structured?

Shaping your data

Create collections from a description, and evolve them over time. Additive schema changes apply immediately; breaking changes require confirmation.

create_collection

A new collection from a plain description or a starter template (Tasks or Tickets). Field descriptions are required; they tell the agent what each field means.

Example requests

spin up a ticket tracker

make a customers collection with name, plan, mrr

update_schema

Evolve a collection. Additive changes (a new optional field, a relaxed enum) apply immediately; breaking changes require explicit confirmation. Returns a diff.

Example requests

add a renewal date to customers

add an 'urgent' status option

Working with records

Create, read, query, update, and delete records. Writes are attributed and guarded by optimistic concurrency.

create_records

Insert 1–100 records at once, validated all-or-nothing so a bad row never lands half-written.

Example requests

new ticket: runner retry loop drops deliveries, high priority

import these 30 tasks

get_record

Fetch one record by id, optionally resolving one level of its relations (a linked task, a parent customer).

Example requests

pull up TIC-206

show that customer + the linked deal

query_records

Filter, sort, and paginate (up to 200 per page) with a total count. Grouping by a field returns per-group counts in a single call.

Example requests

open tickets grouped by assignee

what's in progress rn?

update_record

A partial update guarded by optimistic concurrency. If the record changed in the meantime, the call returns the current version instead of overwriting it.

Example requests

move TIC-206 to in progress

bump that ticket to high priority

delete_record

A soft delete. The record drops out of queries but is retained.

Example requests

archive that ticket

drop the duplicate customer

Reacting to changes

Soon

Part of the phase-2 reactive loop. Every change emits an event; triggers match events and dispatch agents or webhooks.

create_trigger

Watch a collection for create, update, or delete events and dispatch an agent or webhook when they match a filter. Causation is tracked across cascades.

Example requests

when a ticket comes in, have triage-bot look at it

ping ops when inventory drops below 10

list_triggers · delete_trigger

See what automations are running and turn them off.

Example requests

what automations do i have?

turn off the triage trigger

get_queue_status

Per-agent backlog: pending count, the age of the oldest event, and whether the queue is paused.

Example requests

anything waiting on my agents?

is the queue backed up?

resume_queue

Resume a paused queue: replay each event in order, or reconcile the whole backlog against current state in a single pass.

Example requests

catch up on whatever piled up while the runner was down

Audit & usage

The activity log records what changed and why; usage reports consumption against your cap.

query_activity

Search the immutable log by collection, record, actor, action, or time range, and follow causation chains to see what triggered what.

Example requests

who touched this ticket and why?

what happened in tickets this week?

get_usage

Current-period consumption, spend, and remaining budget against your spend cap. Readable by agents as well as people.

Example requests

how much have i used this month?

how close am i to my cap?

Reference notes

This is the complete tool surface for the current release. All writes are attributed and recorded in the activity log. Tools marked Soon are part of the phase-2 reactive loop and are not yet available. The full MCP schema and field-level reference live in the developer docs.