MCP

Everyn MCP is one hosted, organization-scoped Model Context Protocol server. A connected host can upload or rediscover a Dataset, create or patch a reusable Job, start an explicit sample or full Run, wait without cancelling work, and export a complete-results CSV for local analysis.

The canonical endpoint is https://mcp.everyn.ai/mcp over Streamable HTTP. Protocol version 2026-07-28. There are fourteen tools. Do not invent a fifteenth tool or a host-specific shortcut.

MCP is not a second product. Datasets, Jobs, Runs, usage, and billing stay in Everyn. Receipts hand off to the matching page in the Everyn app.

Workflow

1. Call get_context for the current authenticated organization only.
2. Upload or rediscover a Dataset. If upload_csv returns a signed transfer descriptor, use that dedicated structured field to move bytes. Never echo the descriptor in text, later tool inputs, or logs.
3. Create or patch a Job with save_job. Prefer a sample before an unverified full Run.
4. Start work with exactly one start_run form: new, resume, or retry.
5. Wait with bounded get_run calls. Preview with get_run_results if needed.
6. When next_action is export_and_analyze, call export_run, download the CSV locally, and analyze that file.

Required behavior

• Never treat a local filesystem path as a hosted file. Use upload_csv or rediscover a Dataset the user uploaded in the app.
• Never silently widen a sample Run into a full-dataset Run.
• Do not invent cost, plan, usage, or funding values. If a section is unavailable, say so and use the provided handoff.
• After the user asked you to wait, keep calling bounded get_run waits without asking them to prompt again.
• Do not blindly retry quality or spec failures.
• Do not stop at terminal Run status. Export, download, and analyze the complete-results CSV.
• Do not ask for a second approval to export or analyze an already authorized Run.
• After discovery, use exact Everyn IDs. Do not guess resources by name.
• Do not fetch arbitrary URLs. Only Everyn-issued transfer targets exist, and the client moves bytes.
• Do not request organization IDs. No MCP tool accepts organization_id.
• Do not use API keys when OAuth failed.

Consequential actions

A direct user request for the exact sample, full Run, retry, resume, or cancellation is sufficient intent. If you propose one of those actions, show the receipt summary and ask first. Host-native confirmation may still appear.

Docs map