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 VS Code Copilot 7 tools — connect in under 2 minutes

Name: Stoplight
Availability: InStock
Author: Vinkius

code.visualstudio.com/docs/copilot/chat/mcp-servers

Built by Vinkius GDPR 7 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

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.

GitHub Copilot Agent mode brings Stoplight data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 7 tools — Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

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 VS Code Copilot 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 VS Code Copilot via MCP

Follow these steps to integrate the Stoplight MCP Server with VS Code Copilot.

Create MCP config

Create a .vscode/mcp.json file in your project root

Add the server config

Paste the JSON configuration above

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

Start using Stoplight

Ask Copilot: "Using Stoplight, help me..." — 7 tools available

Why Use VS Code Copilot with the Stoplight MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Stoplight through the Model Context Protocol.

VS Code is used by over 70% of developers — adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

Stoplight + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Stoplight MCP Server delivers measurable value.

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

Stoplight MCP Tools for VS Code Copilot (7)

These 7 tools become available when you connect Stoplight to VS Code Copilot 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 VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot 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 VS Code Copilot

Common issues when connecting Stoplight to VS Code Copilot through the Vinkius, and how to resolve them.

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

Stoplight + VS Code Copilot FAQ

Common questions about integrating Stoplight MCP Server with VS Code Copilot.

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.