2026-02-27 17:05:05 +00:00
|
|
|
name: docmost
|
|
|
|
|
version: "1.0.0"
|
|
|
|
|
description: Docmost MCP server for wiki/documentation page management and search
|
|
|
|
|
dockerImage: "mysources.co.uk/michal/docmost-mcp:latest"
|
|
|
|
|
transport: STDIO
|
|
|
|
|
repositoryUrl: https://github.com/MrMartiniMo/docmost-mcp
|
fix(templates): make the shipped templates match reality
The templates are what `create server --from-template` builds from and what
mcpd seeds on start, so drift there ships broken servers. Nothing ever read
these files in a test, and they had rotted badly.
- grafana: GRAFANA_URL now defaults to the in-cluster ClusterIP and the
description spells out why the public hostname is wrong — reaching a
co-located Grafana over its ingress hairpins through the per-host Envoy L7
policy, which drops the caller's identity and returns a bare `Access denied`
403 with a perfectly valid token. That cost a day of looking at the token.
- unifi-network: was wrong on every field that mattered. `runtime: python`
for an npm package, an env contract (UNIFI_HOST/USERNAME/PASSWORD) the
package doesn't read, and no probe. Now UNIFI_TARGETS with the
classic-vs-unifi_os distinction and the :8443 egress caveat written down.
- docmost, gitea: both carried "health check disabled" comments citing a
limitation of the old docker-exec probe, which readiness-via-proxy removed.
Both probes verified against the live servers. gitea uses search_repos, not
get_me, because get_me needs a `read:user` scope a repo-scoped token lacks.
- filesystem: packageName was `@anthropic/filesystem-mcp`, which 404s on npm —
the template could never have installed. Points at the real package.
- terraform: deleted. `@anthropic/terraform-mcp` 404s too and there is no
npm-published replacement to point it at.
- node-red: deleted, the service is gone.
Two supporting fixes:
- The seeder declared no `runtime` field and never wrote the column, so a
template asking for the python runner silently seeded as null and got node.
- A new templates test reads every shipped file: schema-valid, a runner the
orchestrator knows, some way to actually start, unique env names, and a
readiness probe (without one an instance can only ever report `live`).
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0114dg56YmVacyqhp5fitcTb
2026-08-09 23:53:22 +01:00
|
|
|
healthCheck:
|
|
|
|
|
# get_workspace calls the Docmost API, so a pass proves URL + login. The old
|
|
|
|
|
# "probe requires packageName" caveat here was true of the long-gone
|
|
|
|
|
# docker-exec probe; readiness now goes through the MCP proxy, which works
|
|
|
|
|
# the same for image-based STDIO servers. Verified against the live server.
|
|
|
|
|
tool: get_workspace
|
|
|
|
|
arguments: {}
|
|
|
|
|
intervalSeconds: 60
|
|
|
|
|
timeoutSeconds: 10
|
2026-02-27 17:05:05 +00:00
|
|
|
env:
|
|
|
|
|
- name: DOCMOST_API_URL
|
|
|
|
|
description: Docmost API URL (e.g. http://100.88.157.6:3000/api)
|
|
|
|
|
required: true
|
|
|
|
|
- name: DOCMOST_EMAIL
|
|
|
|
|
description: Docmost user email for authentication
|
|
|
|
|
required: true
|
|
|
|
|
- name: DOCMOST_PASSWORD
|
|
|
|
|
description: Docmost user password for authentication
|
|
|
|
|
required: true
|