​

Setup an Agent

​

Deployment Options

​

Why Deploy Agents?

​

Self-Hosted MCP Servers

• Security: Keep sensitive data and processing within your infrastructure
• Performance: Reduce latency by running servers closer to your data sources
• Compliance: Meet regulatory requirements for data residency
• Custom Logic: Run proprietary or custom MCP server implementations

​

Team Collaboration

• Shared Resources: Make MCP servers available to your entire organization
• Centralized Management: Configure and monitor all servers from one place
• Access Control: Fine-grained permissions for different team members
• Usage Monitoring: Track and optimize MCP server usage across your team

​

Production Reliability

• High Availability: Automatic failover and redundancy
• Scaling: Handle increased load automatically
• Monitoring: Built-in observability and alerting
• Backup & Recovery: Automated backup strategies

​

Architecture Overview

Claude Desktop  →  WeaveMCP Console  →  Virtual Server  →  Agent  →  MCP Server
    (Client)          (Control Plane)     (Endpoint)     (Bridge)   (Implementation)

​

Components

1. Virtual MCP Server: A cloud-hosted endpoint that receives MCP requests
2. Agent: Self-hosted component that connects to virtual servers and manages local MCP servers
3. MCP Servers: Your actual tool implementations (filesystem, database, APIs, etc.)

​

Communication Flow

1. Claude Desktop makes an MCP request through the WeaveMCP proxy
2. Request is routed to your virtual server endpoint
3. Virtual server forwards the request to your deployed agent
4. Agent executes the request on the appropriate MCP server
5. Response flows back through the same chain

​

Getting Started

​

Prerequisites

• WeaveMCP Account: Sign up at console.weavemcp.com
• Virtual MCP Server: Created through the web console
• Agent Token: Generated for your virtual server
• Target Platform: Access to one of the supported deployment platforms

​

Basic Setup Steps

1. Create Virtual Server: Use the web console to create a new virtual MCP server
2. Generate Agent Token: Create an authentication token for your agent
3. Choose Deployment Method: Select from Kubernetes, Docker Compose, AWS EC2, or Google Cloud Run
4. Configure Agent: Set up environment variables and configuration files
5. Deploy: Follow platform-specific deployment instructions
6. Test Connection: Verify the agent connects to your virtual server

​

Environment Configuration

WEAVEMCP_AGENT_TOKEN=your-agent-token-here
WEAVEMCP_SERVER_URL=https://your-virtual-server.weavemcp.dev
WEAVEMCP_LOG_LEVEL=info

WEAVEMCP_HEALTH_CHECK_PORT=8080
WEAVEMCP_METRICS_PORT=9090
WEAVEMCP_RETRY_ATTEMPTS=3
WEAVEMCP_RETRY_DELAY=5s

​

Security Considerations

​

Network Security

• TLS Encryption: All communication uses TLS 1.3
• Token Authentication: Agents authenticate using secure tokens
• Network Isolation: Deploy agents in private networks when possible
• Firewall Rules: Only allow outbound HTTPS connections to WeaveMCP

​

Secrets Management

• Token Storage: Use platform-specific secret management (Kubernetes secrets, AWS Secrets Manager, etc.)
• Environment Variables: Avoid hardcoding tokens in configuration files
• Rotation: Regularly rotate agent tokens through the web console

​

Access Control

• Least Privilege: Grant minimal required permissions to agent containers
• Service Accounts: Use dedicated service accounts with limited scopes
• Network Policies: Implement network policies to restrict agent communication

​

Monitoring and Observability

​

Health Checks

# Basic health check
curl http://localhost:8080/health

# Detailed status including MCP server connections
curl http://localhost:8080/status

​

Metrics

• weavemcp_agent_requests_total: Total MCP requests processed
• weavemcp_agent_request_duration_seconds: Request processing time
• weavemcp_agent_connection_status: Connection status to virtual server
• weavemcp_mcp_server_status: Status of individual MCP servers

​

Logging

{
  "timestamp": "2024-01-15T10:30:00Z",
  "level": "info",
  "message": "MCP request processed",
  "server": "filesystem-server",
  "method": "list_files",
  "duration_ms": 125
}

​

Troubleshooting

​

Common Issues

​

Debug Mode

WEAVEMCP_LOG_LEVEL=debug

• Detailed request/response logging
• Connection status information
• MCP server communication details
• Performance metrics

​

Next Steps

​

Advanced Topics

• Load Balancing: Deploy multiple agents for high availability
• Auto Scaling: Scale agents based on demand
• Multi-Region: Deploy agents across multiple regions
• Custom MCP Servers: Integrate your own MCP server implementations
• CI/CD Integration: Automate agent deployment and updates