Org Chart Studio provides an MCP endpoint for agents that can review roster data, render a preview, work with saved charts after authorization, and export supported files. Start with the live discovery documents instead of copying an old tool schema into your integration.
Start with the maintained agent and API documentation
Open the agent hub for the human overview. Give the agent /llms.txt, connect it to the Streamable HTTP endpoint at /mcp, and use tools/list for the current tool names, input schemas, security requirements, and limits.
Builders can read the OpenAPI description, the OAuth protected-resource metadata, and the API catalog. Treat these live documents and tools/list as the contract.
Use public tools without connecting an account
The public tools currently let an agent:
- review CSV or Excel roster data without saving it;
- list and read built-in templates;
- list the available chart styles and their schemas;
- render a watermarked PNG from CSV, Excel, or structured people data.
Use review_org_chart_csv or review_org_chart_xlsx before rendering when the roster may contain missing managers, skipped rows, or an Excel workbook with several sheets. Use render_org_chart_png for the public image. That public render always includes the Org Chart Studio watermark.
Do not describe a public render as a saved chart. The agent must connect to an account before it can read or change saved charts.
Connect saved charts with OAuth
Saved-chart tools use OAuth 2.1. Let the MCP client follow the authorization challenge returned by the server. Do not ask a person to paste a password or bearer token into a prompt.
Current scopes:
charts:readcovers listing and reading saved charts, checking subscription status, previewing a chart style, and exporting a saved chart.charts:writecovers creating, renaming, duplicating, deleting, and editing saved charts. It is also required when an export request would create a payment challenge or apply an eligible size upgrade.
A token with charts:read can use an already active pass that covers the export. It cannot create new payment or entitlement state. Read the security metadata returned by tools/list for the tool you plan to call.
Pay for an agent export
Call the saved-chart export tool with the intended format and current arguments from tools/list. CSV export is a data export. PNG, PDF, and PowerPoint are visual exports with their own entitlement rules.
If the account already has a pass that covers the requested export, the tool proceeds with charts:read. If it does not, the export can return a payment_required result containing the current x402 challenge. Creating that challenge requires charts:write.
Follow the challenge returned for that specific request:
- Read its resource description, exact amount, asset, network, and deposit address.
- Pay that exact challenge once. Do not send a second payment when a retry returns the same pending purchase.
- Settlement is asynchronous. Poll
get_subscription_statusrather than attaching a payment proof to the export call. - Retry the export after the pass becomes active.
The server reuses one durable unpaid challenge for the same logical purchase. A temporary mint_pending response means retry the request after the supplied delay. If a response says the attempt needs review or payment already finished, do not start another purchase. Check subscription status and follow the returned recovery direction.
Do not pay from a copied example, an earlier quote, or a response that says challenge issuance is unavailable. Current size, duration, eligibility, and price come from the returned quote and challenge.
Keep browser checkout separate
The Studio Export dialog and the pricing page use the browser purchase flow. That flow signs the person in and shows the current pass choices before checkout. An agent's x402 challenge is a separate programmatic payment path.
A browser receipt, checkout result, or active pass can affect the same account entitlement, but it is not an x402 payment proof. After any browser purchase, have the agent refresh get_subscription_status before retrying the export.
Protect roster and account data
Use only the roster fields needed for the requested chart. Public review and rendering process the data sent in that tool call; they do not save a chart to an account. Saved-chart tools operate on the connected account and enforce their declared OAuth scope.
Before allowing an agent to delete a chart, replace people, or change reporting lines, review the proposed operation and the connected account. The privacy policy is the current authority for data handling, service providers, and retention. For a product or payment problem, use the safe details in account, data, and support help, without sending passwords, full payment-card numbers, or an employee roster.