MCP

MCP (Model Context Protocol) is a standard that connects an LLM agent so it can use external tools directly. WEEGLOO provides MCP so that an LLM agent can carry out, from a plain-language request alone, the work a person used to do in the content studio. Describe what you want to build in words, and the agent finds the APIs it needs on its own, decides how to call them, and even produces working code.

This cuts down on setup work such as Content Type design and API integration, so you can focus more on your core logic and user experience.

Before you start

Connecting MCP requires three things.

• A WEEGLOO account and a Personal Access Token: used for authentication. A Personal Access Token is the key an account uses to call the API with its own permissions. How to issue one is covered in Issuing a Personal Access Token.
• An environment that supports MCP: any MCP-capable tool, such as Cursor IDE, Claude, Claude Code, or Codex, can be connected the same way.
• Node.js 18 or later: required to run the installer and the file-transfer server (weegloo-upload). This server handles file-related work such as Media uploads and Web Hosting deployments.

Connecting quickly

The installer connects everything in one go. Run the following in your terminal.

npx weegloo@latest

When it runs, it asks you in turn:

1. Choose the environment (IDE) to connect.
2. Enter your Personal Access Token.
3. Choose the MCP server group to use (see below).

The screens for each environment and the manual setup steps are covered on the respective guide pages.

• Cursor IDE setup: connect MCP to Cursor IDE.
• Claude setup: connect to the Claude desktop app.
• Claude Code setup: connect to Claude Code.
• Codex setup: connect to Codex.
• Other environment setup: connect to any other MCP-capable environment.

MCP server groups

The WEEGLOO MCP server is divided into four groups by the set of tools available. You choose one with the group value at the end of the address.

This server connects over HTTP. In a configuration file it looks like this.

{
  "mcpServers": {
    "weegloo": {
      "type": "http",
      "url": "https://ai.weegloo.com/mcp?group=all"
    }
  }
}

File upload server

File-related work, such as Media uploads and Web Hosting deployments, is handled by a separate weegloo-upload server. You run this server with the following command, and it uses a Personal Access Token for authentication.

npx -y weegloo-upload@latest

In a configuration file it looks like this. In the token slot, put the Personal Access Token you issued.

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

What you can do

Once connected through MCP, an LLM agent can perform the following work directly.

• Create, read, update, and delete resources such as Organization, Space, Content Type, Content, and Media
• Deploy a static website you have built to Web Hosting

Skills and Rules

Along with the MCP connection, the installer can also install Skills and Rules. Skills are guidance given to the agent so it performs specific tasks well, and Rules are the authoring rules to follow in a project. For details, see Skills and Rules.

What to do next

• Cursor IDE setup: follow the step-by-step connection method for each environment.
• Bringing a static page over with AI: follow the flow of moving a real page into a content-based service using the MCP you connected.