Vapi MCP Server
Nothing to run from here
Docstar 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.
93/100
tool-list score
15
tools declared
remote
at its publisher
—
calls last 7d
What it does
Publish your API docs so AI assistants can look up endpoints and call your API correctly.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http docstar-mcp https://mcp.docstar.io/mcp
# 2 — ask your agent for something these tools do
# search_docstar_docs, get_docstar_api_docs, call_any_api_of_docstar and 12 more
Docstar costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
SWAll 2 servers
swayammaheshwari2 servers
2 categories
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. 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.
Claude Codedeclared by this listing
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 docstar-mcp https://mcp.docstar.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: 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 pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
15 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.
Search DocStar's documentation and guides with a natural-language question, e.g. "how do I add a custom domain to my docs?" or "how does sign-in work on my MCP server?". Returns the most relevant passages with their page URLs. Use it for how-to and concept questions about DocStar. To find an API endpoint to call, use get_docstar_api_docs instead.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | What to look for, e.g. "how do I send a WhatsApp template message" |
| collectionIds | array | yes | Always send exactly these collection ids, unchanged: they are the documentation sites searched. |
Browse the DocStar API reference one level at a time, when no dedicated tool on this server does what the user needs. Call it with {} for the top level: the modules (Collections, Pages, Endpoints, Published Versions, MCP Server, FAQs, Changelogs, Webhooks, URL Mappings, ...) with a short description and the endpoints they hold. Call it with path set to a module's link to see inside it, and with
| Parameter | Type | Required | Notes |
|---|---|---|---|
| path | string | no | A link from a listing, exactly as given (e.g. "https://docs.example.com/sms/llms.txt" or ".../sms/send-sms.openapi.yml"), or just the path ("sms", "sms/send-sms.openapi.yml"). Leave it out for the top |
Send a POST, PUT, PATCH or DELETE request to any DocStar API endpoint for the signed-in user and return { status, ok, headers, data }. Use it for changes no dedicated tool covers, once you know the exact endpoint: from the quickstart-docstar skill's recipes, or looked up with get_docstar_api_docs. For GET requests use call_any_read_api_of_docstar. Never guess a URL. Pass the full url with path var
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | Full endpoint URL with path variables replaced by real values, e.g. https://api.example.com/users/42. Put query params in query, not here. |
| headers | object | yes | Request headers as name/value pairs, as the docs list them. Give the auth header (Authorization, proxy_auth_token, x-api-key, ...) an empty value "" so the signed-in user's token is filled in; never p |
| query | object | no | Query params as name/value pairs; an array sends the param once per item. Example: {"type": "flow", "bringflows": true} |
| method | string | yes | HTTP method from the endpoint's docs |
| body | object | no | JSON request body, as the endpoint's docs show it. Leave it out when the endpoint takes no body. |
Read from any DocStar API endpoint with a GET request for the signed-in user and return { status, ok, headers, data }. Use it for lookups no dedicated tool covers, once you know the exact endpoint: from the quickstart-docstar skill's recipes, or looked up with get_docstar_api_docs. Never guess a URL. Pass the full url with path variables filled in, the headers the endpoint's docs list, and query p
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | Full endpoint URL with path variables replaced by real values, e.g. https://api.example.com/users/42. Put query params in query, not here. |
| headers | object | yes | Request headers as name/value pairs, as the docs list them. Give the auth header (Authorization, proxy_auth_token, x-api-key, ...) an empty value "" so the signed-in user's token is filled in; never p |
| query | object | no | Query params as name/value pairs; an array sends the param once per item. Example: {"type": "flow", "bringflows": true} |
List the DocStar organizations (workspaces) the signed-in user belongs to, with each one's id and name (the list is at data.data). Start every DocStar task here: show the user the organizations and ask which one to use, unless there is only one. The chosen id is the orgId every other DocStar tool needs.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| itemsPerPage | string | no | Page size; the DocStar UI uses 50. e.g. 50 |
| pageNo | string | no | Page number (standard MSG91 pagination; not used by the DocStar UI, inferred). e.g. 1 |
List the collections (docs sites) in an organization, with each one's id, name, type and the caller's permission (1 read, 2 read-write). Each collection also has rootParentId: the parent pageId to use with create_page for a top-level page. Get orgId from list_organizations. Pass exclude=runCollection,environment to keep the response small. Ask the user which collection to work in.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| orgId | string | yes | The orgId path variable |
| exclude | string | no | Comma-separated list of collection columns to exclude from the response (e.g. large JSON fields). e.g. runCollection,environment |
Get a collection's MCP server: the url end users connect to, ready-to-paste snippets (a Claude Code command and a JSON config), callbackUrls for the OAuth app, the sign-in setup and any custom domain. Creates the server if it's missing and syncs its tools with the published endpoints. Call it after publishing to hand the user their MCP URL.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| orgId | string | yes | The orgId path variable |
| collectionId | string | yes | The collectionId path variable |
Creates a new documentation collection in the organization together with its invisible root page (type 0), auto-assigns collection permissions to all org users based on their roles, and auto-provisions an MCP server for it in the background. The returned rootParentId is the page id under which top-level pages are created (via Create Page). SSO read-only organizations that already have a collection
| Parameter | Type | Required | Notes |
|---|---|---|---|
| orgId | string | yes | The orgId path variable |
| name | string | no | e.g. Payments API Docs |
| slug | string | no | e.g. payments_api_docs |
| description | string | no | e.g. Public docs for the Payments API |
| type | string | no | e.g. api |
Creates a new API endpoint doc (page type 4, draft) as the last child of the given page. Requires READ_WRITE permission. Publish it afterwards with Update Endpoint State (parent page must be published). Body fields: name (string, optional) - Endpoint title shown in docs. urlName (string, optional) - URL slug; derived from name if omitted and made unique. requestType (string, optional) - HTTP meth
| Parameter | Type | Required | Notes |
|---|---|---|---|
| orgId | string | yes | The orgId path variable |
| pageId | string | yes | The pageId path variable |
| name | string | no | e.g. Create Payment |
| requestType | string | no | e.g. POST |
| URL | string | no | e.g. https://api.example.com/v1/payments/:customerId |
| description | string | no | e.g. Creates a payment for a customer |
| headers | object | no | e.g. {"Content-Type":{"checked":"true","value":"application/json","description":""}} |
| params | object | no | e.g. {"currency":{"checked":"true","value":"USD","description":"ISO currency code"}} |
| pathVariables | object | no | e.g. {"0":{"checked":"notApplicable","key":"customerId","value":"","description":"Customer id"}} |
| body | object | no | e.g. {"type":"JSON","raw":{"rawType":"JSON","value":"{\"amount\":100,\"currency\":\"USD\"}"}} |
| sampleResponse | array | no | e.g. [{"title":"Success","status":200,"description":"","data":{"id":"pay_1","status":"created"}}] |
Partially updates an API endpoint doc; send only fields to change (same fields as Create Endpoint). Any update moves a non-pending endpoint back to draft (state 1), so republish with Update Endpoint State. Requires READ_WRITE permission. Only works for type 4/5 items (otherwise 400 "Wrong Route"). Invalid fields return 400 with the validation message. Body fields: name (string, optional) - Endpoi
| Parameter | Type | Required | Notes |
|---|---|---|---|
| orgId | string | yes | The orgId path variable |
| endpointId | string | yes | The endpointId path variable |
| name | string | no | e.g. Create Payment |
| requestType | string | no | e.g. POST |
| URL | string | no | e.g. https://api.example.com/v1/payments |
| description | string | no | e.g. Creates a new payment for a customer |
| headers | object | no | e.g. {"Content-Type":{"checked":"true","value":"application/json","description":""}} |
| params | object | no | e.g. {} |
| pathVariables | object | no | e.g. {} |
| body | object | no | e.g. {"type":"JSON","raw":{"rawType":"JSON","value":"{\"amount\":100,\"currency\":\"USD\"}"}} |
| sampleResponse | array | no | e.g. [{"title":"Success","status":200,"description":"","data":{"id":"pay_1"}}] |
Creates a new page as the last child of the page given in the path. Pass the collection's rootParentId (invisible root, from List Collections) to create a top-level page (type 1, parent page/module); pass any other page id to create a subpage (type 3). The type is decided by the parent, not the body. New pages start as draft (state 1); passing state 2 publishes immediately (parent must already be
| Parameter | Type | Required | Notes |
|---|---|---|---|
| orgId | string | yes | Organization (company) ID of the current workspace |
| pageId | string | yes | 12-character id of the PARENT page (rootParentId for a top-level page) |
| name | string | no | e.g. Getting Started |
| urlName | string | no | e.g. getting-started |
| state | number | no | e.g. 1 |
| contents | string | no | e.g. content in markdown |
Publishes many pages/endpoints at once: each page in pageIds gets a new default published version and state 2 (approved/published). rootParentId (the collection's invisible root page) must also be supplied so it is marked published. Requires READ_WRITE permission. Triggers background search indexing, translation and AI SEO/meta generation, and clears the docs cache. Get ids from List Collections (
| Parameter | Type | Required | Notes |
|---|---|---|---|
| orgId | string | yes | The orgId path variable |
| collectionId | string | yes | The collectionId path variable |
| rootParentId | string | no | e.g. Xy12Ab34Cd56 |
| pageIds | array | no | e.g. ["Pg12Ab34Cd56","Pg98Zy76Xw54"] |
Returns all non-deleted pages of a collection (the full sidebar tree, flat) with id, name, urlName, type, parentId, child (ordered child ids), state, isPublished, meta, sharingMeta and the endpoint requestType for endpoint pages. Page types: 0 invisible root, 1 parent page/module (top-level), 3 subpage, 4 API endpoint, 5 example/sample request of an endpoint. States: 0 pending, 1 draft, 2 approved
| Parameter | Type | Required | Notes |
|---|---|---|---|
| orgId | string | yes | The orgId path variable |
| collectionId | string | yes | The collectionId path variable |
Sends feedback straight to the DocStar team. Use it when the user wants to report a bug, request a feature, flag wrong or missing docs, or share praise about DocStar or this MCP server. Write the message in the user's words and add any useful context, such as the tool or endpoint involved and what went wrong. Who sent it (user and organization) is taken from the signed-in user's token, never from
| Parameter | Type | Required | Notes |
|---|---|---|---|
| message | string | no | e.g. get_api_docs didn't list the MCP Server module's new endpoints |
| type | string | no | e.g. bug |
| collectionId | string | no | e.g. RoNWaspA9p3Z |
| context | object | no | e.g. {"tool":"get_docstar_mcp_api_docs"} |
Quickstart for the Docstar API: find any endpoint in the Docstar docs and call it for the signed-in user. Load this before any Docstar task. Call this to load the full instructions for this skill before doing the task.
No parameter schema on file.
Free
$0 forever
- 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 Docstar 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: —
ATool-list grade · score 93 / 100
Release 1.0.1 · scanned 28 Oct 2026
Graded from the tools this server lists, not from its source code.
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 score93
Findings0 threat · 3 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digesta1a5fbbaf5f87817037d9215c7f8eea28b9845d71547f7f39210c113b85ac777
Score vectorthreat 100 → client 93
| 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 |
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.
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.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
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 |
|---|---|---|
| search_docstar_docs | no tags | |
| get_docstar_api_docs | untrusted-input | untrusted-input: keyword "fetch" |
| call_any_api_of_docstar | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| call_any_read_api_of_docstar | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| list_organizations | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| list_collections | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_mcp_server | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| create_collection | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| create_endpoint | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| update_endpoint | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| create_page | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| publish_pages | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| list_collection_pages | no tags | |
| send_feedback_to_docstar | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| quickstart-docstar | no tags |
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.
flow-1
Untrusted input can drive an external action even though no sensitive source is exposed.
Supply chain and provenance
Integrityfirst-seen
Surface digesta1a5fbbaf5f87817
Scanned2026-10-28
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.
1.0.1
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 Docstar 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.