Platter
Give your coding agent local project powers—read and edit files, run bash, grep the repo, and execute JS—through one stdio MCP binary without wiring each tool yourself.
Overview
Platter is a MCP server for the Build phase that exposes Read, Write, Edit, Bash, Glob, Grep, and JS tools over stdio so coding agents can work on your local project tree.
What is this MCP server?
- Seven capability areas: Read, Write, Edit, Bash, Glob, Grep, and JS over stdio
- Ships as platform MCP bundles (mcpb) for linux-x64, linux-arm64, and darwin-x64
- Version 2.0.3 with published package file SHA256 checksums
- Local-first workspace manipulation for Claude Code–style agent loops
- No cloud account required—stdio transport only
- 7 named tool areas: Read, Write, Edit, Bash, Glob, Grep, JS
- Release version 2.0.3 with three published mcpb platform artifacts
What problem does it solve?
Agents stall when your MCP setup lacks reliable file, search, and shell tools, forcing you to paste code and run commands manually outside the chat.
Who is it for?
Solo developers who want a compact local MCP toolbox for day-to-day implementation and refactors with full shell power.
Skip if: Builders who need only read-only docs access, untrusted multi-tenant environments, or managed cloud sandboxes instead of host-machine bash.
What do I get? / Deliverables
After you add the Platter mcpb to your client, the agent can navigate, edit, and execute commands in the repo from a single stdio server.
- Registered stdio MCP with Read, Write, Edit, Bash, Glob, Grep, and JS
- Agent-driven local file edits and repository search
- Optional JS execution in the Platter tool surface
Recommended MCP Servers
Journey fit
Platter is core agent infrastructure while you are building: it extends the editor agent with filesystem and shell capabilities on your machine. It sits in agent-tooling because it is the MCP host surface (Read, Write, Edit, Bash, Glob, Grep, JS), not a deployed product feature.
How it compares
Local developer-tool MCP bundle, not a hosted CI runner or a domain-specific SaaS connector.
Common Questions / FAQ
Who is Platter for?
Solo builders and small teams using Claude Code, Cursor, or Codex who want one stdio MCP server for files, search, bash, and JS on their machine.
When should I use Platter?
During Build-phase agent-tooling setup when you are implementing features, fixing bugs, or exploring a repo and need consistent Read/Write/Bash/Grep tools in the agent loop.
How do I add Platter to my agent?
Download the mcpb release for your OS from the Platter GitHub releases, verify the published SHA256, and register it as a stdio MCP server in your agent client configuration.