Turns the ticket, the thread and the source into a page somebody can follow, in the words your product already uses.
Built for: The writer maintaining documentation for a product that ships faster than the docs do.
The button opens the checkout, where the 5 servers and 6 skills are listed one by one. Every member is free, so the checkout lists them and asks for no card.
The reason to buy a stack rather than five listings: each line below needs more than one member connected at the same time.
Read the Jira issue and the Confluence page behind a change and write the update from both.
Publish into Notion or Confluence, in the structure the space already uses rather than a new one.
Read the GitLab source a page is documenting and quote it accurately.
Produce the diagram, the deck and the cover image the page needs without leaving the desk.
What each part contributes, and why it was picked over the obvious alternative. Prices and permissions are read from the listings, so nothing here can disagree with the catalogue.
The issue behind the change, which is where the reason for a documentation update is usually written down first.
The space the page belongs in, read and written in place instead of pasted from a draft.
The other half of the same job for companies whose documentation lives in Notion.
The source of truth for anything technical: the code, the README and the commit that changed the behaviour being documented.
Searches and reads the specifications and decks that never became documentation, which is where most missing pages already exist in draft. It can also edit and share them unless it is signed in read-only.
One markdown convention and diagrams as code, which is what keeps a documentation set consistent across writers.
Applies plain writing rules to text people have to follow under pressure — the difference between a page that works and a page that is complete.
Keeps API terminology consistent across pages, which is where technical documentation quietly contradicts itself.
For the long-form technical paper a docs team is asked for once a quarter: structure, paragraph flow, and a reviewer's reading of it.
Produces the diagram, cover or one-page PDF a document needs, without a round trip through a design team.
The exact identity-platform term, endpoint or environment variable, for the authentication pages that are wrong in every product's documentation.
Every member is free, so the monthly figure is $0 whatever you do with the stack: nothing here is billed by the call, and only adding a paid member could change it.
| Part | What you are paying for | Monthly, as quoted |
|---|---|---|
| Jira | Free | — |
| Atlassian DC Confluence | Free | — |
| Notion | Free | — |
| GitLab | Free | — |
| Google Drive | Free | — |
| Skills | ||
| Markdown and Mermaid Writing | Free · context cost only | — |
| Write Concisely | Free · context cost only | — |
| OpenAPI Glossary | Free · context cost only | — |
| Research Paper Writing | Free · context cost only | — |
| Canvas Design | Free · context cost only | — |
| WorkOS | Free · context cost only | — |
| Everything above | $0 of servers plus $0 of skills, the same in a quiet month and a busy one | $0/mo |
Subscriptions at their monthly plan price; one-off licences spread over 12 months.
Install only these and the bill is nothing: 5 servers and 6 skills, and all 24 tools.
Nothing in this stack carries a call allowance, so nothing here can run out before the month does. The bill is decided when you install it, not when you use it.
The spend cap is one figure for the whole account, set in your dashboard and checked when an order is placed. On the call path what stops a retry loop is the plan's call allowance and its rate limit, and a refused call is never billed.
The steps below come before the install lines: what to decide and scope before connecting anything, in the order it matters. The lines themselves follow, part by part, for the client you pick.
npx mcprush@latest stack add docs-desk writes all 5 servers into Claude Code’s config in one go — or run the lines below one by one. The 6 skills are not included — add them with lines 06–11.
JIRA_HOST — Jira host domain (e.g. your-instance.atlassian.net)JIRA_API_TOKEN — Jira Personal Access Token or API tokenCONFLUENCE_HOST — Confluence host domain (e.g. your-instance.atlassian.net)CONFLUENCE_API_TOKEN — Confluence Personal Access Token or API tokenNOTION_API_TOKEN — Notion integration token (notion.so/my-integrations)GITLAB_PERSONAL_ACCESS_TOKEN — GitLab personal access token for local stdio useGOOGLE_DRIVE_OAUTH_CREDENTIALS — Path to a Google OAuth 2.0 Desktop app credentials JSON fileSet them where you start Claude Code — export JIRA_HOST=… in your shell profile on macOS and Linux, setx JIRA_HOST "…" on Windows, then open a new terminal. Claude Code reads them at start; the config keeps only the names.
# 01 · Jira
claude mcp add --scope user --env 'JIRA_HOST=${JIRA_HOST}' --env 'JIRA_API_TOKEN=${JIRA_API_TOKEN}' --transport stdio jira-mcp '--' npx -y @atlassian-dc-mcp/jira
# 02 · Atlassian DC Confluence
claude mcp add --scope user --env 'CONFLUENCE_HOST=${CONFLUENCE_HOST}' --env 'CONFLUENCE_API_TOKEN=${CONFLUENCE_API_TOKEN}' --transport stdio b1ff-atlassian-dc-confluence-mcp '--' npx -y @atlassian-dc-mcp/confluence
# 03 · Notion
claude mcp add --scope user --env 'NOTION_API_TOKEN=${NOTION_API_TOKEN}' --transport stdio notion-mcp '--' npx -y @suekou/mcp-notion-server
# 04 · GitLab
claude mcp add --scope user --env 'GITLAB_PERSONAL_ACCESS_TOKEN=${GITLAB_PERSONAL_ACCESS_TOKEN}' --transport stdio zereight-gitlab-mcp '--' npx -y @zereight/mcp-gitlab
# 05 · Google Drive
claude mcp add --scope user --env 'GOOGLE_DRIVE_OAUTH_CREDENTIALS=${GOOGLE_DRIVE_OAUTH_CREDENTIALS}' --transport stdio piotr-agier-google-drive-mcp '--' npx -y @piotr-agier/google-drive-mcp
# 06 · Markdown and Mermaid Writing
npx mcprush@latest skill add k-dense-ai/markdown-and-mermaid-writing
# 07 · Write Concisely
npx mcprush@latest skill add neolabhq/write-concisely
# 08 · OpenAPI Glossary
npx mcprush@latest skill add scalar/openapi-glossary
# 09 · Research Paper Writing
npx mcprush@latest skill add master-cai/research-paper-writing
# 10 · Canvas Design
npx mcprush@latest skill add anthropics/canvas-design
# 11 · WorkOS
npx mcprush@latest skill add workos/workosnpx).Set-ExecutionPolicy -Scope CurrentUser RemoteSigned once, or type npx.cmd instead of npx (codex.cmd, gemini.cmd, grok.cmd likewise). PowerShell 7 needs neither.Nothing is connected until you approve it in Claude Code. mcprush is not in the path and meters nothing here.
Installed together, these tool surfaces add up. It is the first thing a security reviewer asks for, so what has been counted — and what nobody has counted yet — is on the page rather than in a PDF.
| Member | Tool surface | Write tools |
|---|---|---|
| Jira | imported | 7 |
| Atlassian DC Confluence | imported | 3 |
| GitLab | not imported | not recorded |
| Google Drive | not imported | not recorded |
| Notion | not imported | not recorded |
A stack's blast radius is the union of its members, not the worst of them. That union cannot be taken here, because 3 members of 5 have no imported tool surface — so the figure a review asks for is missing rather than low, and a member marked not imported is one nobody has counted rather than one that cannot write.
1 skill in this stack instructs the agent to write — Markdown and Mermaid Writing. A skill holds no permission of its own; it can only ask a server that already has the scope, and the approval gate still applies.
A stack is a default, not a verdict. These are the substitutions the maintainer would make, and what each one costs or saves.
Teams whose issues live in Linear read the reason for a change there, and the Atlassian half of the desk disappears with it.
Written by the maintainer, kept on the page rather than in a support thread.
It cannot decide what is true. Where the code and the ticket disagree, the desk shows both and a person resolves it.
It does not own terminology on its own. The glossary skill enforces consistency once you have decided the words.
Both Atlassian members are community-maintained and not affiliated with Atlassian, which matters when your instance is on a version they have not followed.
A stack has an owner: whoever keeps it re-checks the combination when a member changes, and the members themselves are published by the people named on each row.
Tools to inspect code changes, run checks and prepare a pull request review.
Tools to prepare database changes and review their effects before rollout.
Designs the endpoint, wires the auth and the payment, and reviews the shape before it is public and permanent.