Steep MCP server
{
"mcpServers": {
"steep": {
"type": "http",
"url": "https://mcp.steep.app/mcp"
}
}
}{
"mcpServers": {
"steep": {
"type": "http",
"url": "https://mcp.steep.app/mcp"
}
}
}{
"mcpServers": {
"steep": {
"type": "http",
"url": "https://mcp.steep.app/mcp"
}
}
}{
"servers": {
"steep": {
"type": "http",
"url": "https://mcp.steep.app/mcp"
}
}
}{
"mcpServers": {
"steep": {
"type": "http",
"url": "https://mcp.steep.app/mcp"
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsonversion 1.0.0
What it does
Steep MCP exposes read-only access to metrics, targets, entities, and team data from a Steep workspace. It is for teams using Steep for metrics and planning who want their AI assistant to query workspace data through natural language.
- Query metric data over date ranges with optional slicing and breakdowns to analyze business performance.
- Check progress against targets and goals to track planning outcomes.
- Explore the workspace data model by listing entities, modules, metrics, and team members to understand what data is available.
Tools this server exposes
| Tool | Does |
|---|---|
| list_metrics | Lists all metrics available in the Steep workspace. |
| query_metric_data | Queries metric data over a specified date range with optional slicing and breakdowns. |
| list_targets | Lists all targets in the workspace. |
| query_target_progress | Queries progress against a specific target. |
| list_entities | Lists entities available in the workspace. |
| list_modules | Lists modules and the entities that appear in them. |
| list_workspace_members | Lists members of the Steep workspace. |
| list_teams | Lists teams in the Steep workspace. |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.