Lolipop MCP Server

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 theAuthorization: Bearerheader.

- 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.

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

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

Note:claude.ai (the web app's custom connectors) currently requires OAuth and cannot pass a staticAuthorizationheader, 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}.

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

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

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}" } } } }

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}" } } } }

Publish complete websites directly from any AI client via API — no hosting setup, CMS, or configuration required.

Interact with and manage your Ghost CMS blog, including posts, users, and members, through an LLM interface.

Manage WordPress sites, plugins, and themes on the Rocket.net hosting platform via its API.

Manage your SiteBay WordPress hosting platform. Handle sites, execute server commands, and manage staging environments via natural language.

An MCP server for interacting with WordPress sites via the REST API, allowing you to manage posts, pages, and media.

An MCP server for WordPress plugin audits

Manage and utilize website content within the DevHub CMS platform

A free WordPress plugin that turns your site into a governed MCP server: 153 abilities that are all off until you switch them on, bound to a least-privilege WordPress user, with every call audited.

Connects Claude to WordPress sites to create posts and manage sites using the WordPress REST API.