Knowledge · 1 min read
Custom tools (MCP)
Connect Intric to your own systems through a Model Context Protocol server.
Custom tools let your organization connect Intric to systems no ready-made integration covers, using the Model Context Protocol (MCP). An administrator registers the server, Intric reads what it can do, and the resulting capabilities become attachable to assistants.
What a custom tool is
Section titled “What a custom tool is”A custom tool is a connection your organization builds itself, to its own systems — an internal case-management tool, a specific database, anything a standard integration doesn’t already cover.
Adding one to an assistant
Section titled “Adding one to an assistant”Once your administrator has registered an MCP server for your organization, attach the tools it exposes to an assistant from the Knowledge step of the creation wizard, or from the assistant’s settings.
Capabilities and approval
Section titled “Capabilities and approval”Like an integration, each capability a custom tool exposes can be set to run automatically or to ask for approval, depending on your organization’s configuration.
Security classification
Section titled “Security classification”Custom tools are classified manually by an administrator, based on what the connected system can access. If the tool reaches a system holding personal data, it should carry a matching security classification. See Tool classification.
When a server is unreachable
Section titled “When a server is unreachable”If Intric can’t reach the MCP server behind a custom tool, the tool becomes unavailable to any assistant it’s attached to until the connection is restored. This is an administrator-side issue to resolve — see AI Tools.