Integrations overview
Step-by-step guides for the MCP servers SRE teams use most, each set up read-only.
Each guide covers the same five things: a read-only credential, running and exposing the server, onboarding it in sremcp, which tools to approve, and questions to try.
| Server | Where it runs | Transport | Authentication in sremcp | Read-only switch |
|---|---|---|---|---|
| GitHub | Hosted by GitHub | Streamable HTTP | OAuth, or Bearer token (PAT) | /readonly URLs |
| Grafana | Your network | Streamable HTTP | Bearer token | --disable-write |
| Kubernetes | Your cluster | Streamable HTTP | Bearer token, through Supergateway | read_only = true |
| Amazon EKS | Hosted by AWS, or your network | Streamable HTTP, through Supergateway | Bearer token | IAM read-only policy |
| PostgreSQL | Your network | Streamable HTTP, through Supergateway | Bearer token | --access-mode=restricted |
| Prometheus | Your network | Streamable HTTP | Bearer token, through Supergateway | Read-only by design |
| Sentry | Hosted by Sentry | Streamable HTTP | OAuth, or Custom header | Read-scoped token |
| Servers behind Clerk | Your own app | Streamable HTTP | OAuth | Your app's tools |
Any other server
sremcp works with any MCP server it can reach over https. For one that isn't listed:
- Find its transport. If it only runs as a local command, bridge it. See Transports.
- Give it a read-only credential, and turn on its read-only mode if it has one.
- If it runs in your network, expose it with a key.
- Onboard it, approve its read tools, and grant it to the roles that need it.