MCP.Market

Cerebrium Docs MCP server

online · 100% uptime
by cerebrium.ai·ai.cerebrium/docs·v0.1.1
No reviews yet

Search the Cerebrium docs: deployment, cerebrium.toml, hardware, endpoints. Also sends feedback.

B75/100grade B
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
B75/100

full report

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed Cerebrium Docs yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Cerebrium Docs tools (3, 2 write)

write = sends, deletes, buys or posts
  • query_docs_filesystem_cerebriumwrite actionFree

    Run a read-only shell-like query against a virtualized, in-memory filesystem rooted at `/` that contains ONLY the Cerebrium documentation pages and OpenAPI specs. This is NOT a shell on any real machine — nothing runs on the user's computer, the server host, or any network. The filesystem is a sandbox backed by documentation chunks. This is how you read documentation pages: there is no separate "get page" tool. To read a page, pass its `.mdx` path to `head` or `cat` — a page at the URL path `/some/page` lives at `/some/page.mdx`. To search the docs with exact keyword or regex matches, use `rg`. To understand the docs structure, use `tree` or `ls`. **Paths are specific to this site — never guess them.** Discover real paths with `tree / -L 2`, `ls /`, or the search tool before reading. If a path does not exist, that only means the guess was wrong; it does NOT mean the topic is undocumented — use `rg -il "keyword" /` to find where it is covered. **Workflow:** Start with the search tool for broad or conceptual queries like "how to authenticate" or "rate limiting". Use this tool when you need exact keyword/regex matching, structural exploration, or to read the full content of a specific page by path. Supported commands: rg (ripgrep), grep, find, tree, ls, cat, head, tail, stat, wc, sort, uniq, cut, sed, awk, jq, plus basic text utilities. No writes, no network, no process control. Run `--help` on any command for usage. Each call is STATELESS: the working directory always resets to `/` and no shell variables, aliases, or history carry over between calls. If you need to operate in a subdirectory, chain commands in one call with `&&` or pass absolute paths (e.g., `cd /some-directory && ls` or `ls /some-directory`). Do NOT assume that `cd` in one call affects the next call. Examples (replace the placeholder paths with real ones from `tree` or search): - `tree / -L 2` — see the top-level directory layout - `rg -il "rate limit" /` — find all files mentioning "rate limit" - `rg -C 3 "apiKey" /some-directory/` — show matches with 3 lines of context around each hit - `head -80 /some/page.mdx` — read the top 80 lines of a specific page - `head -80 /page-one.mdx /page-two.mdx /section/page-three.mdx` — read multiple pages in one call - `cat /some/page.mdx` — read a full page when you need everything - `cat '/openapi/https://s3.eu-west-1.amazonaws.com/www.cerebrium.ai/openapi_spec.json' | jq '.paths | keys'` — list OpenAPI endpoints OpenAPI specs for this site are mounted at: `'/openapi/https://s3.eu-west-1.amazonaws.com/www.cerebrium.ai/openapi_spec.json'`, `/openapi/package.json`, `/openapi/data/training-dataset-example.json`. Use them to answer questions about endpoints, request/response schemas, parameters, and authentication. Output is truncated to 30KB per call. Prefer targeted `rg -C` or `head -N` over broad `cat` on large files. To read only the relevant sections of a large file, use `rg -C 3 "pattern" /path/file.mdx`. Batch multiple file reads into a single `head` or `cat` call whenever possible. When referencing pages in your response to the user, convert filesystem paths to URL paths by removing the `.mdx` extension. For example, `/some/page.mdx` becomes `/some/page`.

  • search_cerebriumFree

    Search across the Cerebrium knowledge base to find relevant information, code examples, API references, and guides. Use this tool when you need to answer questions about Cerebrium, find specific documentation, understand how features work, or locate implementation details. The search returns contextual content with titles and direct links to the documentation pages. If you need the full content of a specific page, use the query_docs_filesystem tool to `head` or `cat` the page path (append `.mdx` to the path returned from search — e.g. a result at `/some/page` is read with `head -200 /some/page.mdx`).

  • submit_feedbackwrite actionFree

    Report a problem with this documentation site so the docs team can fix it. Use when a documentation page is incorrect, outdated, confusing, incomplete, or has a broken example. This is for feedback about the documentation content itself — not for product support requests or feedback about this tool or assistant.

Public scan report

scanner v0.1.10 · 2026-10-29 · same rubric, same numbers if you re-run it

