Node.js/TypeScript MCP server for Atlassian Confluence. Provides tools enabling AI systems (LLMs) to list/get spaces & pages (content
Nothing to run from here
S1000D Writer (S1000D Stack) is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
100/100
trust score
8
downloads a day
local
runs on your machine
752
downloads in 30d
What it does
Builds S1000D data modules from structured drafts, verifies them, applies only unambiguous fixes.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user s1000d-writer-s1000d-stack-mcp '--' npx -y @shuji-bonji/s1000d-writer-mcp
# 2 — ask your agent for something these tools do
# build_data_module, convert_manual, apply_fixes and 3 more
S1000D Writer (S1000D Stack) costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
SBAll 17 servers
shuji-bonji17 servers
6 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts S1000D Writer (S1000D Stack) as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user s1000d-writer-s1000d-stack-mcp '--' npx -y @shuji-bonji/s1000d-writer-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
6 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Build ONE S1000D data module (descript / proced / process / fault) or publication module (pm) from a structured draft and number it from the allocation rules. You give titles, paragraphs, steps, tables, figures and references as a tree; the server writes the XML (you never write XML, DMCs, ICNs or…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| draft | yes | — | |
| allocation | yes | — | |
| csdbDirs | no | — | |
| write | no | — | |
| overwrite | no | — | |
| allowInvalid | no | — | |
| maxFixRounds | no | — | |
| maxFixes | no | — | |
| product | no | — | |
| issuePolicy | no | — | |
| assetFormats | no | — |
Convert an experiential operation manual (@shuji-bonji/experiential-manual-model JSON) into S1000D: one publication module, one data module per topic (description → descript, procedure → proced, troubleshooting → fault, screenFlow → process plus one proced per screen), a glossary data module,…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| manual | object | no | The manual as JSON (Manual of experiential-manual-model). Alternative to manualPath. |
| manualPath | string | no | Path of a manual JSON file. Relative asset paths are resolved from its folder. |
| allocation | yes | — | |
| securityClassification | string | yes | securityClassification for every data module (the manual has none; the value is written as given, not interpreted). |
| language | no | Language of the output. Default: Manual.language ("ja" → ja-JP). A BCP 47 tag or { languageIsoCode, countryIsoCode }. | |
| topics | array | no | Topic ids to convert (default: all; the glossary is converted only when all topics are). |
| defaultApplic | no | — | |
| responsiblePartnerCompany | string | no | — |
| originator | string | no | — |
| publicationModule | boolean | no | Build the publication module too (default true). |
| assetFormats | no | — | |
| assetBaseDir | string | no | Folder the relative Asset.source.path values are resolved from (default: the folder of manualPath). |
| csdbDirs | no | — | |
| write | no | — | |
| overwrite | no | — | |
| allowInvalid | no | — | |
| includeXml | boolean | no | Include the XML of every data module in the response (default: true when write is false, false when write is true). |
| maxFixRounds | no | — | |
| maxFixes | no | — | |
| product | no | — |
Apply fixes to an existing data module. Each selection copies the location and ONE candidate of a fix that s1000d-verify-mcp suggest_fixes (or this server) returned: { location, action, target?, value? }. The server computes the fix candidates again and applies a selection only if it matches one…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| path | no | — | |
| xml | no | — | |
| csdbDirs | no | — | |
| selections | array | yes | — |
| product | no | — | |
| write | no | — | |
| overwrite | no | — | |
| allowInvalid | no | — | |
| maxFixes | no | — |
Build a comment data module (comment.xsd): a remark about data modules, publication modules, DMLs or DDNs, with the type (q / i / r), the priority code (cp01–cp99), paragraphs, the originator and the sender. The enumerations are written as given and not interpreted. The sequence number defaults to…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| refs | array | no | What the comment is about (all of one kind). Empty: noReferences. |
| commentType | string | yes | — |
| commentPriorityCode | string | yes | — |
| title | string | no | — |
| paragraphs | array | yes | simplePara texts, written as given. |
| originator | object | yes | — |
| senderIdent | string | yes | Sender enterprise code (5 characters). |
| modelIdentCode | string | yes | — |
| securityClassification | string | yes | 01–99, written as given. |
| language | yes | — | |
| yearOfDataIssue | string/integer | no | Default: this year. |
| seqNumber | string/integer | no | Default: the next free number in the CSDB. |
| responseType | string | no | rt01–rt99. Omit for no commentResponse. |
| issueDate | string | no | YYYY-MM-DD (default today). |
| brexDmRef | no | — | |
| issueType | string | no | — |
| remarks | no | — | |
| csdbDirs | no | — | |
| write | no | — | |
| overwrite | no | — |
Take the sentences that a person reads out of a data module so they can be translated: titles, paragraphs, step texts, warnings / cautions / notes, table cells and figure captions. Each segment has a stable id, its XPath, a context hint and the text, with inline elements (emphasis, references …)…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| path | no | — | |
| xml | no | — | |
| include | array | no | Which kinds of sentences to return (default: all). |
| maxSegments | integer | no | Cap on the number of segments returned. |
Put translated sentences back into the data module they were taken from. The output has the same DMC with only the language changed (issueInfo too if given). It stops with error.code "skeleton-mismatch" when the data module changed since extract_segments (skeletonHash). A segment whose id is…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| path | no | — | |
| xml | no | — | |
| csdbDirs | no | — | |
| skeletonHash | string | yes | The skeletonHash returned by extract_segments. |
| segments | array | yes | The translated sentences, by segment id. |
| language | yes | — | |
| issueInfo | no | — | |
| write | no | — | |
| overwrite | no | — | |
| allowInvalid | no | — | |
| maxFixes | no | — |
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install S1000D Writer (S1000D Stack) or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 100 / 100
Release 0.1.2 · scanned 29 Oct 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score100
Findings0 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationsource
Surface digest65a04c3229a5c3ed7148f46c34bcb54678a85fd5c363b6f5f8c02d04553bdfe6
Score vectorthreat 100 → client 100
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfacenot available
Implementation sourceread
Package metadataread
Live transportnot available
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
No tool surface was enumerated, so there is nothing to attribute a capability to.
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest65a04c3229a5c3ed
Scanned2026-10-29
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.1.2. Pin a release below and the command asks for exactly that one.
0.1.2
29 Oct 2026
latestNo release note was published with this version.
0.1.1
undated
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish S1000D Writer (S1000D Stack) can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.