This MCP ([Model Context Protocol](https://modelcontextprotocol.io/introduction)) server provides AIs with tools to interact with your OpsLevel
If you already use Opslevel MCP, the opslevel mcp mcp server is the piece that lets your assistant work with it directly. This MCP (Model Context Protocol) server provides AIs with tools to interact with your OpsLevel account.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Actions — CampaignsChecks — ComponentsDomains — FiltersInfrastructure — RepositoriesSystems — TeamsConfiguration is passed through the environment: OPSLEVEL_API_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
Among the cloud and infrastructure options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Opslevel MCP's toolset — Actions, Checks, Domains and 2 more — is a fair guide to whether it matches your workflow. It is maintained by OpsLevel; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Actions | Campaigns |
| Checks | Components |
| Domains | Filters |
| Infrastructure | Repositories |
| Systems | Teams |
> {
> "mcpServers": {
> "opslevel": {
> "url": "https://app.opslevel.com/mcp"
> }
> }
> }
>Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| OPSLEVEL_API_TOKEN | Credential the server authenticates with. | Yes |
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.
AWS Labs' official server suite — current AWS docs, CDK guidance, cost analysis and service tools.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.
Workers, KV, R2 and D1 by conversation — Cloudflare's official remote servers for building and observability.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.