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 Claude Desktop 7 tools — connect in under 2 minutes

Name: Stoplight
Availability: InStock
Author: Vinkius

modelcontextprotocol.io/quickstart/user

Built by Vinkius GDPR 7 Tools IDE

Claude Desktop is Anthropic's native application for interacting with Claude AI models on macOS and Windows. It was the first consumer application to ship with built-in MCP support, making it the reference implementation for the Model Context Protocol standard.

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": {
      // Your Vinkius token. get it at cloud.vinkius.com
      "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.

Claude Desktop is the definitive way to connect Stoplight to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 7 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.

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 Claude Desktop 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 Claude Desktop via MCP

Follow these steps to integrate the Stoplight MCP Server with Claude Desktop.

Open Claude Desktop Settings

Go to Settings → Developer → Edit Config to open claude_desktop_config.json

Add the MCP Server

Paste the configuration above into the mcpServers section

Restart Claude Desktop

Close and reopen Claude Desktop to load the new server

Start using Stoplight

Look for the 🔌 icon in the chat. your 7 tools are now available

Why Use Claude Desktop with the Stoplight MCP Server

Claude Desktop by Anthropic provides unique advantages when paired with Stoplight through the Model Context Protocol.

Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available

Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface

Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions

Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network

Stoplight + Claude Desktop Use Cases

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

Interactive data exploration: ask Claude to query DNS records, look up WHOIS data, and cross-reference results in a single conversation

Ad-hoc security audits: type a domain name and let Claude enumerate subdomains, check DNS history, and flag configuration anomalies. all through natural language

Executive briefings: generate comprehensive domain intelligence reports by asking Claude to compile findings into a formatted summary

Learning and training: new team members can explore API capabilities conversationally without needing to read documentation

Stoplight MCP Tools for Claude Desktop (7)

These 7 tools become available when you connect Stoplight to Claude Desktop 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 Claude Desktop

Ready-to-use prompts you can give your Claude Desktop 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 Claude Desktop

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

Server not appearing after restart

Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).

Authentication error

Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.

Tools not showing in chat

Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.

Stoplight + Claude Desktop FAQ

Common questions about integrating Stoplight MCP Server with Claude Desktop.

How does Claude Desktop discover MCP tools?

When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.

What happens if the MCP server is temporarily unavailable?

Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.

Can I connect multiple MCP servers simultaneously?

Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.

Is there a limit on the number of tools per server?

Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.

Does Claude Desktop support Streamable HTTP transport?

Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.