MCP.so
Sign In

Crevio MCP ServerVerifiedFeatured

@Crevio

Basic information

Transport

Streamable HTTP

Authentication

OAuth

Category

Finance & Commerce

Author

Crevio

Submitted by

Axel Grubba

About Crevio MCP Server

Delegate work to an AI agent that runs your small business (products, orders, customers, email, sites), or run scripts against the Crevio API and 3,000+ connected apps.

Connection details

https://mcp.crevio.co/mcp

Setup

claude mcp add crevio --transport http https://mcp.crevio.co/mcp

Crevio MCP Server tools

20

Identify the account, user, and credential behind this connection, with plan, credit balance, rate limits, and the tools available. Only needed to troubleshoot the connection or check credits and limits — other tools already act on this account.

List what a script can call: the Crevio API (crevioApi), Crevio's own tools (platform), and every integration you can use, each as a namespace under `tools`, plus the account's other connected apps and their status. Then list a namespace's functions with list_integration_tools.

List one namespace's functions — the name a script calls, its parameters, whether it only reads, whether it needs approval, and a snippet run_script accepts. crevioApi has hundreds of operations: narrow it with `search`.

Run JavaScript on the account's computer with bun — no agent turn — and wait for its result. `tools.<namespace>.<function>(args)` calls anything list_integration_tools shows (every call returns its result and throws on failure; top-level await works), and the script's last expression is its result. Chain calls and transform data in one run, e.g. `const { data } = await tools.crevioApi.listOrders({ status: "succeeded" }); data.length`. Runs as you, and only for account admins. If the wait ends first the reply has wait_timed_out: true and the run id: continue with wait_for_script_run — calling run_script again runs it twice unless you reuse the idempotency_key. Run ids do not expire, and only the user who started a run can read it. At most 4 runs in flight per user. `args` reach the script as the global `args` (and process.argv). Files the script writes into the directory named by the global `outputDir` (20 at most, 50 MB each) come back as `artifacts`; get a download link with get_file_download_url.

Wait for a script run to finish and return its result. If it is still running when the wait ends, the reply has wait_timed_out: true — call again.

Read a script run's status, and its result once it has finished.

Cancel a script run that has not started yet. A running script runs to its end or its timeout.

Delegate a job to the Crevio agent and wait for the result. The agent works your account through the Crevio API and every connected integration (products, customers, orders, email, socials, sites, research) and replies in `result`. Each job is a full agent run that takes from half a minute to several minutes, so use it for work that needs judgement or writing. If the run is still going when the wait ends, the reply has wait_timed_out: true — then call wait_for_run with its id and never call ask_crevio again, which would do the job twice. Run ids do not expire, and only the user who started a run can read it.

Open a chat with the Crevio agent and queue a run, without waiting. Returns the run immediately — its `chat_id` is the conversation to continue with send_message. Follow the run with wait_for_run or get_run.

List the account's chats, newest first.

Get a chat's title, kind, and latest run.

Continue a chat with follow-up instructions or answers — the agent keeps its context. Resumes a run waiting in needs_input, or queues a new run when the last one finished. Returns run_busy while a run is still in progress. Optionally waits for the reply.

Read a chat's messages, oldest first. Returns the most recent `limit` messages; page back through older ones with starting_after.

Wait for a run to settle (completed, failed, cancelled, or needs_input) and return it with the agent's final reply. If it is still running when the wait ends, the reply has wait_timed_out: true — call wait_for_run again.

Fetch a run's current status, summary, pending approvals, and (once settled) the agent's final reply.

List the account's task runs, newest first — delegated jobs and scheduled tasks alike. Filter by status, task, or chat.

Approve or deny the integration actions a run is paused on (status needs_input with pending_approval_ids). Submit a decision for every pending id at once; the run resumes in the background.

Stop a run that is pending, running, or waiting for input, and its media generations still in flight. A run mid-step finishes that step first: it returns with cancel_requested_at set and settles as cancelled moments later (wait_for_run to confirm). Repeating it is harmless.

Exchange an artifact id (art_...) from a run's or script run's `artifacts` for a download link. The link needs no credentials and expires after 15 minutes; ask again for a fresh one.

List the account's audit events, newest first: access and configuration changes, approvals, API key use, and (at the full capture level) the agent's tool calls.

Overview

What is Crevio?

Crevio is an AI agent that runs small businesses: products, orders, customers, email, websites and marketing. Its official MCP server lets Claude, ChatGPT, Cursor or any MCP client delegate work to that agent, or script the Crevio API directly.

What you can do

  • Delegate jobs in plain English with ask_crevio, or start one in the background with start_chat and follow it with wait_for_run.
  • Approve or deny actions on connected apps that a run pauses on, with resolve_approvals.
  • Run scripts with run_script: JavaScript against the whole Crevio API and the 3,000+ apps connected to your account, without an agent turn.
  • Read history: chats, messages, runs and the account's audit log.

20 tools, each with read-only and destructive hints.

Connect

  • URL: https://mcp.crevio.co/mcp (Streamable HTTP)
  • Auth: OAuth 2.1 with dynamic client registration, on any plan including Free. API tokens (Authorization: Bearer or X-Api-Key) need the Business plan.
claude mcp add --transport http crevio https://mcp.crevio.co/mcp

Then call whoami to check the connection. Docs: https://crevio.co/docs/developer/mcp

Frequently asked questions

1

What is the Crevio remote MCP server?

The Crevio remote MCP server is a hosted Model Context Protocol endpoint at https://mcp.crevio.co/mcp, so AI assistants can connect to it without installing or running anything locally.

2

How do I connect to the Crevio MCP server?

Add the endpoint https://mcp.crevio.co/mcp to any MCP-compatible client such as Claude Code, Cursor, or VS Code. The setup snippets on this page configure each client in one step.

3

Does the Crevio MCP server require authentication?

Yes. Crevio uses OAuth: the first time you connect, your MCP client opens a browser window to sign in and authorize access, then reuses the credentials for future sessions.

4

Which transport does the Crevio MCP server use?

Crevio exposes a Streamable HTTP endpoint, the transport used by remote MCP servers and supported by all major MCP clients.

Comments