Any MCP server integration
Point Swoop at any MCP server and it can read metrics from anything that speaks the protocol — then ask your team about what it finds.
Why a human answer beats another chart
Most of a company's numbers live in tools no integration directory covers. MCP means the list stops being a limit: if the system can expose a metric, Swoop can watch it and ask about it.
What Swoop watches
Read-only, and only what you point it at.
- One tool call per source
- Whatever metric that tool returns
- Read-only; nothing is written back
History arrives on connect. Any MCP server can hand over past values, so signals can appear on the first sync rather than after a wait.
Goals you can track from this
Swoop reads what Any MCP server already reports and proposes a goal with your own numbers in it — a baseline, a target you can change, and who to ask about it each week. Nothing is asked of anyone until you accept one.
What it asks, and who it asks
Questions are phrased from the change, never from a theory about the cause — a leading question gets you agreement instead of information.
The signal
Any metric an MCP tool returns moves beyond its usual range
It asks
“Asked in the same shape as every other signal — open, and never naming a cause”
Routed to: Routed by stated expertise, exactly as for a built-in source
Usually answered by: Whoever your index says knows about that metric. Answering is free and unlimited on every plan — you are never billed for the people who reply.
Connecting it
A couple of minutes. A server URL, plus a token if that server wants one.
- 01Server URL
The MCP endpoint. Usually ends in /mcp or /sse.
- 02Access tokenoptional
If the server needs one. Leave blank for servers that don't.
- 03Tool to call
We'll list the server's tools when you connect, so you can copy the right name.
- 04Name this metric
What to call it in Signals.
- 05Where the rows areoptional
Dotted path to the array of points in the tool's result. Blank if it returns the array directly.
- 06Choose what it may watch
Every source states what it is allowed to look at. Ingesting everything available is how this becomes another dashboard nobody opens.
Credentials are stored in your own infrastructure and used read-only. Nothing is ever written back to Any MCP server, and answers are synthesized by an open-source model on Amazon Bedrock inside your own AWS account — no foundational-model vendor sees your data.
Connect Any MCP server and ask your first question
Free to start, and you only pay for panels that answer. A question nobody responds to, one that duplicates a live one, or one answered from what your people already told us costs nothing.
Start free