Enterprise DNA
M MCP Servers Developer low

stape-io/stape-mcp-server

by Various

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

S

MCP

stape-io/stape-mcp-server

Added 1 June 2026

#gtm #gtm-server-side #mcp #mcp-server #stape

Overview

A Model Context Protocol (MCP) server that lets AI assistants like Claude and AI-powered IDEs like Cursor interact with the Stape API. It acts as a bridge, allowing developers to manage Stape configurations and data through natural language or code prompts.

Best for

Best for
Developers already using Stape who want to control it through AI assistants

Use cases

  • Query Stape API resources via an AI chat interface
  • Manage Stape server-side tag configurations using natural language
  • Automate Stape workflows directly from an IDE like Cursor

Notes

A Model Context Protocol (MCP) server that lets AI assistants like Claude and AI-powered IDEs like Cursor interact with the Stape API. It acts as a bridge, allowing developers to manage Stape configurations and data through natural language or code prompts.

13 stars on GitHub. Last updated 2026-03-28. Licensed Apache-2.0.

Use cases

  • Query Stape API resources via an AI chat interface
  • Manage Stape server-side tag configurations using natural language
  • Automate Stape workflows directly from an IDE like Cursor

Pros

  • Works with multiple AI assistants and IDEs out of the box
  • Simple setup via npx or Docker for quick integration
  • Open source with TypeScript type safety

Cons

  • Very low community traction (13 stars) implies limited testing and support
  • Only works with the Stape API, requiring existing Stape knowledge and credentials
  • Functionality is entirely dependent on the capabilities of the Stape API

Indexed from awesome-mcp-servers-punkpeye and enriched against its public facts.

Pros

  • Works with multiple AI assistants and IDEs out of the box
  • Simple setup via npx or Docker for quick integration
  • Open source with TypeScript type safety

Cons

  • Very low community traction (13 stars) implies limited testing and support
  • Only works with the Stape API, requiring existing Stape knowledge and credentials
  • Functionality is entirely dependent on the capabilities of the Stape API