OctOpus MCP Server — Data Science for Claude Code & Cursor
OctOpus ships a Model Context Protocol (MCP) server, so your coding agent can do real data science. Point Claude Code, Cursor, or any MCP-compatible client at OctOpus and it gains tools to profile a dataset, discover the right modelling direction, launch an autonomous research run, check status, and pull deployable artifacts — without leaving your editor.
What the MCP server exposes
The OctOpus MCP server gives your agent a focused set of tools: profile a dataset, choose a modelling direction, launch a research run, check its status, and fetch the results. Your agent calls them like any other tool — so 'profile this CSV and train the best churn model' becomes a single instruction that the agent fulfils end-to-end through OctOpus.
Why MCP beats copy-pasting code
AI coding assistants are great at writing code but they don't run a real research loop, manage holdout validation, or ship a model. By wiring OctOpus in over MCP, the agent delegates the hard ML — model selection, leakage checks, tuning, holdout scoring, deployment — to a system built for it, and gets back validated artifacts instead of an untested notebook.
Set up in minutes
Add the OctOpus MCP server to your client with your OctOpus API key; the docs walk through it. It works with Claude Code, Cursor, and other MCP clients. From there your agent can profile data, kick off runs, and fetch the trained model and prediction-API URL programmatically.
Key capabilities
- MCP tools to profile data, plan, run, check status and fetch results.
- Works with Claude Code, Cursor, and any MCP-compatible agent.
- Delegates the full ML research loop — your agent gets validated models, not raw code.
- Connect it with your OctOpus API key in a few minutes.
- Pull deployable artifacts (the trained model, prediction API URL) programmatically.
Frequently asked questions
What is the OctOpus MCP server?
It's a Model Context Protocol server that exposes OctOpus's data-science tools — profile, plan, run, status and results — to any MCP-compatible agent, so Claude Code or Cursor can run a full autonomous ML workflow without leaving the editor.
How do I connect it to Claude Code or Cursor?
Add the OctOpus MCP server to your client with your OctOpus API key, following the docs. Once connected, your agent sees the OctOpus tools and can call them like any other MCP tool.
What does my agent get back?
Validated artifacts, not just code: a model trained and scored on a holdout, the code that produced it, run status, and the URLs to download the model or call the hosted prediction API.
Is this different from the OctOpus web app?
It's the same engine, a different entry point. The web app is for people who want a browser UI; the MCP server is for agents and developers who want to drive OctOpus programmatically from their IDE or another AI agent.