@workspacejson/codex-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WORKSPACE_JSON_PATH | No | Optional: point at a specific file or search root. |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| workspace_get_file_contextA | Return behavioral intelligence about a single file from workspace.json BEFORE you edit it. Combines two signals the current source tree cannot reveal on its own:
Call this before editing or creating a file. Treat a fragile result as a reason to make minimal, well-tested changes; treat co-change partners as candidates for related edits. Args:
Returns JSON: { "path": string, "fragile": boolean, "fragility": { "reason"?: string, "score"?: number, "evidence"?: string[] } | null, "coChangePartners": string[], "indexed": boolean, // whether the file appears in the workspace file index "workspaceVersion": string | null } Returns fragile:false with empty partners when the file has no recorded history (this is a real answer, not an error). |
| workspace_get_cochange_partners | Return the files that historically change together with the given file, per workspace.json. Use after editing a file to check whether related files also need updating. Args:
Returns JSON: { "path": string, "partners": string[], "count": number } Returns an empty partners array when none are recorded (a real answer, not an error). |
| workspace_list_fragile_filesA | List all files flagged fragile in workspace.json, most fragile first (by score when present). Use for orientation at the start of a task: it tells you which parts of the codebase carry the most historical risk. Args:
Returns JSON: { "count": number, "total": number, "workspaceVersion": string | null, "framework": Record<string, string | number | boolean> | null, "files": [{ "path": string, "reason"?: string, "score"?: number }] } |
| workspace_assess_changeA | Evaluate a SET of file paths (a proposed change) against workspace.json fragility and co-change history, and return a mechanical enforcement decision. Decision semantics (derived, never model-emitted):
Args:
Returns JSON: { "action": "deny" | "warn" | "annotate" | "none", "assessments": [{ "path", "fragile", "tier", "coChangePartners", "missingPartners", "action", "message" }], "workspaceVersion": string | null } |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/workspace-json/codex-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server