MCP.Market

Steep MCP server

online · 100% uptime
by steep.app·app.steep/mcp·v1.0.0·9 stars

Query metrics, targets, entities, and team data in your Steep workspace via MCP.

A92/100grade A
What users say
No reviews yet
Be the first
Safety scan
A92/100

full report

Adoption
Growing

9 stars

Reviews

Write one

Nobody has reviewed Steep yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Steep tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Public scan report

scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 218ms (auth required)20/20
  • –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
  • Auth qualityOAuth resource metadata advertised on 40115/15
  • Maintenancelast push 37 days ago12/15
  • Maintainer identitynamespace and repository owner differ; GitHub account older than a year; website matches verified namespace8/10
Overall 92/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Steep compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
92/100
higher than 95% of 48,255 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
770 ms
faster than 17% of 30,031 servers
GitHub stars
9
more than 87% of 28,688 servers

Install Steep in Claude Code, Cursor or VS Code

claude mcp add --transport http mcp https://mcp.steep.app/mcp
Add to Cursor

What the publisher says

From the Steep repository's README, as published. We do not edit it. Read it on GitHub

<!-- mcp-name: app.steep/mcp -->

Steep MCP

This repository contains the configuration needed to integrate Steep with Claude Code, Cursor, and other MCP-compatible clients. The plugin lets your AI agents interact directly with your Steep workspace, querying metrics, targets, entities, and team data through natural language.

Features

The Steep MCP server provides the following capabilities:

date range, with optional slicing and breakdowns

  • Metrics: list metrics in the workspace and query metric data over any
  • Targets: list targets and query target progress
  • Entities & modules: list entities and the modules they appear in
  • Workspace: list workspace members and teams

All tools are read-only.

Prerequisites

Before setting up the Steep MCP server, ensure you have:

  • Claude Code CLI, Cursor IDE, or another MCP-compatible client installed
  • A Steep account with access to the workspace you want to query

Installation

Claude Code & Cowork

Install from the community plugin marketplace:

/plugin marketplace add anthropics/claude-plugins-community
/plugin install steep@claude-community

Alternatively, install directly from this repo:

git clone https://github.com/SteepHq/steep-mcp.git
claude --plugin-dir ./steep-mcp

Either path loads .claude-plugin/plugin.json and the sibling .mcp.json, configures the Steep MCP server, and prompts you to authenticate via OAuth. No client ID is needed — Claude Code discovers the auth server and registers itself dynamically.

Cursor

Install with one click from the Cursor plugin marketplace.

Alternatively, add Steep manually: Cursor → Settings → MCP and paste:

{
  "mcpServers": {
    "steep": {
      "url": "https://mcp.steep.app/mcp"
    }
  }
}

Save the configuration, then click the connect button to authenticate via OAuth.

Other MCP clients

Point your client at https://mcp.steep.app/mcp (Streamable HTTP transport). Clients supporting Dynamic Client Registration (RFC 7591) will register automatically.

Usage Examples

Once configured, you can interact with Steep through your AI assistant using natural language:

  • List metrics: "What metrics do we have in Steep?"
  • Query data: "Show MRR for the last 6 months, broken down by plan"
  • Track targets: "How are we tracking against our Q2 revenue target?"
  • Explore the data model: "Which entities slice the customer count metric?"
  • Find people: "Who's on the growth team in Steep?"

Updates

Marketplace installs (Claude Code, Cursor) auto-update when we publish a new version. Run /plugin update steep in Claude Code to pull the latest.

Cursor handles updates through its own marketplace UI. Users who installed manually via --plugin-dir or by editing mcp.json directly will keep using whatever revision they cloned — re-clone or re-paste to get changes.

Documentation & resources

  • Steep documentation
  • Steep privacy policy
  • Model Context Protocol specification

Notes & limitations

server. No local installation is required or supported.

  • Remote server only: this configuration connects to Steep's hosted MCP

already has access to. OAuth scopes are limited to the read scopes the server advertises at /.well-known/oauth-protected-resource.

  • Workspace scope: you can only access data your Steep user account

Questions or Issues?

For product questions and integration help, contact help@steep.app.

For security reports, see SECURITY.md.

License

Apache-2.0 — see LICENSE.

The Steep name and logo are trademarks of Steep. See NOTICE.

Nothing above is checked by us. What we check is on the safety report.

Steep: common questions

Is Steep MCP server safe?
Yes, by our scan: it is graded A (92/100). Read the Steep safety report
How do I install Steep?
It runs remotely at mcp.steep.app. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Steep need an API key?
No key to paste: it signs you in with OAuth when your client connects.
Is Steep maintained?
The last commit was 75 days ago (2026-08-21). The latest release is v1.0.0.
Is Steep up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Steep compare with other MCP servers?
safety score 92/100 (higher than 95% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 770 ms (faster than 17% of 30,031 servers). Full comparison.