Skip to main content
Glama
davidweatherall

Cerebras Code MCP Server

by davidweatherall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
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 a fallback provider

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

A3.9/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of confusion between tools. The tool's purpose is clearly defined as the sole interface for code operations.

Naming Consistency5/5

The single tool named 'write' follows a simple verb convention. With only one tool, there are no inconsistencies to assess.

Tool Count2/5

A server dedicated to code operations with only one tool is too few. The scope of the server suggests the need for additional tools like reading, searching, or deleting code, making this count insufficient.

Completeness2/5

The tool only handles writing and modifying files. It lacks essential operations like reading, deleting, or listing code, resulting in significant gaps for a code-focused server.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources