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

Groups and access material

These tools are human-only. Team+ and RBAC apply; Service Accounts cannot manage or join human groups. Read Groups and effective access before changing membership. Membership, deletion and grant results are server snapshots, including changed, wrapper-deletion counts and per-resource changes. Check pending material and remaining paths; success is not proof that every recipient can decrypt. Reconciliation returns attempts in attemptedProjectIds, never a permission grant. Optional project IDs limit project repair, not pending direct group-record shares in the account. Missing holder material can remain pending. Never put a passphrase in a prompt; use the existing local MCP vault configuration.

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

Ask an agent for a bounded page and keep the returned cursor opaque:
MCP tool used: list_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 is inclusive and until is exclusive.
  • read_record.scope accepts sections only: fields, meta, owner, access, or full. It does not select individual field names.
  • Omit environment to select General, or use development, staging, or production to select exactly that record value. The PAT or Service Account token must permit the selected scope; an absent value never falls back to General or another Environment.
  • get_secret, read_record with fields, and get_all return plaintext to the local MCP client. The model or agent can receive that plaintext; use these tools only when that exposure is approved.
  • Log pagination starts without a cursor. Continue with pagination.next_cursor, the same scope and the exact same filters. Cursors cannot be combined with legacy offset. 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

Read one Environment value locally

For a By Environment record, request one value explicitly:
MCP tool used: get_secret with environment: 'staging'

Create a generated password record

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

Create a generated Environment record

The same tool can create a single Staging value without inventing another record or exposing generated material in the prompt:
MCP tool used: create_record with environment: 'staging' and generate: true

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

OAuth partner Apps

The MCP server has no OAuth App credential mode, authorization-code flow, or installation/protection lifecycle tools. Do not place OAuth client secrets, authorization codes, access tokens, or refresh tokens in MCP configuration or an agent conversation. Neither is a confidential partner token store, and a hosted MCP would violate the partner-backend boundary. Implement OAuth partner flows through direct HTTP/OpenAPI or OAuthPartnerClient in the partner’s confidential backend. See OAuth partner integrations, OAuth protocol, and OAuth protection API. MCP may manage ordinary gateways with a separately authorized human PAT; those tools do not act as an OAuth installation.

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