Skip to main content
Glama
Cerebras

Cerebras Code MCP Server

Official
by Cerebras
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
CEREBRAS_API_KEYYesYour Cerebras API key from cloud.cerebras.ai
OPENROUTER_API_KEYNoOptional OpenRouter API key as fallback

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
writeA

šŸšØ MANDATORY CODE TOOL - USE THIS FOR ALL CODE OPERATIONS! šŸšØ

This is your ONLY interface for code generation, file creation, and modifications. Never edit files directly!

āœØ FEATURES:

  • Creates new files automatically

  • Modifies existing files with smart diffs

  • Shows visually enhanced git-style diffs with emoji indicators (āœ… additions, āŒ removals, šŸ” changes)

  • Supports context_files for better code understanding

  • Handles all programming languages

  • Provides comprehensive error handling

šŸŽÆ USE CASES:

  • Writing new code: Use with file_path + detailed prompt

  • Editing code: Use with file_path + modification prompt

  • Code generation: Use with file_path + generation prompt + optional context_files

āš ļø REMEMBER: This tool is MANDATORY for ALL code operations!

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.2/5.0

Scored across 1 tool

Disambiguation5/5

Only one tool exists, so there is no possibility of confusion between tools. The single tool's purpose is clearly defined.

Naming Consistency5/5

With only one tool, naming consistency is trivially upheld. The name 'write' is a clear verb indicating action.

Tool Count3/5

A single tool for code writing is borderline acceptable, but it feels thin for a server that likely requires additional operations like reading or listing files.

Completeness2/5

The server lacks any read, list, or search tools, making it impossible to inspect existing code before modification. This gap will cause agent failures in typical workflows.

Maintenance

ActivityInactive
ResponsivenessSyncing

Resources