Stoplight MCP. Audit, inspect, and map complex API schemas conversationally.
Stoplight MCP connects your AI client directly to an API design and documentation system. Use it to audit, review, and map entire API lifecycles without ever leaving your chat window. Quickly inspect schemas, track team activity logs, or check project ownership details using simple conversation prompts.
Give Claude and any AI agent real-world access
List every accessible workspace, project repository, and individual documentation node within your entire organization.
See exactly who owns a project or which members are authorized to contribute to specific API workspaces.
Pull up recent logs of changes, seeing who updated what endpoint and when across the whole system.
Retrieve the full, structured documentation for any given API node, including its expected data types and parameters.
Ask an AI about this
Waiting for input…
What AI agents can do with Stoplight MCP - 7 Tools
These seven tools allow your AI agent to interact with every part of the Stoplight API, from listing all workspaces down to retrieving specific documentation node schemas.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Stoplight MCPGet Node Details
Extracts the full, detailed schema and raw text definition for one selected documentation node.
Get Project Details
Gives high-level metadata and status details for a chosen Stoplight project.
List Workspace Activity
Fetches recent logs detailing who made changes and what was updated within the...
List Workspace Members
Lists all users associated with the workspace and their current roles or permissions.
List Project Nodes
Lists all individual components—files, endpoints, or models—inside a specific API...
List Projects
Lists all specific API documentation repositories housed within a single workspace.
List Workspaces
Retrieves a list of all top-level organizational containers accessible in your Stoplight account.
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on each call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Stoplight, then connect any of our 5,200+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,200+ others, all in one place
- Add new capabilities to your AI anytime you want
- Connections are secured and governed automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog weekly
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Stoplight. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS CLOUD
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on each call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
The Overhead of Context Switching
Today, reviewing a single API dependency requires juggling at least four different screens: one for the project overview, one to list all endpoints, another to check activity logs, and finally, a fourth page just for the raw schema. You spend more time clicking through tabs and navigating menus than actually analyzing the data.
With this MCP, you keep everything in your chat window. Tell your agent what you need—say, 'What are the latest changes on the Billing API?'—and it pulls that information from `list_workspace_activity` and presents a clean, actionable summary. The result is instant context without leaving your development environment.
Stoplight MCP: Instant Schema & Project Insights
You don't have to run multiple reports or export CSVs just to get a status check. Instead, you can ask the agent to execute `list_projects` to map all available APIs and then use `get_project_details` on any one of them for full visibility.
It fundamentally changes your workflow from 'data gathering' to 'decision making.' You stop managing the tabs and start solving the architectural problem.
What Stoplight MCP does for your AI
Managing APIs used to mean jumping between complex dashboards: the schema view, the project roadmap, the activity feed—all separate tabs that kill momentum. This MCP pulls all of that context into your agent. You can ask your AI client for an overview of every workspace or pull up a full OpenAPI schema for a specific endpoint just by talking to it.
It lets you run architectural reviews and documentation checks conversationally. When you need this level of technical depth, Vinkius makes sure the Stoplight connection is ready for any MCP-compatible client, letting your agent handle complex tasks like checking recent changes or listing all contributors across multiple projects. You get instant visibility into API structures and development status without needing to click through a single dashboard.
019d760d-7deb-708b-b556-12b444403f68 How to set up Stoplight MCP
The bottom line is that you talk to your AI client, and it handles the complex navigation across Stoplight’s entire library of API definitions.
First, authenticate your AI client by installing the Stoplight MCP module into your environment.
Next, configure the connection by providing your unique STOPLIGHT_WORKSPACE slug and a valid API token.
Finally, simply prompt your agent with an action, like 'Show me all projects in core-billing' or 'What were the last 5 changes to this workspace?'
Who uses Stoplight MCP
This MCP is for senior technical staff—API Architects, Platform Engineers, and Technical Leads. If your job involves reviewing dozens of endpoints or keeping track of cross-team dependencies across large codebases, you'll hate clicking through multiple dashboards just to get an overview.
Reviews project readiness by listing projects and then diving into specific documentation nodes to validate schemas before design sign-off.
Resolves integration dependencies quickly by querying endpoint models across multiple, independent Stoplight projects without context switching.
Summarizes complex API documentation updates by pulling recent activity logs and project details into a single, coherent narrative.
Benefits of connecting Stoplight MCP
You cut out the dashboard-hopping. Instead of navigating through multiple tabs to see project structure, you simply ask your agent for a list of all projects using list_projects and get immediate results.
Stop manual documentation reviews. Need to know if an endpoint changed? Use list_workspace_activity to pull up recent logs instantly, letting you track changes without digging through date-stamped audit tables.
Deep dive into schemas on demand. Want the full structure of a payment node? Calling get_node_details gives you the raw OpenAPI schema immediately, perfect for validation checks.
Understand team ownership fast. Use list_workspace_members to instantly confirm who has admin or editor rights in any given workspace, solving governance questions right away.
See your whole picture at once. Start with list_workspaces to map the entire organizational container structure before drilling down into specific projects like 'core-billing-api'.
Stoplight MCP use cases
Reviewing a cross-functional dependency update
A backend engineer needs to know if two separate services (Billing and Inventory) are using the same version of a user ID field. They ask their agent to list all nodes in both projects, then use get_node_details on the relevant endpoints from each project to compare schemas directly.
Onboarding a new team member
A platform architect needs to assign roles. They ask their agent to call list_workspace_members, then review the output to see who has editing permissions, and finally check project details using get_project_details to confirm scope.
Tracking a critical bug fix deployment
A technical writer asks their agent for recent activity. The agent calls list_workspace_activity, providing the exact timestamp and user who updated the API, allowing the writer to write accurate release notes.
Mapping out a new feature scope
An architect wants to see all potential areas for a new payment gateway. They first use list_workspaces to define the boundaries, then run list_projects inside that workspace to catalog every existing API repository.
Stoplight MCP tradeoffs
What to watch out for, and the recommended way to handle each one.
Searching manually through UI filters
A user is stuck in the Stoplight dashboard trying to filter projects by owner, then finding documentation nodes one by one.
Instead, ask your agent to run list_projects first. Then, use get_project_details for metadata and list_workspace_members if you need ownership information.
Asking the AI client general questions
Prompting 'Tell me about our APIs' results in a vague summary because the agent can’t know what to search for.
Be specific. Prompt: 'List all projects and show recent activity.' This triggers both list_projects and list_workspace_activity, giving you concrete data.
Copying and pasting schemas into a document
A developer copies raw schema text, which is difficult to read or verify for type safety.
Ask your agent to use get_node_details. It will pull the structured OpenAPI schema definition directly into your chat, making it clean and ready for review.
When to use Stoplight MCP
Use this MCP if your workflow involves auditing large-scale API documentation or managing complex architectural governance. If you spend more time navigating dashboards than actually writing code or content, this is for you. You need conversational access to system metadata—things like who owns a project (list_workspace_members), what changes happened recently (list_workspace_activity), and the full technical definition of an endpoint (get_node_details). Don't use this if your only goal is general knowledge retrieval or simple text generation. If you just need to write a blog post about APIs, your AI client handles that fine without needing this MCP. But if you need to validate the API definitions themselves, stick with Stoplight.
Frequently asked questions about Stoplight MCP
How does the Stoplight MCP help with API governance? +
The Stoplight MCP provides tools like list_workspace_members to track project ownership. You can instantly confirm who has admin rights and which users are contributors across your entire organization's APIs.
Can I use the Stoplight MCP to check API schema details? +
Yes, calling get_node_details retrieves the full OpenAPI schema for any specific node. This is crucial for ensuring type safety across your documentation.
What if I need to see what changed recently in my APIs using Stoplight MCP? +
You use list_workspace_activity. It provides an immediate log of recent changes, telling you which endpoints were updated and by whom, saving you manual checks.
How many different kinds of API projects can I list with Stoplight MCP? +
You first call list_workspaces to see the top-level groupings. Then, running list_projects inside that workspace shows all contained documentation repositories.
Does the Stoplight MCP require specific credentials? +
Yes, you must authenticate and provide your STOPLIGHT_WORKSPACE slug along with a valid API token to connect the agent to your account data.