Which issues did the last analysis of our API repo introduce?
DeepSource analyses your code for quality and security. Memtro reads the accounts and repositories your token reaches, analysis runs with the issues each introduced, resolved and suppressed, default-branch issues by category and severity, pull requests, dependency vulnerabilities, and dependencies that break the license policy. When asked and granted, it can suppress or unsuppress an issue for the whole team, switch analysis on or off for a repository, change its default branch, and set its quality gates and thresholds. Where in the code each issue occurs is not returned.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right DeepSource tool, reads what it needs, and answers with the source cited.
These tools change something in DeepSource. 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 DeepSource 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 issues did the last analysis of our API repo introduce?
Which reachable vulnerabilities does the web repository have?
Which dependencies break our license policy?
How many issues did pull request 412 raise?
Set line coverage on the api repository to at least 80.
Maya Okafor, a tech lead at Northwind, asked which issues the last analysis of the API repository introduced. Memtro read the latest run and listed the new issues by category and analyzer, alongside how many were resolved.
Tom Reilly, an engineering manager at Acme Ltd, asked Memtro to make security issues fail pull request checks on the payments repository. Memtro set the category gate, so new pull requests with security issues now fail their check.
The teams that lean on DeepSource most, a question each of them asks, and what they connect beside it.
A record in DeepSource 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 DeepSource, open your avatar → Settings → Tokens and generate a token named Memtro with an expiry. It has your own access to every account you belong to.
In Memtro, open Connections → DeepSource and paste the Personal access token.
Add the On-premise host only for a self-hosted DeepSource. An administrator grants the suppression, analysis and gate actions by name to the teams that may use them.
Ask which issues the last analysis of your API repo introduced.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The DeepSource tools are the same everywhere.
Only when you ask, and only what it has been granted: suppress an issue for every repository in the team; unsuppress an issue for the team; switch analysis on for a repository; switch analysis off for a repository; change a repository's default branch (starts a new analysis); set an issue category's quality gate on a repository; set an issue priority's quality gate on a repository; set a metric's quality gate on a repository; set a metric's threshold on a repository. 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.
Personal access token. In DeepSource, open your avatar → Settings → Tokens and generate a token named Memtro with an expiry. It has your own access to every account you belong to.
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
