# MCP

MCP (Model Context Protocol) is a standard that connects an LLM agent to external tools so that the agent can use those 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. How to connect it to an agent is covered in [Connecting](/ai/tools/connect.md). This page covers how the MCP server you connect is composed.

## MCP server groups {#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.

| Group | Tools included | Address |
|---|---|---|
| `default` | Default tool set | `https://ai.weegloo.com/mcp` |
| `core` | Default tools (excluding Web Hosting and tokens) | `https://ai.weegloo.com/mcp?group=core` |
| `extra` | Usage, Webhook, Tag, and limit tools | `https://ai.weegloo.com/mcp?group=extra` |
| `all` | All tools | `https://ai.weegloo.com/mcp?group=all` |

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

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

## File upload server {#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.

```json
{
  "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 {#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 {#skills-and-rules}

Along with the MCP server, the install tool also installs Skills and Rules. Skills are guidance given to the agent so it performs specific tasks well, and Rules are the rules to follow throughout your work. For details, see [Skills and Rules](/ai/tools/skill-rules.md).

## What to do next {#what-to-do-next}

- [Connecting](/ai/tools/connect.md): Covers how to install the MCP server, Skills, and Rules for each environment (agent).
- [Skills and Rules](/ai/tools/skill-rules.md): Covers what the Skills and Rules that the install tool sets up alongside it are.
- [Keeping up to date](/ai/tools/skill-rules.md#keeping-up-to-date): Covers how to keep the Skills and Rules you installed up to date.
- [Migrating a Static Page with AI](/getting-started/quick-start/intro-7/intro-7-1.md): Follow the flow of moving a real page into a content-based service with the MCP you connected.