Unify FAQs

Question 1

How does Unify provide control over who can access specific tools?

Accepted Answer

Unify implements role-based access control (RBAC). You can define various roles (e.g., 'admin', 'readonly', 'developer') and assign specific tool permissions to each. This allows you to precisely control which MCP tools or plugins are visible and accessible to different clients or users.

Question 2

What is Unify (mcp-gateway) and what problem does it solve?

Accepted Answer

Unify (mcp-gateway) is a powerful gateway that consolidates multiple Model Context Protocol (MCP) servers into a single, efficient endpoint. It solves common issues like high resource usage, duplicated configuration, lack of centralized control, and difficulty integrating custom Python tools in multi-server MCP setups.

Question 3

How does Unify improve resource efficiency for MCP servers?

Accepted Answer

Unify employs lazy loading, meaning server subprocesses are only spawned on-demand when their tools are first called. It also features automatic cleanup, killing idle server subprocesses after a configurable timeout, significantly reducing memory and CPU consumption.

Question 4

What are the key benefits of using Unify for AI development?

Accepted Answer

Unify streamlines AI development by centralizing MCP server management, reducing resource overhead through lazy loading and auto-cleanup, enabling rapid integration of custom Python functionalities, and providing robust role-based access control for enhanced security and organization.

Question 5

Can I add custom Python tools or functions with Unify?

Accepted Answer

Yes, Unify fully supports in-process Python `@tool` plugins. You can easily define custom functions within your Python code, and Unify automatically generates their schemas from type hints, allowing seamless integration with your MCP clients without needing a full custom server.

Unify

Unify

Key Features

Use Cases

Key Features

Use Cases