Server data from the Official MCP Registry
Official remote MCP server for Lolipop Rental Server by GMO Pepabo.
About
Official remote MCP server for Lolipop Rental Server by GMO Pepabo.
Remote endpoints: streamable-http: https://lolipop.jp/api/v1/mcp
Security Report
Valid MCP server (1 strong, 1 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry. Trust signals: trusted author (3/3 approved).
Endpoint verified · Requires authentication · 1 issue found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
Permissions Required
This plugin requests these system permissions. Most are normal for its category.
What You'll Need
Set these up before or after installing:
How to Connect
Remote Plugin
No local installation needed. Your AI client connects to the remote endpoint directly.
Add this to your MCP configuration to connect:
{
"mcpServers": {
"io-github-pepabo-lolipop-mcp": {
"url": "https://lolipop.jp/api/v1/mcp"
}
}
}Documentation
View on GitHubFrom the project's GitHub 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.
- 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
Reviews
No reviews yet
Be the first to review this server!
More Developer Tools MCP Servers
Git
Freeby Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
Fetch
Freeby Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
Toleno
Freeby Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
mcp-creator-python
Freeby mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.
MCP Marketplace
Freeby mcp-marketplace · Developer Tools
Search and install MCP servers from inside your AI client.
MarkItDown
Freeby Microsoft · Content & Media
Convert files (PDF, Word, Excel, images, audio) to Markdown for LLM consumption
