Model Context Protocol server providing Taiga UI documentation search and scaffolding tools.
ODocs.co 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
One link any agent can edit: shared docs for people and AI agents, live. No login.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http odocs-co-mcp https://api.odocs.co/mcp
# 2 — ask your agent for something these tools do
# create-document, get-document, patch-document and 7 more
ODocs.co 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 odocs-co-mcp https://api.odocs.co/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.
10 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.
Creates a new ODocs.co document from a title and optional initial content, and returns its id and shareable URL. Anyone who has the URL can read and edit the document; there is no per-person access control. Documents are temporary: a document is deleted after 7 days in which nobody, person or agent, opens or edits it. A signed-in user can save a document in the cloud from the editor, up to their a
| Parameter | Type | Required | Notes |
|---|---|---|---|
| title | string | yes | Document title |
| author | string | no | Name shown on your edits and comments (e.g. "Claude via Greg"), with a robot mark as an agent. Invisible and text-direction characters are removed, line breaks and control characters become spaces, an |
| content | string | no | Initial document content (default: empty) |
Reads an ODocs.co document by ID. The default result is a readable plaintext (.txt-style) view: a metadata frontmatter (id, title, version, persistent, commentCount, openCommentCount, note) followed by the body. format:"json" returns { id, title, content, version, persistent, commentCount, openCommentCount } as an object; frontmatter:false returns just the body. version is the value patch-document
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Document ID (UUID from the doc URL) |
| includeComments | boolean | no | Include the comment threads in the result (the same threads list-comments returns). Default false. In json they are a comments array. In text format each thread wraps the text at its anchor (placement |
| format | string | no | Response format: 'text' (default) is a readable .txt-style view; 'json' is the structured object. |
| frontmatter | boolean | no | (text format only) Include the metadata frontmatter block. Default true; false returns just the body. |
Applies one or more edit operations, in order, to an existing ODocs.co document; people who have it open see each edit in real time. Returns { id, version, ok }, plus a warning when the author name was changed. Two kinds of operation: text-anchored (insert-after / insert-before / replace-text / delete-text), where the server finds the given exact text and resolves it to a position, so no character
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Document ID |
| operations | array | yes | Operations, applied in order. Text-anchored ops (insert-after / insert-before / replace-text / delete-text) name exact text that the server resolves to a position; position-based ops (insert / delete |
| author | string | no | Name shown on your edits and comments (e.g. "Claude via Greg"), with a robot mark as an agent. Invisible and text-direction characters are removed, line breaks and control characters become spaces, an |
| expectedVersion | integer | no | The document version from your last read. If the document has changed since, the patch is refused with 409 and nothing is applied (conflict detection). |
Lists an ODocs.co document's saved versions (version history) as an array of { index, timestamp, contributors } (contributors: who edited in that version, each { label, kind }: the name shown and human or agent), or an empty array when no version has been saved yet. The content of a version is returned by get-version for its index.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Document ID |
Returns the content of one saved version of an ODocs.co document, by its index in list-versions. The default result is a plaintext view (frontmatter: timestamp, title, note; then the content); format:"json" returns { timestamp, title, content }; frontmatter:false returns just the content. The note (that the text is written by anyone with the link) is the frontmatter's note field in the text view;
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Document ID |
| index | integer | yes | Version index, as listed by list-versions |
| format | string | no | Response format: 'text' (default) is a readable .txt-style view; 'json' is the structured object. |
| frontmatter | boolean | no | (text format only) Include the metadata frontmatter block. Default true; false returns just the body. |
Returns the ODocs.co integration guide as plain text: how patch positions and text anchors are matched, conflict detection with expectedVersion, document lifetime (temporary by default), error codes and rate limits. Relevant when working with an ODocs.co document link without other documentation.
No parameter schema on file.
Returns the comment threads people or agents left on an ODocs.co document. Each thread has an id, the quoted text it refers to, whether it is resolved, and its replies. The default result is a readable plaintext <comment> list after a frontmatter (id, commentCount, openCommentCount, note); format:"json" returns the structured array, which also carries contextBefore / contextAfter around the quote,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Document ID |
| includeResolved | boolean | no | Include resolved threads too (default true); false returns open threads only. |
| format | string | no | Response format: 'text' (default) is a readable .txt-style view; 'json' is the structured object. |
Opens a new comment thread on specific text in an ODocs.co document, without changing the document text. Suited to review: flagging a problem, asking a question, or suggesting a change for a person to decide on. The comment is anchored to quote (exact text from the document, matched like replace-text; occurrence selects one match when the quote appears more than once) and is shown highlighted in
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Document ID |
| quote | string | yes | Exact text in the document to comment on, matched exactly against the current text, like replace-text. |
| body | string | yes | Comment text |
| occurrence | integer | no | 0-based index of the match (the earliest match is 0); required when the quote appears more than once. It counts every match in the whole doc text, including the phrase inside longer lines; approximate |
| author | string | no | Name shown on your edits and comments (e.g. "Claude via Greg"), with a robot mark as an agent. Invisible and text-direction characters are removed, line breaks and control characters become spaces, an |
Adds a reply to an existing comment thread on an ODocs.co document, e.g. a note that the feedback was addressed. It does not open, resolve or re-open a thread. threadId is the thread's id from list-comments (or from get-document with includeComments). Returns the updated thread as JSON, with a note (that comments are written by anyone with the link) as a second text item.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Document ID |
| threadId | string | yes | Comment thread ID (a thread's id in list-comments results) |
| body | string | yes | Reply text |
| author | string | no | Name shown on your edits and comments (e.g. "Claude via Greg"), with a robot mark as an agent. Invisible and text-direction characters are removed, line breaks and control characters become spaces, an |
Marks a comment thread on an ODocs.co document resolved, or re-opens it with resolved:false. Resolved threads are not counted in openCommentCount. The optional note is recorded as a reply before the thread closes, so people can see what was done. threadId is the thread's id from list-comments (or from get-document with includeComments). Returns the updated thread as JSON, with a note (that comment
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Document ID |
| threadId | string | yes | Comment thread ID (a thread's id in list-comments results) |
| note | string | no | Optional note recorded as a reply before the thread closes, e.g. "rewrote the intro as asked" |
| author | string | no | Name shown on your edits and comments (e.g. "Claude via Greg"), with a robot mark as an agent. Invisible and text-direction characters are removed, line breaks and control characters become spaces, an |
| resolved | boolean | no | false re-opens the thread. Default true (resolve). |
- 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 ODocs.co 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.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
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.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
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. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| create-document | untrusted-inputexternal-sink | untrusted-input: keyword "download"; external-sink: declares readOnlyHint: false, openWorldHint: true |
| get-document | no tags | |
| patch-document | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| list-versions | no tags | |
| get-version | no tags | |
| get-instructions | no tags | |
| list-comments | no tags | |
| create-comment | external-sink | external-sink: keyword "create_comment", declares readOnlyHint: false, openWorldHint: true |
| reply-to-comment | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| resolve-comment | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
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.
Supply chain and provenance
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
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.1.
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 ODocs.co 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.