SI

stape-io/stape-mcp-server

Developer tools

Эта страница переведена автоматически. Технические детали смотрите в оригинале. Открыть оригинал

18 stars 9 forks Качество 79 Тренд 36Apache-2.0

Interact with the Stape API using AI assistants like Claude, or in AI-powered IDEs like Cursor.

Обзор

This project implements an for the platform. The server wraps the Stape REST API. Full endpoint reference: - Global: https://api.app.stape.io/api/doc - EU: https://api.app.eu.stape.io/api/doc The Stape MCP Server is a remote, HTTP-based MCP endpoint at https://mcp.stape.io/mcp. Clients that speak HTTP directly (Claude Code, VS Code, Copilot CLI, Cursor, Antigravity, Lovable, and Claude Desktop's custom connectors where request headers are available) connect to it as is; stdio-only clients reach it through mcp-remote, a small bridge to remote HTTP MCP servers. A legacy /sse endpoint also exists for backward compatibility with older SSE-based MCP clients. It isn't part of any config below — use /mcp for new integrations. Get a Stape API key from your Stape account and use it instead of ${your_stape_api_key} below (learn how). Restart the client after changing its config. Using the Stape EU environment?

README

Показан фрагмент оригинального README. Открыть оригинал.

Stape MCP Server

This project implements an MCP (Model Context Protocol) server for the Stape platform.

Table of Contents

API Documentation

The server wraps the Stape REST API. Full endpoint reference:

Prerequisites

  • Node.js (v20 or higher)

Installation

The Stape MCP Server is a remote, HTTP-based MCP endpoint at https://mcp.stape.io/mcp. Clients that speak HTTP directly (Claude Code, VS Code, Copilot CLI, Cursor, Antigravity, Lovable, and Claude Desktop’s custom connectors where request headers are available) connect to it as is; stdio-only clients reach it through mcp-remote, a small bridge to remote HTTP MCP servers.

A legacy /sse endpoint also exists for backward compatibility with older SSE-based MCP clients. It isn’t part of any config below — use /mcp for new integrations.

Get a Stape API key from your Stape account and use it instead of ${your_stape_api_key} below (learn how). Restart the client after changing its config.

Using the Stape EU environment? Each client below ends with the one change EU accounts need — see EU Endpoint Support for why.

Claude Desktop

Custom connector (HTTP direct). If your Add custom connector dialog has a Request headers section (in beta, not available to every organization yet):

  1. Go to Customize → Connectors → Add custom connector. On Team and Enterprise plans, an Owner adds it under Organization settings → Connectors instead, and every member then uses the key the Owner entered: everyone in the organization acts as that one Stape account, including its write and delete tools, so only do this when that’s intended.
  2. Set the URL to https://mcp.stape.io/mcp and Authentication to No sign-in.
  3. Under Request headers, add authorization with your Stape API key as the value, mark it Required, and select Add.

The connector also works on claude.ai. EU accounts use https://mcp.stape.io/mcp?region=eu as the URL.

mcp-remote. Without Request headers, add this to your claude_desktop_config.json (Settings → Developer → Edit Config):

{
  "mcpServers": {
    "stape-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.stape.io/mcp",
        "--header",
        "Authorization: ${your_stape_api_key}"
      ]
    }
Открыть полный README на GitHub

Установка

npx -y mcp-remote https://mcp.stape.io/mcp --header Authorization: ${your_stape_api_key}
Новичок в MCP? Начните с руководства на mcpskill.org →

Конфигурация

{ "mcpServers": { "stape-mcp-server": { "command": "npx", "args": [ "-y", "mcp-remote", "https://mcp.stape.io/mcp", "--header", "Authorization: ${your_stape_api_key}" ] } } }