Where it fits
No one right now: the deployment is gone.
- Do not attempt a connection from this listing.
- Check whether the provider redeploys elsewhere.
- Treat the old coordination claims as unavailable.
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 Relay
These skills cover adjacent tasks, matched by purpose and the work each one describes.
Ask which skill or flow fits a situation. It routes among the user-invoked skills in this repository.
Interview the user about a plan or design until its assumptions and trade-offs are clear.
Question a plan or decision until its weak points and missing details are clear.
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.