SitePerto MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| inspect_siteA | Verifica a pasta estática previamente autorizada, arquivos, tamanho e credenciais reconhecidas. Não envia arquivos nem executa comandos. |
| connection_infoA | Consulta somente o projeto vinculado à chave temporária. Não lê clientes, formulários, pagamentos ou conteúdo de outros projetos. |
| send_draftA | Envia a pasta estática autorizada como rascunho, respeitando a cota existente. Não publica, substitui ou exclui temas. A publicação é feita no painel pelo usuário. |
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 3 tools
inspect_site, connection_info, and send_draft target distinct operations: local inspection, project/key metadata lookup, and draft upload. Their boundaries are explicitly stated, with no overlapping purposes.
All names use snake_case and are readable, but the pattern is not fully uniform: inspect_site and send_draft are verb_noun, while connection_info is noun_noun. This minor deviation keeps naming mostly consistent.
Three tools are narrowly scoped to inspecting, checking connection, and sending a draft, so the count is appropriate but minimal. Each tool earns its place, though the set is slightly thin if broader operations are expected.
The surface covers the stated draft-upload workflow: inspect, verify project link, and send draft. It intentionally omits publish/update/delete because those are user-panel actions, though no draft status or listing operation is provided.