Skip to main content

WeaveMCP Quickstart Guide

Get your first MCP server connected and making requests in 5 minutes.

What is MCP?

The Model Context Protocol (MCP) enables AI assistants like Claude to securely connect to external tools and data sources. WeaveMCP acts as a secure proxy layer, letting you centrally manage and share MCP servers across your organization. Instead of each developer maintaining their own MCP server configurations, WeaveMCP provides:
  • Virtual MCP Servers: Centralized endpoints that proxy to your actual MCP servers
  • Team Access Control: Share servers across your organization with proper permissions
  • Unified Management: One place to configure all your MCP integrations

Step 1: Authentication

Choose your preferred method to get started with WeaveMCP:
  • Web Console
  • CLI Commands

Web Console

  1. Go to console.weavemcp.com
  2. Click Sign in with GitHub or Sign in with Google
  3. Authorize WeaveMCP to access your account

Step 2: Organization Setup

  • Web Console
  • CLI Commands

Create or Join Organization

After signing in, you’ll be prompted to either:
  • Create a new organization (if you’re setting up WeaveMCP for your team)
  • Join an existing organization (if a teammate has already set up WeaveMCP)
For this quickstart, create a new organization called “My Company”.

Step 3: Create Your First Virtual MCP Server

  • Web Console
  • CLI Commands

Web Console Steps

  1. From your organization dashboard, click “Create Virtual MCP Server”
  2. Fill in the details:
    • Name: my-first-server
    • Description: My first MCP server setup
  3. Click Create Server
You’ll get a unique endpoint like: https://abc123.weavemcp.dev

Step 4: Add a Downstream MCP Server

Now add an actual MCP server that your virtual server will proxy to.
  1. Click into your newly created virtual server
  2. Click “Add Downstream Server”
  3. For this example, add a simple MCP server:
    • Name: filesystem-server
    • Type: Command
    • Command: npx @modelcontextprotocol/server-filesystem
    • Args: /path/to/your/project
Downstream servers are managed through the web console. The CLI focuses on client configuration and proxy functionality.Visit your organization dashboard to add downstream servers to your virtual MCP server.

Step 5: Configure Your MCP Client

  • Web Console
  • CLI Commands

Web Console Steps

  1. In your virtual server detail page, click “Client Configuration”
  2. Copy the configuration snippet shown
  3. Add it to your MCP client configuration:
For Claude Desktop: Add to ~/Library/Application Support/Claude/claude_desktop_config.json:
{
  "mcpServers": {
    "weavemcp": {
      "command": "weave",
      "args": ["proxy"],
      "env": {
        "WEAVEMCP_SERVER_URL": "https://abc123.weavemcp.dev"
      }
    }
  }
}

Step 6: Test Your Setup

  • Web Console
  • CLI Commands

Testing from Claude Desktop

  1. Restart Claude Desktop
  2. Start a new conversation
  3. Try an MCP request: “Can you list the files in my project directory?”
If everything is working, Claude will use your filesystem MCP server through WeaveMCP!

What’s Next?

🎉 Congratulations! You now have MCP servers running through WeaveMCP.

Need Help?