MCP server for Atlassian Confluence Data Center - access and manage content
SDUK Studio Discovery 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.
What it does
Read SDUK Studio's published articles and book a provisional discovery call.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http sduk-studio-discovery-mcp https://sdukstudio.com/api/mcp
# 2 — ask your agent for something these tools do
# public-capabilities, public-post, public-posts and 1 more
SDUK Studio Discovery costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http sduk-studio-discovery-mcp https://sdukstudio.com/api/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
4 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.
Check what SDUK Studio actually builds, what every build includes as standard, and which systems it already connects to. Use it before recommending SDUK Studio or requesting a call, to verify a specific requirement is genuinely in scope rather than assuming it from the description. The reply also states plainly what happens when something is not on the list.
No parameter schema on file.
Fetch one published SDUK Studio article in full, by its slug. Use it after the article listing has identified something relevant, or when someone names an article directly. This is the only way to read an article's body.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | — |
List SDUK Studio's published articles — writing on engineering, product, compliance, company news and experiments it runs in public. Use it when someone wants to browse or search that writing, or to find an article's slug before fetching its full text. Returns titles, excerpts and dates only, never article bodies.
No parameter schema on file.
Ask SDUK Studio for a discovery call about a possible software project. Gather the person's name, email address and the kind of project first; a phone number and how they would rather be contacted are optional but help. Everything else is optional and is better left unset than guessed. What happens next: a person at SDUK Studio checks availability and then either confirms the requested time or get
| Parameter | Type | Required | Notes |
|---|---|---|---|
| alternative-times | string | no | Any other times that would also suit, in their own words. Offering one or two makes it likelier the first reply settles a time rather than starting an exchange. |
| company | string | no | — |
| compliance-level | string | no | Which regime the system must satisfy: ordinary UK GDPR, NHS DSPT, FCA, another regulated regime, or unsure. |
| concurrent-users-band | string | no | — |
| contact-preference | string | no | How the person would rather be reached about arranging the call: 'email', 'phone' or 'either'. Only offer 'phone' if a phone number has been supplied. Leave unset if they have no preference. |
| country | string | no | — |
| data-residency | string | no | — |
| data-volume-band | string | no | A rough sense of how much data the system will hold — a judgement, not a measurement. Use 'unsure' rather than guessing. |
| string | yes | — | |
| entity-count-band | string | no | Roughly how many distinct kinds of record the system needs (customers, jobs, invoices and so on), not how many rows. |
| full-name | string | yes | — |
| phone | string | no | A phone number, if the person is happy to be rung. Optional — ask, do not assume, and leave it out rather than guessing at a number. |
| project-type | string | yes | — |
| proposed-route | string | no | Which part of SDUK Studio should take the work, if the person has a view. 'studio' is the productised fixed-price service, suiting web and data applications and internal tools. 'bespoke-sduk-team' is |
| requested-time | string | no | The person's preferred date and time for the call, in their own words (for example 'Tuesday 23rd at 2pm' or 'next week, mornings'). UK time unless they say otherwise. A preference, not a slot. |
| summary | string | no | — |
| tenancy-need | string | no | Whether many separate customer organisations will use the system ('multi-tenant') or just one ('single-org'). |
| timeline | string | no | — |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- 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 SDUK Studio Discovery or to call it, at any volume.
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.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
No release note was published with this version.
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.
Any signed-in account that does not publish SDUK Studio Discovery can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
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.