Mapled

io.github.mapledhqPublished by GitHub account mapledhqv0.23.1Updated Nov 7, 2026

Headless CMS for sites built with AI: model content, import it, wire the site, verify.

VerifiedStreamable HTTPWeb executableKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

Mapled is a hosted headless CMS for AI-built sites; the assistant models and imports content, wires the site to it, and verifies the result.

What you can do
  • Model and import content into a Mapled project
  • Connect a site's code to Mapled and follow the setup guide
  • Verify the site reads published content correctly
  • Run the same operations from the shell through the CLI, including a doctor check
When to use it
Useful when a site built with an AI assistant needs editable content managed outside the code, and you want the assistant to set up the CMS connection and content model in one session.
Requirements
Remote endpoint at api.mapled.io/mcp with OAuth in the browser, or the local npm package @mapled/mcp over stdio for clients without OAuth. The stdio route needs a Mapled project token in MAPLED_MCP_TOKEN, plus Node.js for npx. A Mapled account and project are required.
Before you install
The stdio server requires a project token in MAPLED_MCP_TOKEN, which grants access to the project's content; keep it out of shared logs. The assistant can create and change content and site wiring, so review changes before publishing. Content is stored on Mapled's hosted service.

Installation

In SourceWeft

  1. Open Mapled in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.mapledhq%2Fmapled/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "mapled": {
      "type": "http",
      "url": "https://api.mapled.io/mcp"
    }
  }
}

README

Mapled for AI agents

Mapled is a hosted headless CMS for sites built with AI: the owner edits content in Mapled, the site reads published content through a small SDK, and an AI agent connects the two from a single prompt.

Connect a site

In the AI tool that has the site's code open, paste the prompt from Mapled (project → Connect with AI), or ask:

Connect this site to Mapled. Run npx -y @mapled/cli connect and follow the guide it prints.

The browser opens once to authorize; the agent does the rest. The guide for agents: https://api.mapled.io/agents.md

Claude Code plugin

bash
claude plugin marketplace add mapledhq/agent-kit
bash
claude plugin install mapled@mapled

The plugin brings the Mapled MCP server (OAuth in the browser, no token) and the mapled skill.

MCP server

Any client that supports remote MCP servers with OAuth:

https://api.mapled.io/mcp

One click: Add to Cursor · Add to VS Code · Add to VS Code Insiders

In Claude Code: claude mcp add --transport http mapled https://api.mapled.io/mcp. For clients without OAuth, the stdio server with a project token: @mapled/mcp.

Packages

Source: README.md at commit 4134653

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

4
  1. v0.23.1LatestNov 7, 2026
  2. v0.23.0Oct 29, 2026
  3. v0.22.0Oct 17, 2026
  4. v0.21.7Oct 15, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.