Key Features
Key Features
- Multiple Server Support: Connect multiple MCP servers simultaneously
- Automatic Tool Routing: Tools are automatically prefixed by server name to avoid conflicts
- Standard MCP Protocol: Compatible with any MCP-compliant server
- Proxy Architecture: Seamlessly integrates external tools into your agent workflows
Configuration
Configure the MCP plugin by editing the~/.unpage/profiles/<profile_name>/config.yaml
file.
Configuration follows the standard MCP server configuration format: each server under the mcp_servers
key is a dictionary with the following keys, dependent on your chosen transport type:
For stdio (i.e., local MCP servers)
command
: The command to run the MCP serverargs
: The arguments to pass to the MCP server commandenv
: The environment variables to set for the MCP server
For http (i.e., remote MCP servers)
transport
: The transport type of the MCP server (http
,streamable-http
, orsse
)url
: The URL to connect to the MCP serverauth
: The authentication to use for the MCP server (either a string representing a Bearer token, or “oauth” to use OAuth authentication)headers
: The HTTP headers to send to the MCP server
Tool Usage
Once configured, tools from MCP servers become available to your agents automatically. Tools are prefixed with the server name to prevent conflicts:mcp_git_log
- View git history (from git server)mcp_filesystem_read_file
- Read file contents (from filesystem server)mcp_github_create_issue
- Create GitHub issues (from github server)