Claude setup

When you connect the WEEGLOO MCP server to Claude, Claude can directly create, read, and update resources such as Space, Content Type, Content, and Media. What MCP is and what you need to prepare are covered in MCP. This page walks through how to connect specifically for Claude, step by step.

You connect Claude in two environments: the web version (claude.ai) and the desktop app. The differences between the two environments are as follows.

• Web version: Only the HTTP-based weegloo server is connected. All operations to create, read, and update resources are available.
• Desktop app: In addition to the weegloo server, the weegloo-upload server for handling files is also connected. To perform tasks that move files, such as uploading Media or deploying Web Hosting, you need the desktop app.

Both environments require a paid Claude plan (Pro or higher) to connect MCP servers.

Issuing the Personal Access Token needed for the connection is covered in Issue a Personal Access Token. In the configuration below, put the issued value as-is wherever it says <Personal Access Token>.

Connecting to the web version (claude.ai)

The web version connects only the HTTP-based weegloo server. The file upload server (weegloo-upload) is connected only in the desktop app, so if you need file operations, follow the desktop app guide below.

1. Log in to claude.ai, then open the Add connector screen.
2. Enter the server information. Put weegloo for the name and https://ai.weegloo.com/mcp for the server address.
3. Follow the prompts to complete login (authentication).
4. Click the tools icon in the input box. If you can see the tools from the weegloo server, the connection is established.

You can change the set of available tools by appending a ?group= value to the end of the server address. For example, to use all tools, enter https://ai.weegloo.com/mcp?group=all. The differences between groups are covered in the MCP server group table in MCP.

Connecting to the desktop app

The desktop app connects the two servers separately. The weegloo server for resource operations is connected the same HTTP way as the web version, while the weegloo-upload server for file operations is connected by running it directly on your computer.

To run the weegloo-upload server, you must have Node.js 18 or higher installed.

Connecting the weegloo server

You connect the weegloo server the same way as the web version.

1. In the desktop app's settings, open the Connectors screen.
2. Click the add connector button.
3. Put weegloo for the name and https://ai.weegloo.com/mcp for the server address.
4. Follow the prompts to complete login (authentication).

Connecting the weegloo-upload server

You register the weegloo-upload server for file operations by writing it directly into the configuration file.

1. Open the Claude desktop app's configuration file. The location by operating system is as follows.

   • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
   • Windows: %APPDATA%\Claude\claude_desktop_config.json

2. Add the following content to the file. If another server is already registered, add only the weegloo-upload entry inside mcpServers.

   {
     "mcpServers": {
       "weegloo-upload": {
         "command": "npx",
         "args": ["-y", "weegloo-upload"],
         "env": {
           "UPLOAD_API_URL": "https://upload.weegloo.com/v1",
           "AUTH_BEARER_TOKEN": "<Personal Access Token>"
         }
       }
     }
   }

3. Put the issued Personal Access Token in the value of AUTH_BEARER_TOKEN (the <Personal Access Token> slot).

4. Fully quit the Claude desktop app and reopen it. On macOS use Cmd+Q, and on Windows quit from the taskbar icon to close the app completely.

5. Click the tools icon in the input box. If you can see the tools from both the weegloo and weegloo-upload servers, the connection is established.

You can use the npx weegloo@latest installation tool to handle writing the configuration file above automatically. How to use the installation tool is covered in MCP.

When the connection fails

• npx: command not found error: Node.js is not installed, or it is not on your execution path. Install the LTS version from the official Node.js site.
• When the server is not visible on Windows: In the configuration file, change command to cmd and args to ["/c", "npx", "-y", "weegloo-upload"], then try again.
• Authentication error: Check that the Personal Access Token you put in AUTH_BEARER_TOKEN is correct and has not expired.

What to do next

• MCP: Covers the full picture of MCP connection, including the installation tool, server groups, and what you can do.
• Issue a Personal Access Token: Covers how to issue the token used for the connection.
• Migrate static pages with AI: Follow the flow of using the connected MCP to migrate an actual page into a content-based service.