1 high1 low
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 1540ms20/20
  • Tool poisoning3 tool descriptions checked13/15
  • Auth qualityopen endpoint exposes 2 write-action tools with no auth3/15
  • Maintenancelast push 55 days ago12/15
  • Maintainer identitynamespace and repository owner differ; GitHub account older than a year; website matches verified namespace8/10

Findings (2)

  • highWrite-action tools reachable without authenticationauth.open-write
  • lowUnusually long tool description (over 2,000 characters)poison.long-description
    tool query_docs_filesystem_cerebrium: …Run a read-only shell-like query against a virtualized, in-memory filesystem rooted at `/` that contains ONLY the Cerebrium documentation pages and OpenAPI specs. This is NOT a shell on any real machine — nothing runs on the user's computer, the server host, or any network. The filesystem is a sandbox backed by documentation chunks. This is how you read documentation pages: there is no separate "get page" tool. To read a page, pass its `.mdx` path to `head` or `cat` — a page at the URL path `/some/page` lives at `/some/page.mdx`. To search the docs with exact keyword or regex matches, use `rg`. To understand the docs structure, use `tree` or `ls`. **Paths are specific to this site — never guess them.** Discover real paths with `tree / -L 2`, `ls /`, or the search tool before reading. If a path does not exist, that only means the guess was wrong; it does NOT mean the topic is undocumented — use `rg -il "keyword" /` to find where it is covered. **Workflow:** Start with the search tool for broad or conceptual queries like "how to authenticate" or "rate limiting". Use this tool when you need exact keyword/regex matching, structural exploration, or to read the full content of a specific page by path. Supported commands: rg (ripgrep), grep, find, tree, ls, cat, head, tail, stat, wc, sort, uniq, cut, sed, awk, jq, plus basic text utilities. No writes, no network, no process control. Run `--help` on any command for usage. Each call is STATELESS: the working directory always resets to `/` and no shell variables, aliases, or history carry over between calls. If you need to operate in a subdirectory, chain commands in one call with `&&` or pass absolute paths (e.g., `cd /some-directory && ls` or `ls /some-directory`). Do NOT assume that `cd` in one call affects the next call. Examples (replace the placeholder paths with real ones from `tree` or search): - `tree / -L 2` — see the top-level directory layout - `rg -il "rate limit" /` — find all files mentioning "rate limit" - `rg -C 3 "apiKey" /some-directory/` — show matches with 3 lines of context around each hit - `head -80 /some/page.mdx` — read the top 80 lines of a specific page - `head -80 /page-one.mdx /page-two.mdx /section/page-three.mdx` — read multiple pages in one call - `cat /some/page.mdx` — read a full page when you need everything - `cat '/openapi/https://s3.eu-west-1.amazonaws.com/www.cerebrium.ai/openapi_spec.json' | jq '.paths | keys'` — list OpenAPI endpoints OpenAPI specs for this site are mounted at: `'/openapi/https://s3.eu-west-1.amazonaws.com/www.cerebrium.ai/openapi_spec.json'`, `/openapi/package.json`, `/openapi/data/training-dataset-example.json`. Use them to answer questions about endpoints, request/response schemas, parameters, and authentication. Output is truncated to 30KB per call. Prefer targeted `rg -C` or `head -N` over broad `cat` on large files. To read only the relevant sections of a large file, use `rg -C 3 "pattern" /path/file.mdx`. Batch multiple file reads into a single `head` or `cat` call whenever possible. When referencing pages in your response to the user, convert filesystem paths to URL paths by removing the `.mdx` extension. For example, `/some/page.mdx` becomes `/some/page`.…
Overall 75/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Cerebrium Docs compares

Against every graded Productivity MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
75/100
higher than 40% of 1,301 Productivity servers
Tools
3
the typical Productivity server has 7
Tools that change things
67%
typical: 0%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote Productivity server answers 100%
Response time
293 ms
faster than 55% of 656 Productivity servers

What its tools let an agent do: 1 read · 2 change

Install Cerebrium Docs in Claude Code, Cursor or VS Code

claude mcp add --transport http docs https://cerebrium.ai/docs/mcp
Add to Cursor

What the publisher says

From the Cerebrium Docs repository's README, as published. We do not edit it. Read it on GitHub

Cerebrium agent skills

