How to connect tools with MCP
Every tool is an MCP server with declared schemas, organized in three namespaces and authenticated through vaults.
All tools in NeoXam Agents are MCP servers — Model Context Protocol over streamable HTTP — with declared input and output schemas. If an agent can call it, it is declared in the Catalog.
Three namespaces
platform.* — NeoXam product data and actions, shared across the organization: for example platform.dh-br (Business Rule tools), platform.dh-cfg (DataHub configuration search), or platform.aro-positions (ARO break and position data).
agent-specific.* — tools owned and used by a single agent team.
external.* — curated third-party integrations (Slack, Jira, and similar), admitted only through a security-reviewed registry.
External tools are gated
Arbitrary MCP URLs are rejected. A third-party tool enters the registry only after security review and OAuth flow validation.
Beta
The external tool registry is rolling out with the V1 Beta.
Credentials stay in vaults
Tools authenticate through workspace-scoped vaults backed by the physical secrets store. Tokens never appear in descriptors, code, logs, or traces — a redaction layer enforces this, and a missing credential fails explicitly rather than falling back to anonymous access.
Still stuck?
Tell us what you were trying to do and where it failed — screenshots and run IDs help. A human follows up.