Tools & MCPs
Connect your own apps — GitHub, Linear, Slack, Notion and more — so Copilot and Neat Agent can use them on your behalf.
When you're debugging an agent, the context you need is rarely all in Neatlogs. The failing run points at a pull request, a Linear issue, a Slack thread, or a Notion doc. Tools & MCPs lets you connect those accounts to Neatlogs so Copilot and Neat Agent can read from — and act in — them while they help you, without you leaving the chat to go copy things across.
You connect apps under Settings → Tools & MCPs, and each teammate connects their own accounts. Tools always run with your permissions — Copilot only ever sees the repos, issues, and channels you can, never a shared team token.
Connectable apps
Connect any of these with a single OAuth sign-in — no tokens to paste, no configuration:
| App | What Copilot & Neat Agent can do |
|---|---|
| GitHub | Search your code and read repository files to ground a fix in the actual source |
| Linear | Look up and read issues so a run can be tied back to the ticket that tracks it |
| Slack | Read channel history for context, and post updates back to your team |
| Notion | Search and read pages and docs from your knowledge base |
These four are featured, but the catalog is larger — search Settings → Tools & MCPs for others (for example Gmail or Jira). Apps that aren't available yet appear as Coming soon.
Connections are per-teammate and scoped to your active organization. Connecting GitHub for yourself doesn't connect it for anyone else, and everything a tool does runs under your own account's access.
Connecting an app
- Open Settings → Tools & MCPs.
- Find the app — apps are grouped into Connected, Featured, and All apps, with a search box.
- Toggle it on. You're sent to that app's sign-in page to authorize Neatlogs.
- On return, the card shows a Connected for you badge. That's it — the app is now available in chat.
To disconnect, toggle the app off and confirm. Copilot and Neat Agent stop using it immediately. Reconnecting later is instant — you won't have to sign in again unless you fully revoke access from the app's side.
Custom MCP servers
Already run your own Model Context Protocol server? Add it under Settings → Tools & MCPs → Add MCP server by giving it a name and an https URL, plus any auth headers it needs. A Test button checks the connection before you save.
Custom MCP servers power Neatlogs' evaluators — an AI judge can call your own tools while scoring runs. The featured OAuth apps above are what Copilot and Neat Agent use in chat.
In Copilot and Neat Agent
Once an app is connected, there's nothing extra to switch on in chat — Copilot and Neat Agent pick up your connected apps automatically. Just ask in plain language, and they'll reach for the right tool when it helps:
"Open the GitHub file where this tool is defined and check the timeout"
"What Linear issue tracks this failing checkout flow?"
"Summarize the #incidents Slack thread from this morning"
"Post a summary of this investigation to #agent-eng"Copilot is the assistant that lives alongside your traces — ask it about a specific run or search result and it can pull in the connected context it needs. Neat Agent runs deeper, multi-step investigations across many traces, and can use the same connected apps as it reasons.
Not sure what's connected? Just ask — "which apps do I have connected?" — and Copilot will tell you.
How this differs from Integrations
Neatlogs has two places to connect outside tools, for two different jobs:
| Tools & MCPs | Integrations | |
|---|---|---|
| Purpose | Give Copilot & Neat Agent tools to use in chat | Wire Neatlogs into your workflow — alerts, issue creation, trace import |
| Connected by | Each teammate, individually | Set up once for the workspace |
| Examples | GitHub, Linear, Slack, Notion for chat context | Slack alert routing, creating a Linear issue from a detection, importing traces |
Some of the same apps appear in both — that's expected. In Tools & MCPs they're tools you wield through chat; in Integrations they're wired into automated Neatlogs workflows.