Cerebrium MCP
Updated June 2026The Cerebrium MCP MCP server, built by cerebriumai, provides cerebrium ML infrastructure platform — deploy GPU workloads and custom AI models serverlessly via MCP. It is community-built and best for Cloud.
by cerebriumai
About
Cerebrium ML infrastructure platform — deploy GPU workloads and custom AI models serverlessly via MCP.
Installation
pip install cerebrium-mcpWorks With
Frequently Asked Questions
What is Cerebrium MCP?
Who built Cerebrium MCP?
Is Cerebrium MCP free?
How do I install Cerebrium MCP?
What does Cerebrium MCP integrate with?
Repo Health
Local/stdio install — runs on your machine, so there is no remote endpoint to verify live. Trust signal below is from the source repo.
Repo recency not yet available for this server.
Quick Info
- Install Type
- pip
- Author
- cerebriumai
- Categories
- 2
- Integrations
- 2
Related Servers
Memory
Knowledge graph-based persistent memory system. Store and retrieve contextual information.
Sequential Thinking
Dynamic and reflective problem-solving through thought sequences.
AWS MCP Servers
AWS Labs maintains a monorepo of specialized, open-source MCP servers that bring AWS best practices directly into AI-assisted development workflows, spanning infrastructure, data, AI/ML, cost management, and healthcare/life-sciences domains. Rather than one monolithic server, the project ships dozens of focused servers you install individually depending on the task: the AWS Documentation MCP Server for real-time official docs and API references, dedicated servers for Terraform/CDK/CloudFormation infrastructure-as-code, container and serverless platforms (ECS, EKS, Lambda), SQL/NoSQL databases (DynamoDB, RDS, Aurora), search and analytics (OpenSearch), messaging (SQS/SNS), and cost/billing analysis. Most servers install via uvx with a package name like awslabs.aws-documentation-mcp-server, run locally over stdio, and use standard AWS credential chains (IAM roles, profiles, or access keys) rather than exposing raw account credentials to the model. AWS also now offers a managed, remote "AWS MCP Server" (in preview) that combines full API coverage with pre-built agent SOPs, syntactically validated API calls, and complete CloudTrail audit logging for teams that want centralized governance instead of running servers locally. The Getting Started with Kiro/Cursor/VS Code/Claude Code sections in the repo provide one-click install configs for each server, making it straightforward to wire up only the AWS services a given project actually touches.
Cloudflare MCP Server
Cloudflare's official mcp-server-cloudflare repo ships 13+ remote, domain-specific MCP servers rather than one monolith — Documentation, Workers Bindings (storage/AI/compute primitives), Workers Builds, Observability (logs/analytics), Container sandboxes, Browser Rendering (fetch pages, convert to markdown, screenshots), Logpush health, AI Gateway (prompt/response search), Audit Logs, DNS Analytics, Digital Experience Monitoring, Cloudflare One CASB, and GraphQL analytics, each hosted at its own `*.mcp.cloudflare.com/mcp` endpoint over Streamable HTTP (SSE is deprecated but still supported). For broad, code-execution-style access across many Cloudflare products at once, Cloudflare separately publishes a Code Mode server at mcp.cloudflare.com (repo: cloudflare/mcp) — pick domain-specific servers when you want curated, typed tools for one product area (e.g. just Workers or just DNS), and Code Mode when you want fewer, more general-purpose tools. Clients without native remote-MCP support connect via `npx mcp-remote https://<subdomain>.mcp.cloudflare.com/mcp` in their config; clients like the Cloudflare AI Playground accept the URL directly. OpenAI Responses API integration is also documented, requiring a scoped Cloudflare API token per server (e.g. Browser Rendering needs specific dashboard-generated permissions). Typical use: "show me why my Worker is erroring" pulls real-time observability data, or "summarize this URL" drives the Browser Rendering server to fetch and convert a live page to markdown.
Exa MCP Server
Exa's official MCP server connects AI assistants to a search engine purpose-built for AI, using neural embeddings to match on meaning rather than keywords so agents get clean, ready-to-use content instead of a page of blue links to re-parse. The default tool set covers web_search_exa for quick topical lookups and web_search_advanced_exa for full control over domains, date ranges, and content filters, plus specialized tools for code_search (searching real-world code and GitHub), company_research (building company profiles, competitor lists, and financials), crawling/web_fetch (pulling clean content from a specific URL), people_search and linkedin_search (public professional-profile lookups), and deep_researcher_start/check for long-running multi-step research tasks backed by Exa's Research API. The server is hosted at https://mcp.exa.ai/mcp — no local process to run — and connects via one-line setup in Cursor, VS Code, Claude Code, Claude Desktop (available as a native Connector), Codex, OpenCode, Windsurf, and Antigravity, authenticated with an EXA_API_KEY from the Exa dashboard. Tool exposure is tunable per client via a ?tools= query parameter on the endpoint URL, letting teams ship narrow, purpose-built configurations (e.g. company-research-only or LinkedIn-only agents) instead of exposing the full surface, and Exa ships ready-made Claude Skills/agent definitions for common patterns like company research and people search with built-in query-variation and token-isolation guidance.
Sponsored
Better Stack
Free PlanGet alerted when your APIs, browser tests, payment pipelines, or MCP server dependencies go down. Used by 100K+ developers.
Start monitoring free →