Lolipop MCP Server

io.github.pepaboPublished by GitHub account pepabov0.1.0Updated Oct 27, 2026

Official remote MCP server for Lolipop Rental Server by GMO Pepabo.

VerifiedStreamable HTTPWeb executableCloud & InfrastructureDeveloper Tools

Overview

AI-generated overview

Official remote MCP server for Lolipop Rental Server that lets an assistant manage domains, subdomains, free SSL certificates and WordPress installs.

What you can do
  • Add, list, update the public folder of, and remove custom domains
  • Add, list and remove subdomains
  • List free SSL certificates and request Let's Encrypt issuance
  • List WordPress installations and run a one-click install
  • Retrieve account information for the authenticated API key, including plan, server and rate limit
When to use it
Useful when you run sites on Lolipop Rental Server and want to handle domain, subdomain, SSL and WordPress setup through an AI assistant instead of the user panel. It is aimed at existing Lolipop customers rather than general hosting management.
Requirements
A remote endpoint at lolipop.jp over Streamable HTTP, plus a Lolipop Rental Server account on a supported plan. A Personal Access Token issued from the user panel is sent as an Authorization Bearer header; scopes such as domains, ssl and wordpress read/write are chosen at issuance. The MCP client must support custom request headers, or use a local stdio bridge via npx.
Before you install
The token grants access to your hosting account, so keep it out of committed files and shell history and store it in an environment variable. Write-scoped tokens can add, change or remove domains and subdomains, request SSL issuance and install WordPress, which changes live site configuration. Requests beyond the token's scope are rejected. The claude.ai web connector cannot pass a static header and is not supported.

Installation

In SourceWeft

  1. Open Lolipop MCP Server 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.pepabo%2Flolipop-mcp/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": {
    "lolipop": {
      "type": "http",
      "url": "https://lolipop.jp/api/v1/mcp"
    }
  }
}

README

Lolipop MCP Server

日本語版 README はこちら / Japanese README

The official remote Model Context Protocol (MCP) server for Lolipop Rental Server — a shared web hosting service operated by GMO Pepabo, Inc.

Manage domains, subdomains, free SSL certificates, and WordPress installations — all through natural language conversations with AI assistants.

Endpoint

https://lolipop.jp/api/v1/mcp

Transport: Streamable HTTP. Authentication: Personal Access Token (PAT) via the Authorization: Bearer header.

Features

  • Domain management — add, list, update (public folder), and remove custom domains
  • Subdomain management — add, list, and remove subdomains
  • SSL — list free SSL certificates and request issuance (Let's Encrypt)
  • WordPress — list installations and run a one-click install
  • Account info — retrieve the authenticated API key's account information (plan, server, rate limit)

Pricing: MCP server access is free. A valid Lolipop Rental Server contract is required.

Authentication

The Lolipop MCP server authenticates with a Personal Access Token (PAT), issued from the Lolipop user panel.

  1. Sign in to the Lolipop user panel and issue an API key (PAT). Copy the token (lp_pat_...).
  2. Register the endpoint URL together with the Authorization: Bearer <PAT> header in your MCP client (see Quick Start below).

Scopes are selected at issuance time (domains:read / domains:write / ssl:read / ssl:write / wordpress:read / wordpress:write). Requests exceeding the token's scope return 403 insufficient_scope.

Note: claude.ai (the web app's custom connectors) currently requires OAuth and cannot pass a static Authorization header, so it is not supported at this time. Use a client that supports custom headers (Claude Code, Cursor, Gemini CLI, OpenAI Codex), or the mcp-remote stdio bridge below.

Quick Start

Keep your PAT out of committed files and shell history. Store it in an environment variable (e.g. LOLIPOP_PAT) and reference it, rather than pasting the raw token into a config file or a command line. The examples below use ${LOLIPOP_PAT}.

bash
export LOLIPOP_PAT="lp_pat_..."   # your issued token

Claude Code

bash
claude mcp add --transport http lolipop https://lolipop.jp/api/v1/mcp \  --header "Authorization: Bearer ${LOLIPOP_PAT}"

Claude Code MCP docs

Cursor

Add to .cursor/mcp.json. Cursor expands ${env:VAR} references, so the raw token stays in your environment, not the file:

json
{  "mcpServers": {    "lolipop": {      "url": "https://lolipop.jp/api/v1/mcp",      "headers": {        "Authorization": "Bearer ${env:LOLIPOP_PAT}"      }    }  }}

Gemini CLI

Add to ~/.gemini/settings.json. Gemini CLI expands $VAR / ${VAR} references from the environment:

json
{  "mcpServers": {    "lolipop": {      "httpUrl": "https://lolipop.jp/api/v1/mcp",      "headers": {        "Authorization": "Bearer ${LOLIPOP_PAT}"      }    }  }}

See the Gemini CLI MCP server documentation for details.

OpenAI Codex CLI

Codex supports remote MCP servers and can read the token from an environment variable via bearer_token_env_var. Configure https://lolipop.jp/api/v1/mcp per the Codex MCP documentation:

toml
[mcp_servers.lolipop]url = "https://lolipop.jp/api/v1/mcp"bearer_token_env_var = "LOLIPOP_PAT"

Local stdio bridge (for clients without custom-header support)

Use mcp-remote to bridge a stdio-only client to the remote endpoint. Reference the token via environment variable so it does not appear in the config file:

json
{  "mcpServers": {    "lolipop": {      "command": "npx",      "args": [        "-y", "mcp-remote", "https://lolipop.jp/api/v1/mcp",        "--header", "Authorization: Bearer ${LOLIPOP_PAT}"      ]    }  }}

Documentation

Requirements

  • A Lolipop Rental Server account on a supported plan
  • A Personal Access Token (PAT) issued from the user panel
  • An MCP-compatible client that supports custom request headers (Claude Code, Cursor, Gemini CLI, OpenAI Codex CLI, etc.)

Support

License

MIT

Source: README.md at commit abf904a

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

1
  1. v0.1.0LatestSep 16, 2026

Score

85% 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