Skip to main content

​
Overview

Group Management in MCPHub allows you to organize your MCP servers into logical collections based on functionality, use case, or access requirements. This enables fine-grained control over which tools are available to different AI clients and users.

​
Core Concepts

​
What are Groups?

Groups are named collections of MCP servers that can be accessed through dedicated endpoints. Instead of connecting to all servers at once, AI clients can connect to specific groups to access only relevant tools.

​
Benefits of Groups

  • Focused Tool Access: AI clients see only relevant tools for their use case
  • Better Performance: Reduced tool discovery overhead
  • Enhanced Security: Limit access to sensitive tools
  • Improved Organization: Logical separation of functionality
  • Simplified Management: Easier to manage related servers together

​
Creating Groups

​
Via Dashboard

  1. Navigate to Groups Section: Click “Groups” in the main navigation
  2. Click “Create Group”: Start the group creation process
  3. Fill Group Details:
    • Name: Unique identifier for the group
  4. Add Servers: Select servers to include in the group

​
Via API

Create groups programmatically: 
curl -X POST http://localhost:3000/api/groups \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_JWT_TOKEN" \
  -d '{
    "name": "web-automation",
    "servers": ["playwright", "fetch"]
  }'

​
Group Types and Use Cases

Purpose: Browser automation and web scrapingServers:
  • playwright: Browser automation
  • fetch: HTTP requests and web scraping
  • selenium: Alternative browser automation
Use Cases:
  • Automated testing
  • Data collection
  • Web monitoring
  • Content analysis
Endpoint: http://localhost:3000/mcp/web-automation
Purpose: Data manipulation and analysisServers:
  • sqlite: Database operations
  • filesystem: File operations
  • spreadsheet: Excel/CSV processing
Use Cases:
  • Data analysis
  • Report generation
  • File processing
  • Database queries
Endpoint: http://localhost:3000/mcp/data-processing
Purpose: Messaging and collaborationServers:
  • slack: Slack integration
  • discord: Discord bot
  • email: Email sending
  • sms: SMS notifications
Use Cases:
  • Team notifications
  • Customer communication
  • Alert systems
  • Social media management
Endpoint: http://localhost:3000/mcp/communication
Purpose: Software development toolsServers:
  • github: GitHub operations
  • gitlab: GitLab integration
  • docker: Container management
  • kubernetes: K8s operations
Use Cases:
  • Code deployment
  • Repository management
  • CI/CD operations
  • Infrastructure management
Endpoint: http://localhost:3000/mcp/development
Purpose: Machine learning and AI toolsServers:
  • openai: OpenAI API integration
  • huggingface: Hugging Face models
  • vector-db: Vector database operations
Use Cases:
  • Model inference
  • Data embeddings
  • Natural language processing
  • Computer vision
Endpoint: http://localhost:3000/mcp/ai-ml

​
Group Endpoints

​
Accessing Groups

Each group gets its own MCP endpoint:
  • HTTP MCP
  • SSE (Legacy)
http://localhost:3000/mcp/{group-name}
Examples:
  • http://localhost:3000/mcp/web-tools
  • http://localhost:3000/mcp/data-processing
  • http://localhost:3000/mcp/communication

​
Group Tool Discovery

When connecting to a group endpoint, AI clients will only see tools from servers within that group: 
# List tools in web-tools group
curl -X POST http://localhost:3000/mcp/web-tools \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/list",
    "params": {}
  }'
Response will only include tools from fetch and playwright servers.

​
Dynamic Group Management

​
Adding Servers to Groups

  • Dashboard
  • API
  1. Navigate to the group in the dashboard
  2. Click “Manage Servers”
  3. Select additional servers to add
  4. Click “Save Changes”

​
Removing Servers from Groups

  • Dashboard
  • API
  1. Navigate to the group in the dashboard
  2. Click “Manage Servers”
  3. Unselect servers to remove
  4. Click “Save Changes”

​
Best Practices

​
Group Organization

Organize by Use Case: Group servers based on what users want to accomplish, not just technical similarity.
Keep Groups Focused: Avoid creating groups with too many diverse tools. Smaller, focused groups are more useful.
Use Descriptive Names: Choose names that clearly indicate the group’s purpose and contents.

​
Performance Optimization

Balance Group Size: Very large groups may have slower tool discovery. Consider splitting into smaller groups.
Monitor Usage: Use analytics to identify which groups are heavily used and optimize accordingly.

​
Troubleshooting

Check:
  • User has proper permissions
  • Group exists and is active
  • Servers in group are running
  • Network connectivity
Solutions:
  1. Verify user group membership
  2. Check group configuration
  3. Test individual server connections
  4. Review access logs
Possible causes:
  • Server not properly added to group
  • Server is not running
  • Tool discovery failed
  • Caching issues
Debug steps:
  1. Verify server is in group configuration
  2. Check server status
  3. Force refresh tool discovery
  4. Clear group cache
Common issues:
  • Too many servers in group
  • Slow server responses
  • Network latency
  • Resource constraints
Optimizations:
  1. Split large groups
  2. Monitor server performance
  3. Implement request caching
  4. Use connection pooling

​
Next Steps

Smart Routing

AI-powered tool discovery across groups

Authentication

User management and access control

API Reference

Complete group management API

Configuration

Advanced group configuration options
⌘I