​
Installing WeaveMCP on Your Laptop

WeaveMCP is a control plane for managing Model Context Protocol (MCP) servers. The weave CLI tool allows you to connect your local development environment or AI applications (like Claude Desktop) to managed MCP servers.

​
Quick Install

Install the weave CLI with a single command: 
curl -fsSL https://console.weavemcp.com/install.sh | bash
This script will:
  • Detect your operating system and architecture
  • Download the appropriate weave binary
  • Install it to ~/.local/bin/weave
  • Make it executable and ready to use

​
Supported Platforms

  • macOS: Intel (amd64) and Apple Silicon (arm64)
  • Linux: x86_64 (amd64) and ARM64
  • Windows: x86_64 (amd64) and ARM64

​
What Gets Installed

The installer creates:
  • Binary: ~/.local/bin/weave
  • Config directory: ~/.weavemcp/ (created on first run)

​
Setting Up Your Shell

After installation, you may need to add ~/.local/bin to your PATH. The installer will check this and provide instructions if needed.

​
Adding to PATH

If ~/.local/bin isn’t in your PATH, add this line to your shell profile:
Add to ~/.bashrc or ~/.bash_profile:
export PATH="$HOME/.local/bin:$PATH"
After updating your shell profile, restart your terminal or run: 
source ~/.bashrc  # or your appropriate shell profile

​
First Time Setup

​
1. Login to WeaveMCP

Authenticate with the WeaveMCP control plane: 
weave login
This will:
  • Open your browser to the WeaveMCP console
  • Prompt you to sign in with GitHub or Google
  • Automatically configure your local CLI with authentication tokens

​
2. Check Your Status

Verify you’re logged in: 
weave status
You should see your authentication status and available MCP servers.

​
Configure with Claude Desktop

To use WeaveMCP with Claude Desktop, the weave CLI can automatically configure your Claude Desktop settings.

​
Automatic Configuration

After logging in, configure Claude Desktop integration: 
weave login
The login process will detect if Claude Desktop is installed and offer to configure it automatically. This adds a weave-proxy entry to your Claude Desktop configuration that connects to your managed MCP servers.

​
Manual Configuration

If you prefer manual configuration, add this to your claude_desktop_config.json:
Location: ~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "weave-proxy": {
      "command": "weave",
      "args": ["proxy"]
    }
  }
}

​
Using the Proxy

Once configured, restart Claude Desktop. Your managed MCP servers will be available as tools within Claude conversations. The weave proxy command:
  • Connects to your virtual MCP servers on the WeaveMCP platform
  • Handles authentication automatically
  • Provides a local MCP interface that Claude Desktop can connect to
  • Supports both individual and organization-shared servers

​
Development Workflow

​
For Individual Development

# Login and start using your personal MCP servers
weave login
weave status

​
For Team/Organization Development

# Login (will sync with your GitHub organizations)
weave login

# Check available servers (includes org servers you have access to)
weave status

# Proxy will automatically connect to servers you have permission to use
weave proxy

​
Configuration Files

WeaveMCP stores configuration in ~/.weavemcp/:
  • config.json - Authentication tokens and server settings
  • proxy.log - Proxy activity logs (when running weave proxy)

​
Troubleshooting

​
Installation Issues

# Install to a different directory you have write access to
mkdir -p ~/bin
curl -fsSL https://console.weavemcp.com/install.sh | bash -s -- --install-dir ~/bin
  • Check that ~/.local/bin is in your PATH
  • Try running with full path: ~/.local/bin/weave --version
  • Restart your terminal after updating PATH

​
Authentication Issues

# Check your internet connection and try again
weave login

# For corporate networks, you may need to configure proxy settings
weave login --no-browser  # Use manual authentication
  • Verify you’ve created servers in the WeaveMCP console
  • Check that you’re logged into the correct organization
  • Run weave status -v for detailed information

​
Claude Desktop Integration

  • Restart Claude Desktop after configuration changes
  • Check that the weave command is in your PATH
  • Verify Claude Desktop config file syntax is correct
  • Check proxy logs: tail -f ~/.weavemcp/proxy.log

​
Getting Help

For support:
  • Check the WeaveMCP Console for server status
  • View logs in ~/.weavemcp/proxy.log
  • Run commands with verbose output: weave status -v

​
Next Steps

After installation and login:

Web Console

Visit the console to manage your MCP servers

Create Your First Server

Set up your first virtual MCP server from the web console

Test Integration

Start a new conversation in Claude Desktop and verify your tools are available

Explore Features

Learn about organization sharing, access controls, and advanced proxy features

​
Advanced Usage

​
Local Development Mode

For local MCP server development, you can also run weave in local mode: 
# Create local configuration
mkdir -p ~/.weavemcp
cp example-local.json ~/.weavemcp/local.json

# Run in local mode (bypasses cloud, runs local MCP servers)
weave proxy --local
This is useful for testing MCP servers before deploying them to the WeaveMCP platform.

​
API Token Authentication

For CI/CD or headless environments, you can authenticate with API tokens: 
weave login --token=your-api-token
API tokens can be generated from the WeaveMCP console under your profile settings.