What the Steep MCP server does
The Steep MCP server gives MCP-compatible AI clients read access to information in a Steep workspace. It covers four main areas: metrics, targets, entities and modules, and workspace membership. Agents can use natural-language requests to find available metrics, retrieve metric data, inspect target progress, explore the data model, and identify workspace members or teams.
Metric queries can span any date range and may include slices or breakdowns. This supports questions such as comparing MRR by plan over several months. Target queries expose available targets and their progress, while entity and module queries help explain which parts of the Steep data model are available for analysis.
All capabilities are read-only. The server does not provide tools for creating, editing, or deleting Steep data.
How it works
The Steep MCP server is hosted by Steep and is accessed remotely; it does not run as a local installation. Clients connect to the Streamable HTTP endpoint at https://mcp.steep.app/mcp. After connection, the client exposes the server's read tools to the AI assistant, which can translate natural-language questions into requests against the connected workspace.
Authentication uses OAuth. The signed-in Steep account determines which workspace data is available, and access remains limited to the read scopes advertised by the server. Clients that support Dynamic Client Registration can register automatically when connecting to the endpoint.
Setup and configuration
You need a Steep account with access to the workspace you want to query and an MCP-compatible client. Claude Code users can install the Steep plugin from the community marketplace or load a cloned repository with claude --plugin-dir. The plugin configuration loads the MCP endpoint and prompts for OAuth authentication; no client ID is required.
In Cursor, install the integration through its plugin marketplace or add the following server configuration under Settings → MCP:
{
"mcpServers": {
"steep": {
"url": "https://mcp.steep.app/mcp"
}
}
}
Other compatible clients can use the same Streamable HTTP URL. Manual configurations and cloned plugin copies do not receive marketplace updates automatically.
Tools and capabilities
The Steep MCP server supports read operations for:
- Listing workspace metrics
- Querying metric data by date range
- Applying metric slices and breakdowns
- Listing targets and checking target progress
- Listing entities and the modules where they appear
- Listing workspace members and teams
These capabilities suit analytical and discovery tasks, including checking revenue progress, comparing metric segments, finding teams, and understanding which entities can be used to slice a metric.
Limitations and notes
The Steep MCP server is remote-only. No supported local installation is described, so clients must connect to Steep's hosted endpoint. Results are constrained by the permissions and workspace access of the authenticated Steep user. Because every tool is read-only, the integration cannot modify metrics, targets, entities, teams, or other workspace data.
Marketplace installations for Claude Code and Cursor can update through their respective marketplace workflows. If you cloned the repository or entered the MCP configuration manually, you must re-clone or update the configuration yourself to receive changes.