Skip to main content

​
Pick a vendor, paste a token

Connecting an external connector used to mean hand-typing an endpoint URL and transport out of vendor docs. The catalog removes that: press + on the External connectors group of the MCP Servers page and pick a vendor card. The editor arrives with the vendor’s endpoint, transport and auth header already filled in, the token instructions under the Token field, and a Server docs link to the vendor’s own documentation. Every prefilled field stays editable, and the result is an ordinary MCP server: the same HTTPS-only rule, Secret Manager token storage, deny-by-default tool curation and approvals apply unchanged.

​
Connectable today

All six use Streamable HTTP transport and a standard Authorization: Bearer header, prefilled for you.
Grafana is the one you host. There is no fixed endpoint — you run mcp-grafana next to your Grafana, and it must be reachable over HTTPS from outside your network: the SSRF guard rejects localhost and private ranges, so a purely internal Grafana cannot be connected.

​
Coming soon

Some vendors’ hosted MCP servers authenticate only with OAuth, which WHAWIT does not run yet. They appear in the catalog as visible roadmap, marked Coming soon, and cannot be connected:
  • Atlassian (Jira + Confluence) — Jira issues and Confluence runbooks.
  • Slack — search workspace history for incident context.
  • Google Cloud Logging — query log entries in your GCP projects.
  • Datadog — metrics, monitors and dashboards.
  • Cloudflare — zones, Workers and edge observability.

​
Anything else: Custom connector

The trailing Custom connector card connects any vendor-hosted MCP server not listed — name, HTTPS URL and token. Servers for your own operations go under Internal operations instead; the catalog is for vendor context surfaces only.

​
After connecting

  1. On the new server, press Discover tools — everything arrives denied.
  2. Flip Allowed on the tools the agents should have. Connector tools default to no approval requirement at first allow, so read context flows without a human in the loop — flag Requires approval yourself on any write tool you want gated.
  3. Scope the vendor token narrowly: agents see exactly what the token can see.

Set up MCP Actions

Both flows end to end — discovery, curation and the organization policy.

Resolving incidents

Where the allowed tools show up: agents, Radar and the Run action button.