Skip to main content
Glama
workspace-json

@workspacejson/codex-mcp

Official

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
WORKSPACE_JSON_PATHNoOptional: 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

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
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:

  • Fragility: whether this file is historically error-prone / high blast radius, with reason and evidence when available.

  • Co-change: which other files have historically been edited together with this one.

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:

  • path (string): repo-relative or absolute file path.

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:

  • path (string): repo-relative or absolute file path.

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:

  • limit (number, optional): max files to return (default 50, max 500).

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):

  • "deny": an evidenced-fragile file is touched while its recorded co-change partners are absent from the changeset. Include the recorded co-change partners, or stop and review the exception with a human.

  • "warn": evidenced-fragile file touched (partners covered), or co-change partners missing on a non-evidenced file.

  • "annotate": fragility asserted without evidence. Context only.

  • "none": no recorded history. This is NOT a safety approval; this tool never certifies a change as safe.

Args:

  • paths (string[]): repo-relative or absolute paths in the proposed change (1-200).

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

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.6/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a distinct and clear purpose: get context for a single file, list fragile files, and assess a set of file changes. There is no ambiguity or overlap.

Naming Consistency5/5

All tools follow a consistent 'workspace_verb_noun' pattern in snake_case, making them predictable and easy to understand.

Tool Count5/5

Three tools is well-scoped for a specialized server focused on workspace.json code intelligence; each tool earns its place without being too few or too many.

Completeness5/5

The tool surface covers the core operations for the domain: inspecting individual file history, listing high-risk files, and validating changes against historical data. No obvious gaps for its intended read-only analysis purpose.

Maintenance

ActivityMaintained
ResponsivenessNo issues