The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Lolipop MCP Server listing page.
日本語版 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.
Transport: Streamable HTTP. Authentication: Personal Access Token (PAT) via the Authorization: Bearer header.
Pricing: MCP server access is free. A valid Lolipop Rental Server contract is required.
The Lolipop MCP server authenticates with a Personal Access Token (PAT), issued from the Lolipop user panel.
lp_pat_...).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
Authorizationheader, so it is not supported at this time. Use a client that supports custom headers (Claude Code, Cursor, Gemini CLI, OpenAI Codex), or themcp-remotestdio bridge below.
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}.
Add to .cursor/mcp.json. Cursor expands ${env:VAR} references, so the raw token stays in your environment, not the file:
Add to ~/.gemini/settings.json. Gemini CLI expands $VAR / ${VAR} references from the environment:
See the Gemini CLI MCP server documentation for details.
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:
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: