Servidor MCP de Dotsy
Quais servidores do registro oficial de MCP são de Dotsy, se respondem e o que oferecem. Um programa verificou cada item; nada foi copiado da página do produto.
lido em 2026-10-23
- Nome no registroai.dotsy/mcpverificado no registro MCP
O nome no registro fica sob dotsy.ai. O registro só libera esse espaço de nomes para quem prova controle do domínio por DNS ou HTTP.
- Estadorespondeverificado em 2026-10-23
- Ferramentas98
- O servidor se chamapaige
- Versão do servidor0.3.0
- Versão do protocolo2025-06-18
Em 2026-10-23 o servidor respondeu a initialize e tools/list sem login. Primeira resposta em 532 ms.
- Ainda não avaliamos se as ferramentas fazem o trabalho do produto.
- Verificado em 2 dos 7 dias necessários para julgar a confiabilidade.
Depois de conectar
- create_site, update_brief, set_analytics_provider, update_site, publish_site alteram dados sem login: qualquer pessoa com o endereço pode chamá-las.
- As definições ocupam cerca de 36299 tokens de contexto: ative só as ferramentas de que a tarefa precisa.
- Parâmetros sem tipo ou descrição em 43 de 98 ferramentas: confira os argumentos antes de chamar.
Dito por regras a partir das medições acima. A primeira chamada provável é a escolha de um modelo na lista de ferramentas; leia a descrição antes de confiar nela.
- Nota INITE MCPdepois de uma semanaa nota precisa de 7 verificações diárias: 2 até agora
- Respondeumedindo2 das 7 verificações diárias necessárias para mostrar a porcentagem
- Mediana da primeira resposta773 ms
- Espaço no contexto do agente≈ 36.299 tokensas definições de todas as ferramentas (98), que o agente carrega a cada turno
- Definições das ferramentasA · 93 de 100
- Resultados tipados0 de 98 ferramentasdeclaram outputSchema: o resultado chega tipado e é lido de uma vez
- Parâmetros sem tipo: em 1 de 98
- Parâmetros sem descrição: em 43 de 98
Vale conferir
- Ferramentas que alteram dados, em um servidor que responde sem login: create_site, update_brief, set_analytics_provider, update_site, publish_site
Um programa verifica o servidor uma vez por dia: initialize e tools/list, sem modelo. Os tokens são o tamanho das definições, a cerca de quatro caracteres por token. A nota é a média de seis verificações do nome, da descrição, do esquema e das anotações de cada ferramenta; diz se as ferramentas estão bem descritas, não se funcionam. A nota pesa só o que foi medido: se responde (30%), se faz o trabalho do produto (25%), definições (20%), contexto (10%) e uso (15%). Uma parte não medida fica de fora, e uma instrução oculta limita a nota a 40. O estado dos servidores MCP dos fornecedores: método e números →
create_siteCreate empty site; seeds brief. Globally taken slugs auto-suffix to `{slug}-{adjective}-{noun}` (default); pass onSlugTaken:"fail" to get a 409 instead of a renamed site.
get_siteSite detail, stats, publicUrl, brief head (default-on), and readiness flags. pages[] is a ~25-entry head by default (stats.pages has the true count) — pass pages: true for the full array (capped at 1000), or enumerate everything with…
update_briefUpdate `_intent/site.md` (site brief) or a page brief when `page` is set. See field descriptions for rules, notes, and head enums.
get_analyticsRead-only traffic overview (default) or full breakdowns via include[]; optional bot id for crawler page drill-down.
set_analytics_providerConnect a third-party analytics provider (GA4, Plausible, Fathom, Umami) or remove it (provider 'none'). Dotsy adds the provider's script to the <head> of every live page — live immediately, no publish needed. Replaces any earlier…
update_siteUpdate site settings: title, keyConvention, or editingMode ('live' = each editor save publishes immediately; 'staged' = saves stay drafts until publish_site). Slug is the hostname — change it with rename_site, not this tool. Set 'staged'…
rename_siteRename the site slug (public hostname {slug}.dotsy.site). Owner-only. After success: use the returned slug in every later tool. Published site: the old slug redirects on the API (301 for reads, 308 for writes) while it stays reserved; the…
publish_sitePublish draft to live. feedback and handoff required (use dummy feedback + one-line handoff if clean).
get_draft_statusPending draft changes: content keys and routes with status. May include requiredDecision (publish_confirm) before publish_site.
discard_draftsDiscard unpublished drafts: all (omit key/keys/routes), one content key (key), or a selection (keys, routes). Destructive — check get_draft_status first.
delete_sitePermanently delete site; confirmSlug must equal slug.
bulk_put_contentStage many content keys (pages, layouts, fragments). Content only — not routes or assets. Each body ≤60KB and the whole call ≤80KB; larger pages use stage_content_chunk, dotsy push, or PUT content-raw. May queue above the inline threshold.
get_site_manifestContent keys + hashes only (optional routes=true) — static files live in list_assets, not manifest. Diff keys+hashes before apply_changeset; stage only changed bodies.
find_replaceCase-insensitive find→replace across pages in one staged commit. Batch all replacements into ONE call — never parallelize find_replace on the same key (concurrent edits surface as per-key conflict). find/replace ≤60KB.
search_contentFind pages containing a phrase (grep without reading bodies). Requires do-sqlite — graduate_site first if search_unavailable.
graduate_siteEnable site search & collections (kv → do-sqlite), one-way. Unlocks search_content, collection indexes, visitor /__paige/search, and moves any R2 form-submission ledger into SiteDb. 409 blocked covers three unrelated gates: an unsupported…
apply_changesetStage writes[] + deletes[] in one call; attach routes via writes[].route. writes[].ifMatch (hash from get_site_manifest; "" = must not exist) guards each key (a delete takes { key, ifMatch } too); atomic:true makes one stale key write…
import_site_from_urlImport URL to draft. On complete, response may include requiredDecision — preview then ask mirror vs editable before structure_*.
get_structure_statusFlat vs structured page counts; informs user — do not auto-run analyze/apply while requiredDecision pending.
structure_site_analyzePropose shared layout + fragments; persist:false first. Wait for mirror-vs-editable answer if requiredDecision pending.
decompose_analyzeDeprecated — use structure_site_analyze.
structure_site_applyRewrite flat pages to layout + fragments (draft). Do not call while requiredDecision pending — user must pick editable first. It extracts header/footer only: afterwards share_section with no arguments lists the other repeated blocks…
get_structure_resultLast structure apply job result (structuredKeys, conflicts, partial).
adapt_site_analyzePropose nav wiring + blog collectionization for an imported mirror (draft, opt-in). Read-only; returns per-adapter reports + proposalEtag. Nav decline may include nextStep (e.g. mega-menu → edit fragments/header.html). Wait for…
adapt_site_applyApply the adapt proposal (draft): wire nav into the menu store and/or rewrite the blog index to a live <dotsy-collection>. One undo covers the whole apply; a second apply is refused until adapt_site_revert (or force). Queued applies are…
adapt_site_revertAtomically restore everything the last adapt_site_apply wrote (fragments, the menu doc when the op touched it, index, member configs, routes).
get_adapt_statusRead adapt state: proposal summary + proposalEtag (+ applied/consumed flag), undo-record presence, active or queued job progress. Use to resume in a fresh session.
list_contentList content keys (HTML/md); not assets — use list_assets. Defaults to 50 keys per page — raise limit (max 1000) or pass cursor (from nextCursor) to page through the rest. Per-row `size`/`missing` are measured automatically only on pages…
get_contentRead one content key; optional selector (region) or published=true (live body). Bodies over 40KB without a selector return a truncated summary — use selector, batch_patch_content, or dotsy pull.
put_contentStage one content key. Body ≤60KB. Larger pages: stage_content_chunk + apply_changeset bodyStaging, dotsy push, or PUT content-raw. Edits to an existing large page: batch_patch_content.
stage_content_chunkAppend one ≤60KB chunk of a large new page. Omit stagingId on seq 0; pass the returned stagingId on later seq. Set finalize:true on the last chunk, then apply_changeset with writes[].bodyStaging.
patch_contentEdit one content key via ops[] (selector ops or replace-string; wrap/unwrap/move restructure siblings). Stages draft; op shapes in schema.
batch_patch_contentpatch_content on multiple keys; all-or-nothing validation. Preferred edit path for pages over 60KB. replace-string value/replace ≤60KB; whole call ≤80KB.
delete_contentDelete content key (tombstone if published). A fragments/* section that pages still place is refused with section_in_use (lists the pages) — detach it or remove it first.
rename_contentRe-key a page by slug (draft or published static). Server-side hash copy — no body round-trip. Default deletes static routes (obscure-URL); movePath:true repoints the route, rewrites menu refs and other redirects aimed at the old path…
put_postStage a blog post via structured meta+body (?format=post). Key e.g. blog/my-post.html. Declared membership: meta.collections; schedule: meta.visibleAt; SEO title override: meta.seoTitle (card always shows meta.title); custom fields…
inspect_collectionCollection state — count, server.mode, sample entries, tag (membershipKind, match=) when discovered; plus name, noun, URL pattern, layout, where it's listed, and post fields used. Pass status/q/cursor/limit (any one, even empty) for a…
list_collectionsCollections on the site — name, noun, item count (or 'not published yet'), URL pattern, and whether any member is staged. Includes a collection only a draft page lists. Returns a bare array (not wrapped in an object) — pass each row's key…
update_collectionRename a collection's display name and/or noun (e.g. the generic 'posts' key shown as 'Recipes' / 'recipe') — cosmetic only, stored separately from the tag that defines membership; doesn't need publish. Provide at least one of name/noun…
new_post_templateRead-only scaffold for a new post — suggested key/path, membership meta, blank or duplicate body. Then put_post (+ optional put_route).
get_collection_schemaRead the site's collection field definitions (`_data/collections.json`, draft view): { schema: { v: 1, collections: { "<key>": { fields[], settings? } } }, hash }. hash is null when no schema exists yet — pass it as put_collection_schema…
put_collection_schemaReplace the whole field schema (draft; publish makes it live). Read it with get_collection_schema first and send it back edited. Collection keys exactly as list_collections returns them ("blog/" or an id). Field: { key, type, label?…
infer_collection_schemaSuggest fields for one collection from a sample of its items' meta.custom values (published data, else drafts) — writes nothing. Returns { sampled, suggestions: [{ field: { key, type, options? }, count, samples, defined }], skipped }…
reindex_collectionBuild/finish collection indexes after publish returns collectionDataPending or collectionSqlPending.
preview_pageVerify-only composed HTML check; home preview may include requiredDecision — ask mirror vs editable before structure_*.
verify_pagePre-publish lint (tags, assets, layout). Pair with preview_page — see get_skill('verify').
preflight_sitePlan check before publish or large build (counts, route soft limit, seo suggestions). When ok is false, blocking lists the failed suggestion codes. Read-only.
start_edit_sessionOpen a draft session. Returns preview/edit URLs for the person (see linkGuidance). draftEditorUrl only when the site gives AI agents Full access. path defaults to '/'.
get_site_outlineSite shape: every layout and shared section (`sections`: fragments/* by name, with page count, whether the file exists and staged-change flag), whether a layout is missing, redirects count, menus grouped by where they show, and…
share_sectionMake a block that repeats on several pages one shared section, or change where one shows. No arguments: lists blocks repeated on 3+ pages. sourceKey + selector (or selectors: a sibling run, one wrapper): a dry run finds every page with…
detach_sectionGive one page its own copy of a shared section; every other page keeps the shared one. A draft — publish_site to go live. A section the layout places is hidden on that page instead (share_section name + hide).
get_routeGet one route by path (home is '/').
put_routeCreate/replace route; contentKey derived from path if omitted. On a field that accepts null (contentKey, redirectTo, redirectStatus, preserveQuery), sending null clears it back to its default.
patch_routePartial route update (only sent fields change; an OMITTED field is left alone). On a field that accepts null (contentKey, redirectTo, redirectStatus, preserveQuery), sending null CLEARS it back to its default — different from omitting it…
rename_pageChange a page's URL: moves its route from `from` to `to`. Menu links and other redirects that pointed at the old path retarget automatically; a 301 is left at the old path by default (leaveRedirect). Retry-safe (resend the same call after…
delete_routeRemove a route by path.
list_goalsList site conversion goals (pageview paths and form submits). Required before start_test.
put_goalsCreate or replace all site conversion goals (≤50). Required before start_test when no goal exists.
estimate_testEstimate days to reach promote readiness for a page (traffic baseline). Read-only.
start_testStart a same-URL A/B test (draft or live source). Rules → get_skill('verify') § A/B.
As primeiras 60 de 98, na ordem do servidor.
Como conectar
Adicione o servidor à configuração do seu cliente MCP. Claude Desktop, Cursor e a maioria dos outros clientes leem este formato:
{
"mcpServers": {
"dotsy": {
"type": "http",
"url": "https://mcp.dotsy.ai/mcp"
}
}
}Adicionar
Claude Code, no terminal
claude mcp add --transport http dotsy https://mcp.dotsy.ai/mcpAdicionar ao CursorAdicionar ao VS Code
claude.ai, ChatGPT e outros clientes: adicione https://mcp.dotsy.ai/mcp como conector personalizado nas configurações.
Especificação OpenAPI
87 rotas, lido em 2026-10-23. Abrir a especificação ↗
Cada linha é algo que um programa encontrou ao procurar: o registro, a resposta do próprio servidor, uma especificação que se lê. Linha ausente quer dizer que não encontramos, não que não exista.
Cookies
Antes de contar esta visita
A análise e a medição de anúncios nos dizem quais páginas e quais dos nossos anúncios cumprem seu papel: Google Analytics e Google Ads, o pixel da Meta, Yandex Metrica e um identificador próprio. Nada é armazenado até você responder, e recusar não muda nada no site.