Setting Up Other Environments

Last updated: July 3, 2026

Beyond Cursor IDE, Claude, Claude Code, and Codex, many other environments support MCP. This page covers the general method for manually connecting WEEGLOO MCP to such environments. The location of the configuration file and how to open it differ from one environment to another, but what you put into the configuration file is the same everywhere.

Once connected, the LLM agent in that environment performs the work a person used to do in the content studio, driven by nothing more than natural-language requests. Describe what you want to build, and the agent designs a Content Type and creates Content or Media on its own.

Before You Start

You need the following to connect.

  • An environment that supports MCP: Any tool that supports registering MCP servers in a configuration file can be connected the same way. Check that environment's documentation for the location and format of the configuration file and how to open it.
  • Personal Access Token: Used for authentication. A Personal Access Token is the key your account uses to call the API with its own permissions. How to issue one is covered in Issuing a Personal Access Token.
  • Node.js 18 or later: Required to run the file-transfer server (weegloo-upload).

The MCP server address, group distinction, and the role of the weegloo-upload server are covered in MCP.

The Two Servers to Connect

WEEGLOO provides two MCP servers, and the two connect in different ways.

  • weegloo: The main server that creates, reads, updates, and deletes resources. It connects over HTTP.
  • weegloo-upload: The server that handles file-related work, such as uploading Media or deploying to Web Hosting. It runs locally as a command and uses a Personal Access Token for authentication.

Most environments let you register both servers in a single configuration file. Put both in one file.

Adding to the Configuration File

To connect by editing the configuration file directly, follow these steps.

  1. Open the MCP configuration file of the environment you want to connect. Check that environment's documentation for the file's location and format.

  2. Add the following two servers under the mcpServers entry in the configuration file.

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

  3. Change the url of the weegloo server to match your needs. If you need every tool, use https://ai.weegloo.com/mcp?group=all. The differences between groups are covered in MCP.

  4. Put the Personal Access Token you issued into the <Personal Access Token> placeholder in the AUTH_BEARER_TOKEN value of the weegloo-upload server. Because the configuration file stores the actual token as-is, take care not to expose this file publicly or push it to a shared repository.

  5. Save the configuration and restart the environment. Some environments require an action to reload the configuration.

Some environments use a different key name instead of mcpServers or use a different format. In that case, move the values from the JSON above (the server names, type, url, command, args, env) into that environment's format. The values themselves do not change from one environment to another.

Verifying the Connection

After you restart the environment, the connection is established once the tools from both servers appear in that environment's tool list.

  • weegloo: Tools for working with resources appear. Some environments require browser-based authentication the first time you connect to an HTTP server. When that happens, complete the authentication by following the on-screen prompts.
  • weegloo-upload: Tools for working with files appear.

Once connected, you can ask that environment's agent to create a Space or a Content Type.

What You Can Do

Once connected, the LLM agent can carry out the following work on its own.

  • 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

What to Do Next