Node.js/TypeScript MCP server for Atlassian Confluence. Provides tools enabling AI systems (LLMs) to list/get spaces & pages (content
DeployIt Product Expert 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
AI product expert answering from live source code, with sources and a verification status.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http deployit-product-expert-mcp https://mcp.deployit.ai/demo
# 2 — ask your agent for something these tools do
# server_info, get_recent_changes, ask_product_expert
DeployIt Product Expert 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 deployit-product-expert-mcp https://mcp.deployit.ai/demoReconnect, 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.
3 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.
Describe this MCP server: which product it answers for, which repositories back it, and how fresh the underlying code index is. Instant (no AI). Call it once at the start of a session to confirm you are talking to the right product — if the index is stale or still building, say so instead of trusting deep answers.
No parameter schema on file.
Instant list of recent changes to "deployit" — the semantic changelog derived from its commits. No AI processing: responds in under a second, costs nothing, and never counts against any quota. Use this FIRST for "what changed", "what's new", "since when" questions; escalate to ask_product_expert only when you need an investigated answer.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| days | number | no | How many days back (default 14, max 90). |
Ask a question about "deployit" and get an answer verified against its live source code and git history. Use it for anything about product behavior, features, settings, limits, error messages, or recent changes. HOW IT WORKS AND HOW LONG IT TAKES: the expert genuinely investigates — it searches and reads the product's real source code before answering. A fresh investigation takes 20-60 SECONDS. D
| Parameter | Type | Required | Notes |
|---|---|---|---|
| question | string | yes | The question about the product, as specific as possible. Identical wording hits the cache — when retrying after a timeout, repeat the question verbatim. |
| context | string | no | Optional context from your own conversation with the end user (symptoms, plan, what they tried…). Makes the answer more targeted, but context-carrying questions are never cached — omit it for generic |
| depth | string | no | quick (default): up to ~1 minute of investigation, right for support questions. thorough: digs much deeper for hard questions — expect the timeout-then-retry-from-cache flow. |
- 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 DeployIt Product Expert 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 DeployIt Product Expert 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.