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
Uselink 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
2
downloads a day
local
runs on your machine
41
downloads in 30d
What it does
MCP server for publishing and managing uselink documents from AI coding tools (Claude, Cursor, Codex).
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user uselink-mcp '--' npx -y @uselink/mcp
# 2 — ask your agent for something these tools do
# uselink_set_url_handle, uselink_list_folders, uselink_read_folder and 29 more
Uselink costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
C0All 1 server
c0x12c1 server
1 category
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 Uselink 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 uselink-mcp '--' npx -y @uselink/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
32 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.
Set the user
No parameter schema on file.
List folders in a project. Pass parent_folder_id to list children of a specific folder; omit it to list folders at the project root. Returns folders plus a parent_breadcrumb for navigation.
No parameter schema on file.
Read a single folder by id, including doc / live / draft counts.
No parameter schema on file.
Create a new folder inside a project. Omit parent_folder_id to create at the project root, or pass a folder id to nest. Slug is auto-generated from the name if omitted.
No parameter schema on file.
Update a folder
No parameter schema on file.
Re-parent a folder. Omit parent_folder_id to move the folder to the project root, or pass a folder id to nest under it.
No parameter schema on file.
Delete a folder. Documents inside the folder are NOT deleted — they are moved back to the project root.
No parameter schema on file.
List projects the active PAT can see. Workspace-scoped tokens see projects in that workspace; personal tokens see the user
No parameter schema on file.
Read a single project by id.
No parameter schema on file.
Create a new project. Workspace is inferred from the PAT — workspace-scoped tokens create inside that workspace, personal tokens create a personal project. Slug is auto-generated from the name if omitted.
No parameter schema on file.
Update a project
No parameter schema on file.
Soft-archive a project. Its documents stay accessible by direct URL but no longer appear in listings.
No parameter schema on file.
Restore a previously archived project.
No parameter schema on file.
Rename a project
No parameter schema on file.
Check whether a project slug is available in the PAT
No parameter schema on file.
Make this the user
No parameter schema on file.
Move a personal project into a workspace.
No parameter schema on file.
Remove a project from its workspace and return it to the user
No parameter schema on file.
List documents in the uselink workspace bound to the active PAT. Returns id, title, slug, status, and timestamps. Supports filtering by status and free-text search.
No parameter schema on file.
Read the full content of a uselink document by id OR slug (exactly one is required). Returns title, content, format, published status, and metadata.
No parameter schema on file.
Free-text search across documents in the workspace bound to the active PAT. Thin wrapper over uselink_list_documents with the search field set.
No parameter schema on file.
List threaded comments on a document.
No parameter schema on file.
List assets (images, files) attached to a document.
No parameter schema on file.
Move a document into a different project and/or folder. Pass project_id (required) plus an optional folder_id; omit folder_id to land at the project root.
No parameter schema on file.
Update an existing uselink document
No parameter schema on file.
Publish a uselink document. Snapshots the current draft into the published version and makes it accessible via the public URL. Returns the document with its public URL.
No parameter schema on file.
Unpublish a uselink document, removing it from public access. The draft is preserved.
No parameter schema on file.
Delete a uselink document. The document is removed and the public URL stops working.
No parameter schema on file.
Upload a single image or file from the local filesystem and attach it to a uselink document. Returns the asset with its CDN URL. Use the returned URL in your document
No parameter schema on file.
Upload a zip archive containing an HTML page and its referenced assets. The server extracts the zip, stores every asset, rewrites <img src> references to CDN URLs, and returns the rewritten HTML plus the list of assets created and skipped.
No parameter schema on file.
Post a reply to an existing comment thread on a uselink document. Replies are nested under the parent comment.
No parameter schema on file.
Mark a comment thread on a uselink document as resolved.
No parameter schema on file.
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 Uselink 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.3.0 · scanned 13 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 digestd8b583c8f50d2fbdd76376b92f01c7b518d40290d4f180e5e7f2b22e97f5ef60
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 digestd8b583c8f50d2fbd
Scanned2026-10-13
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.3.0. Pin a release below and the command asks for exactly that one.
0.3.0
undated
latestNo release note was published with this version.
—
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 Uselink 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.