Connect

8 clients · secrets stay placeholders

JSON (mcpServers)Claude CodeCodexOpenCodeCursorVS CodeGemini CLIGoose

{
  "mcpServers": {
    "docs": {
      "type": "http",
      "url": "https://cerebrium.ai/docs/mcp"
    }
  }
}

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

[mcp_servers.docs]
url = "https://cerebrium.ai/docs/mcp"

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "docs": {
      "type": "remote",
      "url": "https://cerebrium.ai/docs/mcp",
      "enabled": true
    }
  }
}

{
  "mcpServers": {
    "docs": {
      "type": "http",
      "url": "https://cerebrium.ai/docs/mcp"
    }
  },
  "deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=docs&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vY2VyZWJyaXVtLmFpL2RvY3MvbWNwIn0%3D"
}

{
  "servers": {
    "docs": {
      "type": "http",
      "url": "https://cerebrium.ai/docs/mcp"
    }
  }
}

{
  "mcpServers": {
    "docs": {
      "httpUrl": "https://cerebrium.ai/docs/mcp"
    }
  }
}

extensions:
  "docs":
    enabled: true
    name: "docs"
    type: streamable_http
    uri: "https://cerebrium.ai/docs/mcp"
    timeout: 300

Quality 92 / 100strong

protocol88 · weight 25

pass
protocol.modernsupports 2026-07-28 (server/discover)
pass
protocol.statelessanswers without a session
pass
protocol.transportstreamable HTTP
warn
protocol.list_ttltools/list declares ttlMs 0, so clients re-fetch it on every use

authorizationn/a · weight 15

n/a
auth.prm, auth.as_metadata, auth.cimdno remote uses OAuth
n/a
auth.secret_in_urlno templated URL

tool hygiene93 · weight 30

pass
tools.descriptionsevery tool has a description
warn
tools.description_length1 tools have descriptions over 1,024 characters, which crowds the context
pass
tools.schemasevery tool has an object input schema
pass
tools.annotations3 of 3 tools declare readOnlyHint or destructiveHint
pass
tools.directory_hintsevery tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHint
pass
tools.token_costabout 1,355 tokens to load every tool
pass
tools.api_dumptools are not a one-to-one API dump

stability100 · weight 15

pass
stability.changesno tool changes in 30 days
pass
stability.rug_pullno tool changed its meaning under the same name

dependenciesn/a · weight 15

n/a
deps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI package

3 tools, about 1,355 tokens to load them all · tool set b2119a05ebd0 · checked 2026-10-19 10:52 UTC

Tool changes

No tool definition changes recorded. A server's first observation is its baseline; later probes record what changes.

Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.

Trust 93 / 100

provenance85

liveness100

freshness85

hygiene100

+repository +dns-namespace +website +reachable +uptime-100% ~updated-48d-ago

Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.

Endpoints

remote	auth	reachable	uptime 30d	p50	protocol	last ok
`https://cerebrium.ai/docs/mcp` streamable-http	none	yes	100%	677 ms	2026-07-28	2026-10-19

Tools (3)

`query_docs_filesystem_cerebrium`read-only	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_cerebrium`read-only	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_feedback`	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.

Schemas: list_tools.

Similar MCP servers

Official server.json

{
  "name": "ai.cerebrium/docs",
  "title": "Cerebrium Docs",
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
  "remotes": [
    {
      "url": "https://cerebrium.ai/docs/mcp",
      "type": "streamable-http"
    }
  ],
  "version": "0.1.1",
  "repository": {
    "url": "https://github.com/CerebriumAI/cerebrium-skills",
    "source": "github"
  },
  "websiteUrl": "https://cerebrium.ai/docs",
  "description": "Search the Cerebrium docs: deployment, cerebrium.toml, hardware, endpoints. Also sends feedback."
}