Pastea MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PASTEA_MCP_URL | No | Run against a development Pastea server by setting PASTEA_MCP_URL, e.g. http://127.0.0.1:41418/mcp |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pastea_statusA | Reports whether Pastea is reachable and connected on this Mac, and what to do if it is not. |
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 1 tool
With only one tool, there is no possibility of overlap or misselection; pastea_status has a single unambiguous purpose. Distinctness is trivially satisfied rather than earned through careful scoping.
The lone name pastea_status uses clean snake_case and is readable, but it is a noun_status form rather than a verb_noun action pattern, and a single tool provides no pattern to demonstrate consistency against.
One tool is far too thin for a server branded as 'Pastea MCP', which implies paste/content management functionality. A single connectivity probe cannot represent the apparent scope of the service.
The surface exposes only a reachability check, with no create, read, list, update, or delete operations for pastes. An agent has no way to actually do anything with Pastea, making this a severe gap for the stated purpose.