Skip to main content
The Model Context Protocol lets any server expose data + tools to any LLM client. Xura is an MCP client.

​
Why MCP

  • Bring your own data platform without a custom integration.
  • Expose your internal tools to Xura without shipping a plugin.
  • Everything MCP-compliant works out of the box.

​
Adding a server

AI Studio → MCPs → Add server. Provide:
  • Name — display name in the UI.
  • URL — the MCP server endpoint (usually https://…/mcp or wss://…).
  • Transport — HTTP or WebSocket.
  • Auth token — bearer token if the server requires it.
Xura connects, discovers tools + resources, and shows them under a per-server namespace (mcp_<serverPrefix>_<toolName>).

​
Permissions (default-deny)

Every discovered tool is disabled by default. Toggle the ones you trust — Xura won’t expose disabled tools to any Agent or Flow. This protects you from a compromised MCP server declaring destructive tools.

​
Using MCP tools in Flows

  • Show up in the action node tool dropdown alongside built-in and integration tools.
  • Planner considers them when planning from description.
  • Invoked with the tool’s declared arg schema.