MCP vs. REST API

The MCP server and the REST API overlap heavily, but neither is a strict superset of the other.

Surface	MCP	REST API
Agents, versions, skills, artifacts, model groups	Yes	Yes
Agent sessions (start, poll, follow up, cancel)	Yes	Yes
Connected MCP servers (list, inspect, call tools)	Yes	Yes
Flows, workbooks, and runs	Yes	Yes
Company Brain search	Yes	Yes
Audit logs	Yes (`get_audit_logs`, time range only)	Yes (`GET /get_audit_logs`, with event/user/IP/workspace filters)
Organization data exports	Yes (`export_data`, `get_export_status`)	Yes
Gumloop documentation search	Yes (`search_documentation`, `ask_gummie`)	No
Evaluations	No	Yes
Session approvals and queued messages	No	Yes
Workspace file upload and download	No	Yes
Workspace/role membership and role credit limits	No	Yes
Chat completions (OpenAI-compatible)	No	Yes

Use MCP when an AI client should drive Gumloop, including agent management, sessions, skills, flows, Brain, audit logs, exports, and docs search. Use the REST API for the full administrative surface, including evaluations, approvals, file operations, and organization membership and credit administration.

Core concepts

Guides

Tools

MCP vs. REST API