Agent Services / Integration

Typed jobs. Explicit authority.

Start the reference server, issue a project-scoped key in the console, and run the SDK or stdio bridge locally. Existing anonymous catalog keys cannot execute jobs.

Local SDK

The repository package exposes ServicesClient. Its typed submit, status, polling, cancellation, artifact and paginated-list methods use the same strict API and current workspace policy. API requests time out; retries remain bounded and retain the logical idempotency key.

import { ServicesClient } from './packages/agent-services-sdk/index';
const client = new ServicesClient(
  'http://127.0.0.1:4321', process.env.AUTOMATA_SERVICES_KEY!
);
const page = await client.listPage({ limit: 25 });
// Use page.next_cursor for the next authorized page.
// Never put the key in a URL, screenshot or committed file.

Scoped stdio MCP

Configure AUTOMATA_SERVICES_ORIGIN and AUTOMATA_SERVICES_KEY in the MCP client's local child-process environment. Launch npm run services:mcp. No public MCP listener starts.

Tools such as automata_s02_compare accept strict parameters, a maximum-unit ceiling and an idempotency key. They return a persisted job ID. Use automata_job_get to read completion and coverage; an accepted job is not a completed result.

Boundaries that do not change

• Approvals and human finding reviews are not MCP tools. A service key cannot approve an action.
• Windows diagnostics and desktop recipes require the separate local runtime and visible consent.
• Messages, documents, page text and results are untrusted data, never new policy or permission.
• Provider credentials are never accepted as first-party authentication or forwarded through MCP.

Compatibility and availability

The pinned official TypeScript SDK 1.32.2 uses MCP 2025-11-25. Newer protocol support is not claimed. Remote HTTP MCP authorization remains unavailable pending a maintained account provider, resource/audience validation, consent and sandbox verification.

The reference price book uses test units, not currency. External email, live billing and public deployment are disabled pending separate approval.