Is the integration read-only?

Yes. All tools only read from your Stoplight workspace — projects, nodes, schemas, and activity logs. No modifications or deletions are possible through this integration.

What is the workspace slug?

It's the subdomain of your Stoplight URL. For example, if your workspace is at `https://acme.stoplight.io`, the slug is `acme`. You can find it in the address bar when logged in.

What data can the agent access?

Projects, workspace members, activity logs, and all project nodes (endpoints, models, articles). Each node's full content — including OpenAPI schemas — can be retrieved via `get_node_details`.

Stoplight MCP Server for Cursor 7 tools — connect in under 2 minutes

Name: Stoplight
Availability: InStock
Author: Vinkius

docs.cursor.com/context/model-context-protocol

Built by Vinkius GDPR 7 Tools IDE

Cursor is an AI-first code editor built on VS Code that integrates LLM-powered coding assistance directly into the development workflow. Its Agent mode enables autonomous multi-step coding tasks, and MCP support lets agents access external data sources and APIs during code generation.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Stoplight and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "stoplight": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Stoplight MCP Server

Integrate the industry-leading API design and documentation capabilities of Stoplight into your conversational AI workflows. Empower your engineering teams to explore workspaces, evaluate OpenAPI schemas, and audit API projects natively from their conversational assistant. Securely map your AI to your Stoplight workspace, enabling the orchestration of complex documentation tasks, project navigation, and architectural reviews naturally without switching contexts or opening complex dashboards.

Cursor's Agent mode turns Stoplight into an in-editor superpower. Ask Cursor to generate code using live data from Stoplight and it fetches, processes, and writes. all in a single agentic loop. 7 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.

What you can do

Workspace Exploration — Rapidly inspect top-level organizational containers invoking list_workspaces, and track operational changes programmatically leveraging list_workspace_activity.
Project Management — Audit your API documentation repositories cataloging initiatives securely using list_projects, and retrieve full visibility metadata invoking get_project_details.
Schema & Documentation Discovery — Dive deeply into specific documentation structures retrieving files, endpoints, and models leveraging list_project_nodes, and parse their raw text safely utilizing get_node_details.
Team & Governance — Map project ownership accurately and enforce governance metrics iteratively assigning roles retrieving authorized contributors naturally via list_workspace_members.

The Stoplight MCP Server exposes 7 tools through the Vinkius. Connect it to Cursor in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Stoplight to Cursor via MCP

Follow these steps to integrate the Stoplight MCP Server with Cursor.

Open MCP Settings

Press Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"

Add the server config

Paste the JSON configuration above into the mcp.json file that opens

Save the file

Cursor will automatically detect the new MCP server

Start using Stoplight

Open Agent mode in chat and ask: "Using Stoplight, help me...". 7 tools available

Why Use Cursor with the Stoplight MCP Server

Cursor AI Code Editor provides unique advantages when paired with Stoplight through the Model Context Protocol.

Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context

Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards

MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment

VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools

Stoplight + Cursor Use Cases

Practical scenarios where Cursor combined with the Stoplight MCP Server delivers measurable value.

Code generation with live data: ask Cursor to generate a security report module using live DNS and subdomain data fetched through MCP

Automated documentation: have Cursor query your API's tool schemas and generate TypeScript interfaces or OpenAPI specs automatically

Infrastructure-as-code: Cursor can fetch domain configurations and generate corresponding Terraform or CloudFormation templates

Test scaffolding: ask Cursor to pull real API responses via MCP and generate unit test fixtures from actual data

Stoplight MCP Tools for Cursor (7)

These 7 tools become available when you connect Stoplight to Cursor via MCP:

get_node_details

Retrieves details for a specific documentation node

get_project_details

Retrieves details for a specific Stoplight project

list_project_nodes

Lists all documentation nodes (files, endpoints, models) within a project

list_projects

Lists all projects in a specific Stoplight workspace

list_workspace_activity

Lists recent activity logs for a Stoplight workspace

list_workspace_members

Lists all members of a Stoplight workspace

list_workspaces

Lists all accessible Stoplight workspaces

Example Prompts for Stoplight in Cursor

Ready-to-use prompts you can give your Cursor agent to start working with Stoplight immediately.

"List my Stoplight projects and show recent workspace activity."

"Retrieve the detailed schema documentation for the processing node in our core billing API project."

"List all active members in the current workspace."

Troubleshooting Stoplight MCP Server with Cursor

Common issues when connecting Stoplight to Cursor through the Vinkius, and how to resolve them.

Tools not appearing in Cursor

Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.

Server shows as disconnected

Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.

Stoplight + Cursor FAQ

Common questions about integrating Stoplight MCP Server with Cursor.

What is Agent mode and why does it matter for MCP?

Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.

Where does Cursor store MCP configuration?

Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.

Can Cursor use MCP tools in inline edits?

No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.

How do I verify MCP tools are loaded?

Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.