Where it fits
No one right now: the provider blocks automated access and the listing is unverified.
- Do not attempt a connection from this listing.
- Check the provider site directly.
- Treat all capability claims as unverified.
A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.
Skills that pair with Playground AI
These skills cover adjacent tasks, matched by purpose and the work each one describes.
Explore what the user wants, what they assume, and which approach is worth committing to before any creative work. Use before building a feature, component, plan, or other new work where a wrong direction is costly.
Shared vocabulary for designing deep modules. Use it to design or improve a module's interface, find opportunities to deepen one, decide where a seam goes, or make code easier to test and navigate with AI, or when another skill needs the deep-module vocabulary.
Produces several sharply different interface designs for the same module, with sub-agents working in parallel. Use it when someone wants to design an API, survey interface options, weigh different module shapes, or says design it twice.
No skills found
Try a different search term or clear the filters.
Common failure modes
These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.
- Authentication fails or no tools appear. The listing does not verify the provider's credential flow; check its documentation before retrying.
- The endpoint responds but rejects tool calls. Confirm the current address and any account, key, or payment requirement with the provider.
- Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Before you connect
- The provider can see the requests and data your agent sends through the server.
- Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
- Use project scope for repository-specific servers; use global scope for personal tools.
- Remove the server and revoke its token when you stop using it.
Check the connection before a real task
These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.