Moveo One MCP
Moveo One ships an MCP server. Point Claude, Claude Code, Cursor or any MCP client at your workspace and it can work inside the product on your behalf — no dashboard round-trip.
The obvious use is the one that saves the most time: an assistant that is already sitting in your codebase can install the SDK, deploy, and then confirm events actually arrived — without you switching context to check.
Two ways to run itDirect link to Two ways to run it
| Local | Hosted | |
|---|---|---|
| Transport | stdio, runs on your machine | Streamable HTTP at https://hound.moveo.one |
| Auth | Browser device flow; credentials in your OS keychain | OAuth 2.1 + PKCE |
| Filesystem tools | Yes — can read your repo and edit files | No |
| Best for | Working in an editor on a real codebase | Clients that support remote MCP servers |
The hosted server offers the same tools minus the ones that read and write your local filesystem. Everything that talks to your Moveo One data is available in both.
What it can doDirect link to What it can do
- Integrate — scan your project, recommend an approach, and insert the SDK for script-tag and npm projects. For tools that live outside your codebase — Google Tag Manager, Segment, PostHog — it returns the exact configuration to paste.
- Verify — confirm events are reaching Moveo One, and wait for the first event after a deploy.
- Analyze — read your overview and dashboards, refresh a plot, and answer questions about your data in plain language.
- Simulate — create cohorts and audiences, calibrate them against your own data, launch Quantum runs on either track, and follow them to completion.
- Models — check data readiness, build and validate a training config, start training, poll it, and read the resulting metrics.
- Experiment — create and follow prediction-driven A/B experiments.
- Connect a warehouse — inspect, test and configure import and export, in both directions.
- Know where you stand — your plan, days remaining and quota used.
Full list on What it can do.
Getting startedDirect link to Getting started
uvx moveo-one-mcp login
Then register the server with your client — see Install.
You need a Moveo One account; sign up at app.moveo.one.
What it will not doDirect link to What it will not do
Worth knowing up front, so you don't wait for a tool that isn't coming:
- It does not touch the database. The MCP is a thin client over the same API the web app uses. It can do what your account can do, and nothing more.
- Payment stays in the browser. No tool changes a plan or a subscription; plan status is read-only.
- Destructive operations stay in the browser. Deleting a model, a training request, an experiment, an integration config or an API token is a click behind a confirmation dialog, not a chat turn.
- Credentials are never echoed. Warehouse tools return configuration shapes and status, never a password or key. A newly minted API token is the one exception — it has to be shown once, and the tool says so plainly.