microtica agents
Start free
Docs menu

Connect MCP servers

AWS, Kubernetes, Git, and Cloudflare cover most investigations, but your stack might have something else the Investigator should reach — an observability platform, an incident tool, any other MCP server your team runs. The server needs to be reachable over the public internet at an HTTP(S) URL; Microtica’s SSRF guard rejects private and reserved network destinations, both when you connect it and on every call afterward. You don’t need an AWS or Kubernetes connection first — a custom MCP server can be the only tool source in a project. Connect it once, and its tools join the Investigator’s built-in ones.

Connect

  1. In the console, open your project’s settings and choose External Servers under MCP.
  2. Click Connect. The Connect MCP server dialog opens.
  3. Fill in a Name for the server, its Server URL, and — if the server requires one — a Bearer token. Many MCP servers need no auth at all, so the token is optional.
  4. Click Connect. Microtica connects to the server and lists its tools before saving, so a bad URL or token fails here — not mid-investigation.

What it unlocks

Once connected, the server’s tools are available to the Investigator alongside its built-ins for this project’s investigations. Every call to one of these tools pauses for your approval first — even a read-only call — so a custom server won’t run unattended the way built-in tools can; an investigation that needs one waits with needs_input until someone approves the call, including investigations started over the MCP API. The bearer token is encrypted at rest and sent only to the server you pointed it at.

Disconnect

Click Disconnect next to the server and confirm. The next call to any of the server’s tools is rejected immediately, including one from an investigation that’s already running — only a call already in flight when you disconnect completes.

If it doesn’t connect

  • A failed connection shows the server’s own error — check the URL is reachable and, if the server requires one, that the token is correct and unexpired.
  • A slow or unresponsive server times out after 10 seconds; retrying is always safe.

That’s the last connection. With your accounts linked, the Investigator has what it needs — time to put it to work.

Next: MCP API keys