Fusion MCP server
Which servers in the official MCP registry are Fusion's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-08
- Registry nameio.github.BuilderIO/agent-native-analyticspublished by BuilderIO on GitHub
Published under the GitHub organisation BuilderIO, the same one builder.io links from its homepage. The registry ties that namespace to a GitHub sign-in.
- Staterequires sign-inchecked 2026-10-08
On 2026-10-08 the server answered and asked for a sign-in with a Fusion account (OAuth). It shows its tool list only to signed-in users, so we list none here.
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"agent-native-analytics": {
"type": "http",
"url": "https://analytics.agent-native.com/mcp"
}
}
}The first time it connects, the client opens a Fusion sign-in.
- io.github.BuilderIO/agent-native-assetsanswers, requires sign-inpublished by BuilderIO on GitHub
- io.github.BuilderIO/agent-native-brainanswers, requires sign-inpublished by BuilderIO on GitHub
- io.github.BuilderIO/agent-native-calendarnot asked yetpublished by BuilderIO on GitHub
- io.github.BuilderIO/agent-native-chatnot asked yetpublished by BuilderIO on GitHub
- io.github.BuilderIO/agent-native-clipsnot asked yetpublished by BuilderIO on GitHub
- io.github.BuilderIO/agent-native-contentnot asked yetpublished by BuilderIO on GitHub
- io.github.BuilderIO/agent-native-designnot asked yetpublished by BuilderIO on GitHub
- io.github.BuilderIO/agent-native-dispatchnot asked yetpublished by BuilderIO on GitHub
- io.github.BuilderIO/agent-native-formsnot asked yetpublished by BuilderIO on GitHub
- io.github.BuilderIO/agent-native-mailnot asked yetpublished by BuilderIO on GitHub
- io.github.BuilderIO/agent-native-plannot asked yetpublished by BuilderIO on GitHub
- io.github.BuilderIO/agent-native-slidesnot asked yetpublished by BuilderIO on GitHub
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.