About Lolipop MCP Server
Lolipop MCP Server is an official remote MCP server for the Lolipop Rental Server hosting service. It lets account holders manage domains, SSL, WordPress installations, and account information through MCP clients, with PAT-based authentication.
Key features
- 01Add, list, update, and remove custom domains
- 02Manage subdomains
- 03List and request free SSL certificates
- 04List and install WordPress
- 05Retrieve account plan, server, and rate-limit information
Use cases
- 01Add a custom domain to a hosting account
- 02Request a free SSL certificate
- 03Install WordPress on a hosted site
- 04Check account and server details
MCP support
The remote MCP server exposes hosting-management tools over Streamable HTTP at https://lolipop.jp/api/v1/mcp. It authenticates with a Personal Access Token sent as a Bearer header.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://lolipop.jp/api/v1/mcpclaude mcp add --transport http pepabo-lolipop https://lolipop.jp/api/v1/mcp{"mcpServers":{"pepabo-lolipop":{"type":"http","url":"https://lolipop.jp/api/v1/mcp"}}}Open in Cursor{"servers":{"pepabo-lolipop":{"type":"http","url":"https://lolipop.jp/api/v1/mcp"}}}Open in VS Code{"mcpServers":{"pepabo-lolipop":{"type":"http","url":"https://lolipop.jp/api/v1/mcp"}}}{"mcpServers":{"pepabo-lolipop":{"serverUrl":"https://lolipop.jp/api/v1/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
https://lolipop.jp/api/v1/mcpAuth requiredTools
Details
From the project READMELolipop 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.
- Sign in to the Lolipop user panel and issue an API key (PAT). Copy the token (
lp_pat_...). - 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
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.
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}.
export LOLIPOP_PAT="lp_pat_..." # your issued token
Claude Code
claude mcp add --transport http lolipop https://lolipop.jp/api/v1/mcp \
--header "Authorization: Bearer ${LOLIPOP_PAT}"
Cursor
Add to .cursor/mcp.json. Cursor expands ${env:VAR} references, so the raw token stays in your environment, not the file:
{
"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:
{
"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:
[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:
{
"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
- For service-related inquiries: Lolipop Support
- For issues with this repository: please open a GitHub Issue
License
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.