Steel Remote MCP Server

๐Ÿ›ก๏ธ Officialโœ“ VerifiedStreamable HTTPOAuth 2.1๐Ÿ›ก๏ธ A+0 toolsยทOnline338msยท30d uptime: 100%ยทLast checked 12m ago

Steel's remote MCP provides browser sessions built for agents โ€” persistent contexts, anti-bot handling and structured page extraction for autonomous web tasks. Endpoint verified live on RemoteMCP.net (preflighted 401 OAuth challenge).

https://mcp.steel.dev/mcp
Provider
Steel.dev โ†—
Categories
๐Ÿ› ๏ธ Developer Tools & Git
ไธญๆ–‡็ฎ€ไป‹

Steel ๅฎ˜ๆ–นๆ‰˜็ฎก็š„่ฟœ็จ‹ MCP ๆœๅŠกๅ™จใ€‚Steel ่ฟœ็จ‹ MCP๏ผŒๆไพ›ไธ“ไธบไปฃ็†ๆ‰“้€ ็š„ๆต่งˆๅ™จไผš่ฏ๏ผšๆŒไน…ๅŒ–ไธŠไธ‹ๆ–‡ใ€ๅ็ˆฌๅค„็†ไธŽ็ป“ๆž„ๅŒ–้กต้ขๆๅ–ใ€‚

Maintainer of Steel? Claim or update this listing โ†’

Streamable HTTPhttps://mcp.steel.dev/mcp
Install in Cursor โ†’

Or add to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "steel": {
      "url": "https://mcp.steel.dev/mcp"
    }
  }
}

๐Ÿงฐ Steel MCP Tools & Schema (0)

ToolSafetyDescriptionParameters

๐Ÿ›ก๏ธ Security, Quality & Context Token Audit

๐Ÿ›ก๏ธ Grade A+Context tax: ~0 tokens injected into every system prompt by this serverโ€™s 0 tools

Every tool definition (name + description + input schema) is injected into your LLMโ€™s context on every request โ€” Estimate per-call LLM token cost โ†’

  • No prompt-injection or hidden-character anomalies detected in tool descriptions
  • Streamable HTTP primary endpoint (current 2025-03-26 transport)
  • OAuth 2.1 with PKCE S256 enforced
  • Official first-party endpoint operated by the vendor
  • Manually verified by RemoteMCP.net

๐Ÿ” OAuth 2.1 & Security

Auth type
OAuth 2.1
Dynamic Client Registration
โ€”
PKCE S256
โœ… Supported
Protected resource metadata
https://mcp.steel.dev/.well-known/oauth-protected-resource (expected location)
๐Ÿ” Audit OAuth 2.1 Config โ†’

๐Ÿงฉ Recommended Agent Skills

๐Ÿ“– Steel MCP Endpoint Overview & Security Guide

Steel โ€” Remote MCP Server

Steel's remote MCP provides browser sessions built for agents โ€” persistent contexts, anti-bot handling and structured page extraction for autonomous web tasks. The remote endpoint means there is nothing to install โ€” point your MCP client at the URL and complete the OAuth consent screen. Steel.dev operates and versions the server themselves, so tool coverage tracks their API surface as it ships.

Official Steel Endpoint & Transport Architecture

  • Endpoint URL: https://mcp.steel.dev/mcp
  • Transport: Streamable HTTP

Streamable HTTP is the current MCP transport (2025-03-26 spec): a single URL accepts JSON-RPC POSTs and may stream responses over SSE, so one endpoint serves both simple and streaming workloads. Steel does not publish a separate legacy SSE endpoint, so your client must speak Streamable HTTP.

Authentication, Scopes & Permission Boundaries

Steel uses OAuth 2.1 โ€” the first request returns a 401 Unauthorized challenge with a WWW-Authenticate header pointing at the authorization metadata. Compliant clients (Cursor, Claude, VS Code, ChatGPT) handle the whole flow โ€” PKCE โ€” and simply open a browser consent screen.

All 0 cataloged tools are read-only โ€” Steel cannot mutate your account data, which makes it safe to connect broadly.

Common Troubleshooting & Connection Tips

  • 401 Unauthorized on connect โ€” that's expected; the server is OAuth-protected. Let your client complete the browser consent flow, or inspect the endpoint in our OAuth debugger to see the exact WWW-Authenticate challenge.
  • "Session expired" / stale Mcp-Session-Id โ€” just re-send initialize; stateless clients can ignore session headers entirely.

๐Ÿš€ How to Connect

  1. Copy the Steel endpoint URL
    The remote endpoint is https://mcp.steel.dev/mcp.
  2. Add it to your MCP client
    Claude Code: claude mcp add --transport http steel https://mcp.steel.dev/mcp. Cursor: add "steel": { "url": "https://mcp.steel.dev/mcp" } under mcpServers in ~/.cursor/mcp.json. Other clients work similarly.
  3. Complete the OAuth consent
    On first connection your client opens a Steel.dev consent screen in the browser. Approve it to grant access; the token is stored by the client and refreshed automatically.
  4. Verify with the online inspector
    Paste https://mcp.steel.dev/mcp into remotemcp.net/inspector, run initialize and tools/list, and confirm Steel's 0 tools respond.

โ“ FAQ

What is the Steel remote MCP endpoint?

The primary endpoint is https://mcp.steel.dev/mcp. It is an official first-party server operated by Steel.dev, speaking the Streamable HTTP transport.

How do I authenticate with Steel?

Steel uses OAuth 2.1. When your client first connects it receives a 401 challenge, discovers the authorization server via RFC 9728 metadata, and opens a browser consent screen.

I'm getting a 401 Unauthorized from Steel โ€” what's wrong?

A 401 means your client hasn't completed (or has lost) the OAuth authorization. Remove and re-add the server in your client to restart the consent flow, and check that your browser session can reach the provider's login page. If the 401 arrives without a WWW-Authenticate header, run it through our OAuth debugger to see what's missing.

Which MCP clients work with Steel?

Any client that supports remote MCP servers: Cursor, Claude Code (`claude mcp add --transport http steel https://mcp.steel.dev/mcp`), VS Code Copilot, ChatGPT connectors, Windsurf, Kiro (`~/.kiro/settings/mcp.json`), and Claude Desktop via the `mcp-remote` bridge.

What tools does Steel expose?

0 tools are cataloged in this directory โ€” including . Use our online inspector to fetch the live tool list straight from the endpoint.

๐Ÿ”— Connect Guides

๐Ÿ“› Embed Status Badge in README

Steel status badge
[![Remote MCP Status](https://remotemcp.net/api/badge/status/steel.svg)](https://remotemcp.net/servers/steel)
Steel inspector badge
[![Test in Inspector](https://remotemcp.net/api/badge/inspect/steel.svg)](https://remotemcp.net/inspector?url=https%3A%2F%2Fmcp.steel.dev%2Fmcp)
Steel audit grade badge
[![MCP Audit Grade](https://remotemcp.net/api/badge/grade/steel.svg)](https://remotemcp.net/servers/steel)
Steel context tax badge
[![Context Tax](https://remotemcp.net/api/badge/tokens/steel.svg)](https://remotemcp.net/servers/steel)

Related Servers

GitHub's official remote MCP server hosted at api.githubcopilot.com. Gives AI agents first-party access to repositories, issues, pull requests and code search.

https://api.githubcopilot.com/mcp/
๐Ÿ›ก๏ธ Officialโœ“ VerifiedStreamable HTTPOAuth 2.1๐Ÿ›ก๏ธ A+~3096 tok92 toolsOnline310ms
Linear MCPLinear Orbit Inc.

Linear's official remote MCP server. Agents can search, create and update issues and query your team's workflow over Streamable HTTP or SSE.

https://mcp.linear.app/mcp
๐Ÿ›ก๏ธ Officialโœ“ VerifiedHTTP + SSEOAuth 2.1๐Ÿ›ก๏ธ A+~899 tok30 toolsOnline8ms
Claude SkillsClaudeSkills.club

Claude Skills's hosted remote MCP server. ClaudeSkills.club's public MCP lets agents search and pull from a catalog of 90,000+ Agent Skills (SKILL.md) โ€” workflow specs, safety scores and one-line install instructions. It is public and unauthenticated โ€” connect and call tools immediately.

https://claudeskills.club/mcp
๐Ÿ›ก๏ธ Officialโœ“ VerifiedStreamable HTTPPublic ยท No Auth๐Ÿ›ก๏ธ A+~344 tok3 toolsOnline125ms
GitLabGitLab

GitLab's hosted remote MCP server. GitLab's official MCP server gives agents first-party access to repositories, merge requests, issues, pipelines and code search across gitlab.com and self-managed instances. It is protected by OAuth 2.1; compliant clients complete a browser consent flow with PKCE.

https://gitlab.com/api/v4/mcp
๐Ÿ›ก๏ธ Officialโœ“ VerifiedStreamable HTTPOAuth 2.1๐Ÿ›ก๏ธ A+~659 tok22 toolsOnline176ms