Skip to main content
Connect your coding agent to Oqoqo with the plugin (recommended). Then the agent can operate your workspace: create catalog items, launch experiments, watch runs, and read results. The dashboard is for Matrix, Frictions, Traces, and for entering secrets. Day-to-day work can stay in the agent session.
This page is about the Oqoqo MCP server that operates your workspace. It is separate from MCP servers you attach to treatments when you test your own product. See Treatments and Assets.

Why MCP exists

Your coding agent should be able to:
  • create tasks and treatments with you
  • launch and watch experiments
  • read Matrix, traces, and frictions
  • open the exact dashboard link when a secret is required
MCP gives that capability inside ChatGPT (Codex), Claude Code, Cursor, GitHub Copilot, and other MCP hosts. The CLI exposes the same capabilities from the terminal. Ask Oqo covers everyday work inside the dashboard. You can also install from the dashboard under Automate → Oqoqo MCP.

Install

Prefer the plugin. It registers the Oqoqo workspace server and the product docs server for you. Do not add both the plugin and a direct MCP connection in the same host. That would load the same tools twice.

ChatGPT

Claude

Then start Claude Code and run /mcp.

Cursor

In Cursor Agent, enter /plugin. Open Marketplace, select oqoqo, and install it for the user.

GitHub Copilot

Then start copilot and run /mcp auth oqoqo.
Use this path only when your host does not support plugins. Authentication uses OAuth. On first use, the host opens Oqoqo’s authorization page.Workspace endpoint:
Product docs endpoint (add once with direct MCP):

ChatGPT

Claude

Then start Claude Code and run /mcp.

Cursor

Add to ~/.cursor/mcp.json (user) or .cursor/mcp.json (project):
Then authenticate and enable:

GitHub Copilot

Then start copilot and run /mcp auth oqoqo.

Capabilities

MCP and the CLI share the same product capabilities. Oqoqo MCP page with the main agent capabilities. Destructive tools use the host’s native approval flow plus a short-lived server confirmation.

Keep secrets in the dashboard

OAuth grants, API keys, and secret headers stay in the dashboard. Ordinary project, catalog, experiment, and analysis work stays available from the agent session. When a tool needs a secure value, it returns the exact Web setup link for that step. Billing checkout also stays on the Web.

First prompt

Then ask the agent to draft a task, launch a small experiment, and explain the Matrix and frictions when it finishes.

CLI

The same capabilities from your terminal and scripts.

Ask Oqo

The in-app assistant for everyday project work.

Projects

Create and switch projects.

Dashboard map

Where each surface lives in the app.