Who owns this service, and which checks is it failing?
OpsLevel connects Memtro to your service catalog. It reads services with owner team, tier, lifecycle, maturity level, language and tags, and one service in depth with its note, failing and passing checks, dependencies, dependents and last deploy. It reads teams with members and contacts, deploys in a time window, scorecards with pass rates and repositories. When asked, and once an administrator has granted the action by name, it can replace a service's note, add or remove tags, create, edit or delete a service, and record a dependency. OpsLevel tokens have no scopes and act as their creator.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right OpsLevel tool, reads what it needs, and answers with the source cited.
These tools change something in OpsLevel. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
Once OpsLevel is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
Which tier 1 services are failing checks?
Who owns the payments service, and how do I reach them?
What was deployed to production in the last 24 hours?
Which scorecards have the lowest pass rate?
Record that checkout depends on payments
Tom Reilly, site reliability engineer at Acme Ltd, asked who owned the payments service during an incident. Memtro named the owner team with its Slack channel and members, and the service's last deploy two hours earlier.
Priya Sharma, platform engineer at Northwind, asked Memtro to move the legacy billing service to the end-of-life lifecycle and tag it for migration. Memtro updated the service and added the tag in OpsLevel. Nobody was notified.
The teams that lean on OpsLevel most, a question each of them asks, and what they connect beside it.
A record in OpsLevel is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
UptimeRobot
Honeycomb
Cronitor
FireHydrant
StatusCake
GlitchTip
GLPI
Langfuse
LibreNMS
NetBox
Snipe-IT
Woodpecker CI
Zabbix
LangSmith
Helicone
GrowthBook
Drata
Intruder
GitGuardian
Secureframe
ilert
JumpCloud
ConfigCat
Split
Aikido Security
Astronomer
Comet Opik
CrowdStrike Falcon
Detectify
Domotz
LambdaTest
LangWatch
LlamaCloud
Logz.io
Lunary
NinjaOne
Northflank
Portkey
PromptLayer
PRTG Network Monitor
Raygun
Retell AI
Runpod
Shodan
Spike.sh
Squadcast
Tenable
UpGuard
Uptime.com
Vanta
Zenduty
Cortex
WorkOS
Kandji
Automox
Huntress
SimpleMDM
Healthchecks.io
Rapid7 InsightVM
ZenhubIn OpsLevel, open API → API Tokens and choose Create API Token.
Describe it as Memtro and copy the token from the confirmation, as it is shown once. It can do whatever its creator can.
In Memtro, open Connections → OpsLevel and paste it into API token.
Ask your first question: which tier 1 services are failing checks?
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The OpsLevel tools are the same everywhere.
Only when you ask, and only what it has been granted: replace a service's note (the previous note is returned); add tags to a service; remove a tag from a service; create a service in the catalog; change a service's name, description, owner team, tier, lifecycle, product, language or framework; record that one service depends on another; delete a service from the catalog. Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.
API token. In OpsLevel, open API → API Tokens and choose Create API Token.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time
