1. Conduid
  2. Content
  3. Reearth Cms MCP
MCP server · Content

Reearth Cms MCP

by · github.com/reearth/reearth-cms-mcp

MCP server for Re:Earth CMS

Unclaimed Apache-2.0 last commit 10 months ago mcpmcp-serverreearthgolangcontentcms
InstallView source
61Good

Scored 2 days ago · breakdown

About Reearth Cms MCP

Reearth Cms MCP is an MCP server published by reearth in the Content category: mCP server for Re:Earth CMS.

The repository has 2 stars and 0 forks, with the last commit 10 months ago. Six months or more without a commit doesn't mean the server is broken, but check the open issues before depending on it in production.

Install

From source
git clone https://github.com/reearth/reearth-cms-mcp

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Ask AI

✦

Ask AI about Reearth Cms MCP

Powered by Claude · Grounded in docs

I know everything about Reearth Cms MCP. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

  • ✓README presentThe repository ships documentation.
  • ✓License declaredUsable under a stated license.
  • !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.

3 checks have not been run yet.

Releases

v0.1.0v0.1.0 · 10 Dec 2025Full Changelog**: https://github.com/reearth/reearth-cms-mcp/commits/v0.1.0

README

Re:Earth CMS MCP Server

MCP server for Re:Earth CMS.

Usecases

Here are some useful prompts to get started:

Usecase Prompt
Add comment Add a comment "Needs review" to item XXX
Bulk update Update all items in "locations" model to set status to "published"
Copy structure Copy the "template" model and name it "new-project"
Create item Create a new item in the "events" model with title "Summer Festival" and date "2025-08-15"
Data summary Summarize the data in the "sensors" model
Explore models What models are available in project XXX?
Export data Export all items from "buildings" model as GeoJSON
List all projects Show me all projects in my workspace
Publish asset Publish asset 123 in project abc
Publish item Publish item 456 in model "articles"
Search items Find all items in the "products" model that contain "Tokyo"
Unpublish asset Unpublish asset 789 in project abc
View schema Show me the schema for the "articles" model

Features

  • Assets: Manage assets and publish/unpublish them
  • Comments: Add, update, and delete comments on items and assets
  • Export: Export items as CSV or GeoJSON
  • Groups: Create, update, and delete groups
  • Items: Create, read, update, delete, and publish items
  • Models: List models and retrieve schema definitions
  • Projects: List and manage projects in your workspace

Note that this MCP doesn't have capabilities to manage workspaces, users and model's schemas.

Installation

Docker (Recommended)

docker pull reearth/reearth-cms-mcp

Go

go install github.com/reearth/reearth-cms-mcp

Configuration

Prerequisites

This MCP server uses the Re:Earth CMS integration API, so you need the following information:

How to obtain:

  • Integration Token: Create an integration in your Re:Earth CMS workspace settings. (Documentation is not yet available)
  • Workspace ID: You can find your workspace ID in the URL when using Re:Earth CMS editor: https://cms.reearth.io/workspaces/{workspace-id}/...
claude mcp add reearth-cms -e REEARTH_CMS_TOKEN=your-api-token -e REEARTH_CMS_WORKSPACE_ID=your-workspace-id -- docker run -i --rm -e REEARTH_CMS_TOKEN -e REEARTH_CMS_WORKSPACE_ID reearth/reearth-cms-mcp

claude mcp add reearth-cms -e REEARTH_CMS_TOKEN=your-api-token -e REEARTH_CMS_WORKSPACE_ID=your-workspace-id -- reearth-cms-mcp

Add the following to your Claude Desktop config file:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json
{
  "mcpServers": {
    "reearth-cms": {
      "command": "docker",
      "args": ["run", "-i", "--rm", "-e", "REEARTH_CMS_TOKEN", "-e", "REEARTH_CMS_WORKSPACE_ID", "reearth/reearth-cms-mcp"],
      "env": {
        "REEARTH_CMS_TOKEN": "your-api-token",
        "REEARTH_CMS_WORKSPACE_ID": "your-workspace-id"
      }
    }
  }
}

{
  "mcpServers": {
    "reearth-cms": {
      "command": "reearth-cms-mcp",
      "env": {
        "REEARTH_CMS_TOKEN": "your-api-token",
        "REEARTH_CMS_WORKSPACE_ID": "your-workspace-id"
      }
    }
  }
}

Add the following to your Codex MCP configuration:

[mcp_servers.reearth-cms]
args = ["run", "-i", "--rm", "reearth/reearth-cms-mcp"]
command = "docker"

[mcp_servers.reearth-cms.env]
REEARTH_CMS_TOKEN = "you-api-token"
REEARTH_CMS_WORKSPACE_ID = "your-workspace-id"

[mcp_servers.reearth-cms]
command = "reearth-cms-mcp"

[mcp_servers.reearth-cms.env]
REEARTH_CMS_TOKEN = "you-api-token"
REEARTH_CMS_WORKSPACE_ID = "your-workspace-id"

Add the following to your Cursor MCP configuration (~/.cursor/mcp.json):

{
  "mcpServers": {
    "reearth-cms": {
      "command": "docker",
      "args": ["run", "-i", "--rm", "-e", "REEARTH_CMS_TOKEN", "-e", "REEARTH_CMS_WORKSPACE_ID", "reearth/reearth-cms-mcp"],
      "env": {
        "REEARTH_CMS_TOKEN": "your-api-token",
        "REEARTH_CMS_WORKSPACE_ID": "your-workspace-id"
      }
    }
  }
}

{
  "mcpServers": {
    "reearth-cms": {
      "command": "reearth-cms-mcp",
      "env": {
        "REEARTH_CMS_TOKEN": "your-api-token",
        "REEARTH_CMS_WORKSPACE_ID": "your-workspace-id"
      }
    }
  }
}
  1. Open Raycast Settings
  2. Go to Extensions > AI Commands > MCP Servers
  3. Click Add Server and configure:
Field Value
Name reearth-cms
Command docker
Arguments run -i --rm -e REEARTH_CMS_TOKEN -e REEARTH_CMS_WORKSPACE_ID reearth/reearth-cms-mcp
  1. Add environment variables:
Variable Value
REEARTH_CMS_TOKEN your-api-token
REEARTH_CMS_WORKSPACE_ID your-workspace-id

Or via config file (~/.config/raycast/mcp.json):

{
  "mcpServers": {
    "reearth-cms": {
      "command": "docker",
      "args": ["run", "-i", "--rm", "-e", "REEARTH_CMS_TOKEN", "-e", "REEARTH_CMS_WORKSPACE_ID", "reearth/reearth-cms-mcp"],
      "env": {
        "REEARTH_CMS_TOKEN": "your-api-token",
        "REEARTH_CMS_WORKSPACE_ID": "your-workspace-id"
      }
    }
  }
}
  1. Open Raycast Settings
  2. Go to Extensions > AI Commands > MCP Servers
  3. Click Add Server and configure:
Field Value
Name reearth-cms
Command reearth-cms-mcp
  1. Add environment variables:
Variable Value
REEARTH_CMS_TOKEN your-api-token
REEARTH_CMS_WORKSPACE_ID your-workspace-id

Alternatively, you can add the server via Raycast's config file (~/.config/raycast/mcp.json):

{
  "mcpServers": {
    "reearth-cms": {
      "command": "reearth-cms-mcp",
      "env": {
        "REEARTH_CMS_TOKEN": "your-api-token",
        "REEARTH_CMS_WORKSPACE_ID": "your-workspace-id"
      }
    }
  }
}

{
  "mcp": {
    "servers": {
      "reearth-cms": {
        "command": "docker",
        "args": ["run", "-i", "--rm", "-e", "REEARTH_CMS_TOKEN", "-e", "REEARTH_CMS_WORKSPACE_ID", "reearth/reearth-cms-mcp"],
        "env": {
          "REEARTH_CMS_TOKEN": "your-api-token",
          "REEARTH_CMS_WORKSPACE_ID": "your-workspace-id"
        }
      }
    }
  }
}

{
  "mcp": {
    "servers": {
      "reearth-cms": {
        "command": "reearth-cms-mcp",
        "env": {
          "REEARTH_CMS_TOKEN": "your-api-token",
          "REEARTH_CMS_WORKSPACE_ID": "your-workspace-id"
        }
      }
    }
  }
}

License

This project is licensed under the Apache License 2.0. See the LICENSE file for details.

README copy captured when this server was indexed; it may lag the repository. The original is authoritative.

Questions

About Reearth Cms MCP

How do I install Reearth Cms MCP?

No package has been published for this server, so install it from source: clone the repository and follow its README.

Is Reearth Cms MCP safe to use with an AI agent?

Its trust score is 61 out of 100 (good). It passes 2 of the 3 static security checks run so far; the failures are listed above. It has no ConduID identity yet, so agent calls to it are not receipted.

Is Reearth Cms MCP still maintained?

The last commit was 10 months ago. That's long enough that you should check whether the maintainer is responding to issues before depending on it.