Capabilities
Model Context Protocol servers give coding agents tools and data: a browser, GitHub, up-to-date library docs. Each entry has a ready manifest, its credentials and its security notes.
Which agents receive them
Self-hosted: you control the registry
Your installation keeps its own capability registry. Register entries from this directory, or your own private skills, MCP servers and plugins; set versions, permissions and install policies. Nothing is fetched from us, and nothing phones home.
Managed cloud: we run it for you
The same registry, operated by us. Your organization registers and installs capabilities the same way, with the same policies and approvals. Compare the two.
6 mcp servers
Chrome DevTools team (Google)
Google's Chrome DevTools MCP server. Gives the agent a live Chrome with DevTools — console, network requests, performance traces and screenshots — to debug web apps.
Upstash
Upstash's Context7 MCP server. Fetches current, version-specific documentation and code examples for libraries, so the agent does not rely on outdated training data.
Model Context Protocol project
The MCP reference fetch server. Retrieves a web page and converts it to Markdown so the agent can read documentation, changelogs or issues linked from a task.
GitHub
GitHub's official MCP server. Gives the agent tools for repositories, issues, pull requests, Actions runs and code security alerts through the GitHub API.
Microsoft
Microsoft's Playwright MCP server. Lets the agent open pages in a real browser, click, type and read the accessibility tree while it builds or debugs a web app.
Shopify
Shopify's developer MCP server. Searches Shopify's developer documentation and API schemas — Liquid, Admin GraphQL, Storefront, Functions — so the agent builds against real APIs.