MCP client setup

Use CloudEval’s MCP server when an agent should call CloudEval as a tool server instead of parsing CLI text output.

CloudEval command line and agent panel showing actions for ChatGPT, Claude, Codex, Cursor, and VS Code

Before you configure a client

Check the local MCP surface first:

cloudeval mcp status --format json
cloudeval doctor --mcp --format json

Authenticate with one of these options:

stored cloudeval login credentials
stored cloudeval login --headless credentials for remote or SSH sessions
--machine when your environment supports machine access

mcp serve uses stdin for MCP protocol messages, so run login before starting the MCP server.

Choose a client

CloudEval MCP setup examples for Codex, Cursor, Claude Code, and VS Code using cloudeval mcp serve

Codex
Cursor
Claude Code
VS Code

Generate the Codex setup guidance:

cloudeval mcp setup codex --dry-run

A typical local registration uses the CloudEval stdio server:

codex mcp add cloudeval -- cloudeval mcp serve

Use a focused toolset when Codex should only inspect part of the product:

codex mcp add cloudeval-reports -- cloudeval mcp serve --toolset reports

Generate Cursor setup guidance:

cloudeval mcp setup cursor --dry-run

Use the generated mcpServers entry in Cursor’s MCP configuration surface. Keep secrets in Cursor environment configuration or stored CloudEval login state, not inline command arguments.

If your Claude Code environment accepts an mcpServers JSON entry, start with the generic output:

cloudeval mcp setup generic --dry-run --format json

If your local CloudEval CLI supports a Claude-specific target for your installed Claude client, you can inspect that output too:

cloudeval mcp setup claude --dry-run

Use the generated stdio command and keep authentication in stored login state or environment variables.

Use the generic MCP JSON output for VS Code MCP extensions or built-in MCP configuration surfaces:

cloudeval mcp setup generic --dry-run --format json

The exact place to paste the config depends on the VS Code MCP extension or client you use. The important part is that the server command runs:

cloudeval mcp serve

Focus tool access

Use focused toolsets when the assistant should have a narrower CloudEval surface.

Toolset	Use it for
`all`	Full CloudEval MCP surface
`readonly`	Read-only project, report, billing, and capability discovery
`projects`	Project lookup, creation handoff, project deeplinks, and project context
`reports`	Report runs, report downloads, report deeplinks, and latest report context
`billing`	Billing and credit inspection

Example:

cloudeval mcp serve --toolset readonly

Verify the integration

After configuring the client:

Restart the MCP client if it requires a restart.
Ask the client to list available CloudEval tools.
Run a low-risk command such as capability discovery or project listing.
Confirm the result uses the expected CloudEval profile, base URL, and auth mode.

CloudEval agent result explaining selected Azure resources with diagram context and generated Mermaid output

Next step

Use Agent and automation rules for safety defaults, or CLI command reference for the MCP command surface.

Start here

Agents and MCP

Reference

Before you configure a client

Choose a client

Focus tool access

Verify the integration

Next step

Start here

Agents and MCP

Reference

Documentation Index

​Before you configure a client

​Choose a client

​Focus tool access

​Verify the integration

​Next step

Before you configure a client

Choose a client

Focus tool access

Verify the integration

Next step