AI & Machine Learning
crevio.co
Manage and interact with Crevio AI agents by identifying user credentials, delegating jobs, and handling chat sessions.
ENDPOINT 1
https://mcp.crevio.co/mcp
MCP server metadata
- Name
- crevio-api
- Version
- 2.0.0
Known tools 14
whoamiIdentify the account, user, and credential behind this connection, with plan, credit balance, rate limits, and the tools available.
Inferred read-onlysend_messageContinue a chat with follow-up instructions or answers — the agent keeps its context.
Inferred read-onlywait_for_runWait for a run to settle (completed, failed, or needs_input) and return it with the agent's final reply.
Inferred read-onlyget_runFetch a run's current status, summary, pending approvals, and (once settled) the agent's final reply.
Inferred read-onlylist_runsList the account's task runs, newest first — delegated jobs and scheduled tasks alike.
Inferred read-onlyresolve_approvalsApprove or deny the integration actions a run is paused on (status needs_input with pending_approval_ids).
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.crevio-api]
url = "https://mcp.crevio.co/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"crevio-api": {
"type": "http",
"url": "https://mcp.crevio.co/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: crevio-api
Remote MCP URL: https://mcp.crevio.co/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"crevio-api": {
"url": "https://mcp.crevio.co/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"crevio-api": {
"type": "http",
"url": "https://mcp.crevio.co/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "crevio-api",
"transport": "streamable-http",
"url": "https://mcp.crevio.co/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.