Stoplight MCP. Audit, document, and map entire API schemas from chat.

Listen, forget switching tabs or running complex CLI commands just to check an API doc. This MCP Server lets your AI client talk straight to your Stoplight workspace. It gives you hands-on access—you can design, document, and audit entire API lifecycles without ever leaving the chat window. You're gonna get full lifecycle visibility right where you work.

We structured this so you don't gotta know the underlying structure; you just ask for what you need, and your agent handles it. It keeps everything mapped securely to your Stoplight workspace, letting you run architectural reviews and pull documentation without losing context.

Organizational Oversight

You can start by mapping out the whole house. To see every top-level organizational container in your account, just call list_workspaces. For a broader view of everything available, list_projects shows all API documentation repositories housed within your workspace. You can track down who's been doing what with list_workspace_activity, which gathers and displays recent updates across the whole workspace.

To check team ownership, run list_workspace_members; this lists every person associated with your current API workspace and maps out their specific roles.

Project Deep Dives

When you zero in on a specific area, the tools help you drill down fast. If you want to know what's inside an API project—every file, endpoint, or model it contains—you use list_project_nodes. Need the full backstory on one particular repository? Call get_project_details to retrieve detailed metadata about a named Stoplight API project.

For the absolute nitty-gritty of any given documentation node, get_node_details pulls the complete, raw OpenAPI schema text you need for auditing or comparison.

What You Can Actually Do

Your AI client uses these tools to manage three key areas: Workspaces, Projects, and Schema Details. It can show all accessible organizational containers using list_workspaces, while also letting you monitor recent activity across them via list_workspace_activity. When you're working on a project, your agent runs list_projects to survey the available API documentation repositories.

You can then get deep visibility into a specific repo's metadata with get_project_details, and enumerate every component—files, endpoints, models—inside that project by calling list_project_nodes. If you need raw data for a schema comparison or audit, use get_node_details to pull the full OpenAPI text. Finally, if you gotta know who's responsible for what, your agent runs list_workspace_members to list all team members and their roles.