Tools & MCP

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 & MCP lets you connect those accounts to Neatlogs so Copilot (the chat in Investigate) and Neat Agent (the neat AI panel on a trace) can read them while they help you, without you leaving the chat to copy things across.

You connect apps under Settings → Account → Tools & MCP. It's a personal setting: each teammate connects their own accounts, separately in each organization. Connected apps always run with your permissions: Copilot only sees the issues, channels, and pages your account can, never a shared team token. The exception is GitHub repositories reached through your organization's GitHub App, which follow the App's access policy (see GitHub).

Connectable apps

Connect any of these with an OAuth sign-in. There are no tokens to paste:

These four are marked Featured, but the catalog is larger: search Settings → Account → Tools & MCP for other apps (for example Gmail or Jira). Apps that aren't enabled for your deployment show Unavailable.

Connecting an app

1. Open Settings → Account → Tools & MCP and stay on the Apps tab.
2. Find the app. Filter with All, Connected, or Available, or type at least two characters to search apps and capabilities across the whole catalog.
3. Select Connect. Authorization opens in a new tab; if your browser blocks it, allow pop-ups for Neatlogs and select Connect again.
4. Approve access in that tab, return to Neatlogs, and select Check connection. The app now shows Connected and is available in chat.

Select Reauthorize to renew or change the permissions you granted. To disconnect, select Disconnect, then Disconnect account. Copilot and Neat Agent stop using your account for that app. If you reconnect soon after, Neatlogs may restore the earlier grant without asking you to sign in again.

GitHub

GitHub has its own entry: select Manage GitHub.

• Repository connections shows whether your organization's GitHub App grants access. When the App is active, Copilot uses only repositories mapped to the current project. Under the Shared policy it reads them with the App's permissions; under Strict it also checks yours. Organization owners and admins install the App, map repositories, and choose the policy in Integrations.
• If the organization uses the Strict repository access policy, select Authorize GitHub App under Your App authorization so Copilot can use your GitHub permissions for mapped repositories.
• Where your organization offers it, Individual connection lets you connect a personal GitHub account (Connect with GitHub, later Reconnect GitHub) or a personal access token (Use a personal token, later Replace token).

Copilot opens a pull request only when you clearly ask for one and an admin has turned on Allow pull request writes for that repository.

Custom MCP servers

The Custom MCP tab registers a Model Context Protocol server that an AI evaluator can be granted as evidence while it scores runs.

1. Select Add server.
2. Enter a Name and an HTTPS Server URL for a Streamable HTTP MCP endpoint.
3. Add any Authentication headers the server needs (for example Authorization). Header values are encrypted at rest and never shown again.
4. Turn on Available for evaluator grants, then select Save server.
5. Open the saved server and select Test saved connection. Neatlogs sends an MCP initialize request to the URL.

The test fails if the server isn't publicly reachable over HTTPS, redirects (redirects are rejected), doesn't answer within about 8 seconds, or returns an error. "Auth rejected (HTTP 401)" or "(HTTP 403)" means the server refused your authentication headers.

Custom MCP servers are personal, like apps: each server belongs to you in the selected organization. An evaluator can use one only when the server has Available for evaluator grants turned on and the evaluator's evidence includes Custom MCP server. To change credentials later, open the server and select Replace headers; saving replaces every stored header. After Remove server, evaluator grants that use it lose access to its tools.

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"
"Find the Notion runbook for payment retries"

Copilot is the assistant in Investigate. Ask it about a search, an incident, or a set of runs and it pulls in the connected context it needs. Neat Agent is the neat AI panel you open from a trace with Ask neat AI, and it can use the same connected apps while it answers questions about that run.

How this differs from Integrations

Neatlogs has two places to connect outside tools, for two different jobs:

Some of the same apps appear in both, and that's expected. In Tools & MCP they're tools you use through chat; in Integrations they're wired into Neatlogs workflows. Connecting Linear in one place does not connect it in the other.

Frequently asked questions

Why doesn't Copilot use my connected apps in a project?

Connected apps work in projects where you're a Project Member or Project Admin, not a Project Viewer. If chat reports that the organization's plan doesn't allow integration tools, ask an organization owner.

Can an AI evaluator use my connected apps?

Only when the evaluator's evidence includes Connected tools & MCP, and only for read-only calls. See AI evaluators.

Is this the same as the Neatlogs MCP server?

No. This page connects outside tools into Neatlogs. The Neatlogs MCP server works the other way: it lets your own coding agent query Neatlogs from your editor.

Related