Chatpipe MCP

What darktw/chatpipe-mcp MCP server does

The darktw/chatpipe-mcp MCP server exposes ChatPipe page publishing through Model Context Protocol. An AI coding agent can submit a complete HTML document and receive a URL for the resulting live page. The service is intended for generated dashboards, landing pages, contact forms, project pages, documentation, demos, proposals, and similar browser-accessible content.

The server provides four operations:

• publish_page creates a page from a name, URL slug, and HTML string. Pages are public by default, or can use password access when a password is supplied.
• list_projects returns the user’s published pages, including their URLs, names, and access levels.
• update_page replaces the HTML for an existing slug and can also change its name. The existing URL stays unchanged.
• delete_page permanently removes a page identified by its slug.

How it works

The darktw/chatpipe-mcp MCP server is used as a hosted MCP service at https://api.chatpipe.net/mcp. The client sends an Authorization: Bearer header containing an API key generated in the ChatPipe account. After the MCP client is configured, an agent can call the publishing tools directly from its coding workflow.

Publishing requires a page name, a lowercase hyphenated slug, and complete HTML. The optional access value defaults to public; selecting password requires the corresponding password parameter. Updates require the existing slug and replacement HTML, with the page name being optional. Listing does not require parameters, while deletion requires only the slug.

ChatPipe states that communication uses HTTPS and that API keys are scoped to the owner’s pages. Password-protected pages are encrypted at rest. Regenerating an API key revokes the previous key.

Setup and configuration

Create a free ChatPipe account, then generate an MCP API key under Settings → API Key (MCP). The key is shown only after generation, so it must be copied at that point. The documented Claude setup registers the hosted endpoint with a bearer authorization header:

claude mcp add chatpipe --transport url https://api.chatpipe.net/mcp --header "Authorization: Bearer YOUR_API_KEY"

The placeholder must be replaced with the generated key before running the command. A manual MCP client configuration can use the same URL and authorization header. The repository does not document a local package or local process for running the server; the supplied setup connects to ChatPipe’s remote endpoint.

Tools and capabilities

The darktw/chatpipe-mcp MCP server supports publishing HTML without requiring the user to configure a deployment pipeline, hosting service, or domain. Pages can be updated in place, which is useful when an agent generates a first version and later revises its content while preserving the shared URL.

The free plan includes five projects and 30-day link expiry. Pro and Business plans provide unlimited projects and links that do not expire. The README lists password protection for Pro and Business, and email-restricted access for Business. The documented publish_page parameters directly describe public and password access; email restriction is presented as a plan feature rather than as a listed tool parameter.

Limitations and notes

This service requires a ChatPipe account and API key. Free accounts have project and expiry limits, and password protection is not included on the free plan. The HTML input must be supplied as complete content, and page management uses the chosen slug. Deleting a page is permanent. The repository describes compatibility with MCP clients generally, but the provided setup example specifically uses the Claude command-line configuration.

The darktw/chatpipe-mcp MCP server is licensed under MIT.