Official Agent Skills and hosted docs MCP for Cerebrium, the serverless GPU and CPU platform for real-time AI workloads. The skills teach a coding agent to write a valid cerebrium.toml, pick hardware and a region, deploy, call the endpoint, and debug the result without leaving the terminal. The MCP gives it live search over the documentation.

Works with Claude Code, Codex, Cursor, GitHub Copilot, Windsurf, Cline and anything else that reads the Agent Skills format.

Install

Any agent (installs the skills into every detected harness):

npx skills add CerebriumAI/cerebrium-skills -g -y
npx add-mcp https://cerebrium.ai/docs/mcp -n cerebrium-docs -g -y

Claude Code (one plugin bundles the skills and the docs MCP):

/plugin marketplace add CerebriumAI/cerebrium-skills
/plugin install cerebrium@cerebrium

Codex:

codex plugin marketplace add CerebriumAI/cerebrium-skills

Gemini CLI (one extension bundles the skills and the docs MCP):

gemini extensions install https://github.com/CerebriumAI/cerebrium-skills

Cursor loads the repository directly as an Agent Plugin: the root plugin.json and mcp.json are the open-standard manifests, so no Cursor-specific install step is needed.

Or agent-driven: paste this into the agent of your choice.

Install the Cerebrium agent toolkit following instructions from
github.com/CerebriumAI/cerebrium-skills: use `npx skills add` and `npx add-mcp`,
global and auto-confirmed for all agents (-g -y).

Then create an account and authenticate the CLI once:

# create an account at https://dashboard.cerebrium.ai (also where API keys are created)
pip install cerebrium   # or: brew tap cerebriumai/tap && brew install cerebrium
cerebrium login

Compute is billed per second: see pricing for current rates and any starting credit.

In CI, skip login and set CEREBRIUMSERVICEACCOUNT_TOKEN instead.

What is in here

One skill, structured for progressive disclosure: agents load the ~120-line core (skills/cerebrium/SKILL.md, the workflow, the safety rules, the endpoint shapes) when a Cerebrium task appears, and pull in a reference file only when the task needs it.

The docs MCP (hosted at https://cerebrium.ai/docs/mcp) searches and reads the published documentation, and accepts documentation feedback: searchcerebrium, querydocsfilesystemcerebrium, and submit_feedback. No account access, no key needed. It is declared twice on purpose, because the two formats are not interchangeable: .mcp.json is the Claude Code convention, and mcp.json at the repository root is the path the Agent Plugins standard requires, with that standard's streamable-http transport name.

The plugin metadata is likewise declared per host: .claude-plugin/ for Claude Code, .agents/plugins/ for Codex, root plugin.json for Agent Plugins clients such as Cursor, and gemini-extension.json for the Gemini CLI. server.json is the MCP registry entry.

Try it

  • "Deploy this FastAPI app to Cerebrium on an H100 with auth enabled, then follow the logs."
  • "My Cerebrium app queues requests under load. Work out why and fix the config."
  • "Which GPU and region fit a 13B vLLM model on Cerebrium, and what should the cerebrium.toml be?"

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Cerebrium Docs: common questions

Is Cerebrium Docs MCP server safe?
Mostly: it is graded B (75/100). Read the Cerebrium Docs safety report
How do I install Cerebrium Docs?
It runs remotely at cerebrium.ai. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Cerebrium Docs need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Cerebrium Docs maintained?
The last commit was 62 days ago (2026-09-04). The latest release is v0.1.1.
Is Cerebrium Docs up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
What can I use instead of Cerebrium Docs?
Servers from other publishers that do the same job: AI Agents API Library MCP server, Unifi Applications MCP server and Context7 MCP server.
How does Cerebrium Docs compare with other Productivity MCP servers?
safety score 75/100 (higher than 40% of 1,301 Productivity servers); tools 3 (the typical Productivity server has 7); tools that change things 67% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Cerebrium Docs

Same job from other publishers: the closest match first, then the best rated.

  • AI Agents API Library
    Find APIs and MCP servers for AI agents: auth, free tier, MCP endpoint, docs, last-checked date.
    B
  • Unifi Applications
    Queryable UniFi API docs: endpoint search, schemas, code examples. No controller access.
    A
  • Context7
    Up-to-date docs for AI agents
    A
  • Svelte MCP
    The official Svelte MCP server providing docs and autofixing tools for Svelte development
    A
  • SvGrid
    Checks AI-written SvGrid code against the real API, plus version-pinned Svelte 5 grid docs.
    A