Creating Your First vMCP
This tutorial will guide you through creating your first vMCP that aggregates multiple MCP servers.
Prerequisites
- vMCP installed and running (see Installation)
- At least one MCP server configured
Step 1: Navigate to vMCPs Page
- Open http://localhost:8000 in your browser
- Click on "vMCPs" in the navigation menu
You'll see the vMCP management interface.
Step 2: Create a New vMCP
Click the "Create vMCP" button. This opens the vMCP creation dialog.
Fill in Basic Information
- Name: Give your vMCP a descriptive name (e.g., "Development Tools")
- Description: Explain what this vMCP is for (e.g., "Aggregates filesystem and git tools for development")
Step 3: Add MCP Servers
In the "MCP Servers" section:
- Click "Add Server"
- Select an MCP server from the dropdown
- Set the priority (lower numbers = higher priority)
- Add more servers as needed
Example Configuration:
Server 1: filesystem (Priority: 1)
Server 2: github (Priority: 2)
Server 3: postgres (Priority: 3)
Understanding Priority
When multiple servers provide the same tool name, vMCP uses priority to determine which one to call:
- Priority 1 = Highest (called first)
- Priority 2 = Second choice
- Priority 3 = Third choice, etc.
Step 4: Configure Active Config (Optional)
The "Active Config" section allows you to set runtime parameters that can be used with variable substitution.
Example:
{
"default_repo": "myorg/myrepo",
"api_key": "your-api-key",
"workspace_path": "/home/user/projects"
}
These values can be referenced in tool calls using @config:key_name:
{
"repo": "@config:default_repo"
}
Step 5: Save Your vMCP
Click "Create" to save your vMCP.
You'll see your new vMCP appear in the list with:
- Server count
- Active status
- Configuration indicator
- Creation date
Step 6: Test Your vMCP
View Available Tools
- Click on your vMCP card
- In the dropdown menu, select "View Tools"
- You'll see all tools from all connected servers
Use with MCP Client
Your vMCP is now available at:
mcp://localhost:8000/vmcps/{vmcp_id}
Configure your AI agent or MCP client to connect to this endpoint.
Example: Development vMCP
Here's a complete example for local development:
Name: Development Tools
Description: Local development with filesystem, git, and documentation access
Servers:
- filesystem (Priority: 1)
- git (Priority: 2)
- memory (Priority: 3)
Active Config:
{
"workspace": "/home/user/projects/myapp",
"default_branch": "main"
}
This vMCP gives your AI agent access to:
- File operations (read, write, list)
- Git operations (commit, push, pull)
- Memory/context storage
- All tools can reference the workspace path via
@config:workspace