mcp

The Weaverse MCP Server enables you to search the Weaverse documentation via the MCP (Model Context Protocol) interface. It exposes a tool named search_weaverse_docs which can be invoked by compatible MCP clients (such as Cursor or Claude Desktop) to query Weaverse documentation and retrieve relevant results. To connect, configure your MCP client to point at the weaverse-mcp server entry and call the search_weaverse_docs tool with your query. The server is designed to be lightweight and focuses on enabling fast, context-aware access to Weaverse documentation through the standard MCP tooling.

With a Cursor or Claude Desktop setup, you typically provide the following configuration to your client so it can route queries to the server: the mcpServers mapping including the server name, command, and arguments. Once configured, you can issue natural language queries like “show me how to search Weaverse docs” and the tool will return concise results from the documentation corpus, enabling you to navigate topics, sections, and examples efficiently.

Prerequisites:

• Node.js (recommended: current LTS) and npm or npx available on your system
• Internet access to fetch the MCP package from npm

Step-by-step installation:

# Quick start (uses npx as described in the project)
npx -y @weaverse/mcp@latest

If you prefer a more persistent installation (optional, not required for running via npx):

# Install the MCP package globally (alternative approach)
npm install -g @weaverse/mcp

# Start the server (when installed globally, you can run the command directly)
weaverse-mcp

Note: The repository README demonstrates starting the server via npx as the primary method. The above alternative shows a global install path if you prefer a persistent executable.

Configuration and usage tips:

• The MCP server exposes a single tool: search_weaverse_docs. Use this tool to query Weaverse documentation.
• The canonical starting command is the npx form shown in the README: npx -y @weaverse/mcp@latest
• If you plan to integrate with Cursor or Claude Desktop, ensure your client’s mcpServers configuration mirrors the example so the client can route queries to this server.
• Environment variables are not strictly required for basic operation, but you can extend configuration to set any needed environment-specific overrides (e.g., API endpoints or authentication tokens) by adding an env block to the mcp config if your deployment environment requires it.
• If you experience transient network issues, re-running the npx command to fetch the latest package can help ensure you’re using the most up-to-date server.