chatpipe-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CHATPIPE_API_KEY | Yes | Your ChatPipe API key generated from chatpipe.net (Settings → API Key (MCP)). This is used in the Authorization header as a Bearer token. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| publish_pageB | Publish HTML content as a live, shareable page on ChatPipe. Returns a public URL. |
| list_projectsA | List all your published ChatPipe pages/projects with their URLs and metadata. |
| update_pageC | Update the HTML content of an existing published page. |
| delete_pageC | Delete a published page permanently. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: list_projects for viewing, publish_page for creation, update_page for modification, and delete_page for removal. There is no overlap or ambiguity between these CRUD operations.
All tool names follow a consistent verb_noun pattern (e.g., list_projects, publish_page, update_page, delete_page) with snake_case throughout. This predictability makes it easy for agents to understand and select the right tool.
With 4 tools, this server is well-scoped for managing ChatPipe pages, covering the essential CRUD operations (list, create, update, delete). Each tool earns its place without being overly sparse or bloated.
The tool set provides complete lifecycle coverage for the domain of publishing and managing HTML pages on ChatPipe, including listing, creating, updating, and deleting pages. There are no obvious gaps that would hinder agent workflows.