Custom MCP Servers

Organizations can connect custom MCP servers when they need Arif to use a specialized internal system or workflow. This is an administrator and developer activity, but the public concept is straightforward: a custom server adds reviewed capabilities to Arif.

Good Use Cases

• Read-only access to approved business context.
• A specialized reporting or analytics workflow.
• A controlled project, ticket, or knowledge source.
• A reviewed action that has clear inputs, outputs, and safety expectations.

Public Requirements

A custom server should:

• Describe each capability clearly.
• Use the minimum necessary access.
• Avoid exposing secrets to users or model output.
• Separate read-only tools from tools that create side effects.
• Be reviewed before it is made available in chat.

User Experience

After a custom server is approved and enabled, users interact with it like any other Arif capability. They ask for a business outcome, and Arif decides whether the custom tool is relevant.

Safety

Custom tools are still governed by Arif's normal execution path. Permissions, policy, approvals, and rollback expectations should be clear before the tool is enabled.