Steep

app.steepPublished by steep.appOfficial publisherv1.0.0Updated Oct 28, 2026

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

VerifiedStreamable HTTPWeb executableData & AnalyticsBusiness & Commerce

Overview

AI-generated overview

Steep's hosted MCP server lets an assistant query metrics, targets, entities and team data in a Steep workspace using natural language.

What you can do
  • List workspace metrics and query metric data over any date range, with optional slicing and breakdowns
  • List targets and query target progress
  • List entities and the modules they appear in
  • List workspace members and teams
When to use it
Useful when your team keeps its business metrics, targets and data model in Steep and you want an assistant to answer questions like MRR trends, target tracking or which entities slice a metric, without leaving the chat.
Requirements
A remote Streamable HTTP endpoint at mcp.steep.app; no local install. A Steep account with access to the workspace you want to query, and an MCP-compatible client. Authentication is OAuth, with dynamic client registration for clients that support it; no client ID is needed.
Before you install
Access is limited to data your Steep account can already see, and OAuth scopes are restricted to read scopes. All tools are read-only, so nothing is changed in the workspace. Queries send your metric and team questions to Steep's hosted server.

Installation

In SourceWeft

  1. Open Steep in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/app.steep%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

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

README

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:

  • Metrics: list metrics in the workspace and query metric data over any date range, with optional slicing and breakdowns
  • 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:

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

Alternatively, install directly from this repo:

bash
git clone https://github.com/SteepHq/steep-mcp.gitclaude --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:

json
{  "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

Notes & limitations

  • Remote server only: this configuration connects to Steep's hosted MCP server. No local installation is required or supported.
  • Workspace scope: you can only access data your Steep user account already has access to. OAuth scopes are limited to the read scopes the server advertises at /.well-known/oauth-protected-resource.

Questions or Issues?

For product questions and integration help, contact [email protected].

For security reports, see SECURITY.md.

License

Apache-2.0 — see LICENSE.

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

Source: README.md at commit 1a0ef1d

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts