MCP guide

The platform exposes Model Context Protocol servers for agents, in two modes backed by the same validated commands:

• stdio — a local server process launched by your agent host; the credential is injected through the environment by your secret manager.
• remote Streamable HTTP — connect to https://api.xentropy.ai/mcp. The endpoint publishes OAuth protected-resource metadata and answers unauthorized requests with it; browser login/consent uses authorization code with S256 PKCE. Callback URLs must be registered ahead of time — dynamic client registration is intentionally unavailable. A manually provisioned scoped credential can be supplied instead as an Authorization: Bearer header.

Tool surfaceCopy Anchor Link

Charts — list, get, create, update, refresh, and export charts, plus data discovery and preview tools.

Artifacts (motion) — create from templates, read source, validate planned changes, apply operation batches, render, poll jobs, and manage outputs and shares.

Resources — including the motion component catalogue (artifact://catalog/motion/components).

A complete workflowCopy Anchor Link

1. Discover tools and read the motion component catalogue.
2. Create an artifact from a template with a fresh, stable idempotency key — the response includes the artifact ID and its first revision.
3. Read the actual source; use the real node and dataset IDs it returns.
4. Validate the planned change, then apply it as one atomic operation batch with the expected revision ID and a new idempotency key.
5. Render a frame (PNG) from that revision; poll the job until completed and inspect the output. Check first, middle, and final frames for animations.
6. Iterate against the latest revision, then render the MP4 from that exact revision and wait for completed before delivering the download.
7. Share only when instructed — an expiring, revocable snapshot with exactly the files you select, source and remix left off unless requested.

Error and output disciplineCopy Anchor Link

• Errors arrive structured: code, message, and validation issues where relevant.
• Replies use structured output schemas; large binaries are delivered as authenticated links, never embedded.
• A queued or failed job is not a completed export — poll until the job is completed, then read the output manifest.
• Revocation is immediate: revoke a credential from the console and its next request fails authorization.