Skip to main content
MCP tools use @airctrl/sdk. Tool results contain structured JSON. Errors return safe codes and messages without exposing stored credentials. Use MCP prompt cookbook for one prompt per tool. Use MCP workflows for prompts that coordinate several tools safely.

Identity availability

A human PAT can use every API-backed tool on this page when RBAC permits it. Local helpers do not require API authorization. A Service Account sees only the tools that its API identity can actually use: All other tools are human-only and are not registered in Service Account mode. RBAC can still deny any listed operation when the Service Account lacks the required custom-role permission or project access.

Status and context

Service Account metadata

These metadata tools are human-only. Service Account creation, state changes, credential lifecycle and identity rotation are not MCP tools.

Record reading and creation

Record lifecycle and sharing

Record audit

Providers and gateway setup

Gateway tokens

Logs, usage and OpenTelemetry

Input rules

  • IDs are UUID strings. Copy them from instead of asking an agent to guess them.
  • Dates and timestamps use ISO 8601. day uses YYYY-MM-DD; since accepts a complete timestamp.
  • Pagination starts at offset: 0. Keep limit small when an agent only needs a summary.
  • accountId selects the account. It does not grant access to it.
  • projectId, recordId, gatewayId, credentialId and tokenId select resources. still checks RBAC and resource access.
  • Optional booleans must be real JSON booleans such as true, not strings such as "true".
  • Tools that create credentials or tokens can return a value only once. Save it immediately in an approved destination.
For write or destructive operations, ask the agent to repeat the target IDs and intended change before it calls the tool. This makes accidental changes easier to catch.

Complete workflow examples

Inspect a project without decrypting records

list_records returns safe metadata. It does not decrypt secret fields.
MCP tool used: list_records

Read one secret locally

The MCP server obtains encrypted data through the SDK and decrypts it on the machine where MCP is running. The agent can still receive the plaintext result, so only use this tool in a trusted agent session.
MCP tool used: get_secret

Create a generated password record

create_record encrypts the generated fields locally before sending the record to .
MCP tool used: create_record

Set up a gateway from an environment variable

The MCP process reads AIRCTRL_MCP_KEY_OPENAI_PRODUCTION; the model does not need the provider key in the prompt. The returned gateway token is shown only once.
MCP tool used: setup_gateway

Review usage before changing limits

This separates a read-only review from the later write.
MCP tools used: read_usage_spend, read_usage_metrics, set_gateway_settings

Revoke a gateway token

Revocation takes effect immediately. Listing a token never returns its secret value.
MCP tools used: list_gateway_tokens, revoke_gateway_token

Tool results

API-backed tools return structured JSON from @airctrl/sdk. Read tools return the requested resource, list tools return arrays or paginated data, and write tools return the new or updated resource. One-time credentials are the exception: their plaintext is present only in the successful creation result. Local helpers behave differently:

Tool failures

An MCP failure includes a safe code and explanation. The tool does not return a successful result when the API denied the operation. Never ask an agent to work around an authorization failure by trying unrelated accounts, projects or IDs.

Short agent requests