https://mcp.trevosdk.com/mcp. It lets an AI app do what the CLI does: list what
Trevo proposed, approve or dismiss, ask for a fresh batch, follow generation, and start, end and
decide experiments. Nothing runs on your machine.
Connect
Add the server to your app. On first use it opens a Trevo sign-in, then a page where you choose:- The workspace it opens. One per connection; connect again for another.
- What it may change. Every write is off until you turn it on, and you can only turn on what your role allows. Reading the workspace is always included.
Claude Code
/mcp in Claude Code and choose Authenticate.
Cursor
Add it to~/.cursor/mcp.json, or .cursor/mcp.json in a project:
claude.ai
Settings → Connectors → Add custom connector, with the URL above.ChatGPT
Add a custom connector with the URL above and OAuth as the authentication. Custom connectors need developer mode, which depends on your ChatGPT plan.With an API key
For a script, a CI job or a headless agent, send a workspace API key instead of signing in. Make one under Settings → API access:Tools
Every write is marked as one that changes things, and the server asks the app to confirm with you
first.
generate and proposals_approve answer before the work is done: follow them with
runs_show or experiments_status, which wait up to 45 seconds per call.
What it can do
The app acts as you, with the writes you allowed and your role still holds. A write it may not make gets Trevo’s refusal, with the reason. The workspace’s audit log records when an app is connected or disconnected, and each change under your name, marked with the app that made it, for example “via ChatGPT”. What the app reads from Trevo goes to it and to its model provider, and is handled under that app’s terms. Connect only apps your company allows for this data.Disconnect
- Account → Connected apps lists the apps you connected, in every workspace.
- Settings → API access → Connected apps lists the apps connected to that workspace. Anyone who can manage API keys sees and disconnects everyone’s.