Skip to main content
Glama
Sign In
litewrite-mcp-server

litewrite-mcp-server

by KevinKwank
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Pull Project to Local Mirror

litewrite_pull
Idempotent

Mirror a Litewrite project to a local directory: download server files, remove deleted local files, and record a manifest so later pushes detect changes.

Instructions

Mirror a Litewrite project down into a local directory (git-clone/pull style).

Downloads all text files from the server into the local working copy at ~/.litewrite-mcp/ (or LITEWRITE_LOCAL_DIR), removes local files that no longer exist on the server, and records a content manifest so a later push can detect changes.

Args:

  • projectId (string, required): The project id.

Returns what was downloaded and removed.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "projectId": "<projectId>"
    },
    "name": "litewrite_pull"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdYesThe Litewrite project id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Description discloses significant traits beyond annotations: the exact local target path and env override, that it deletes local files no longer on the server, and that it writes a content manifest. The destructive-looking local deletion is tempered by the destructiveHint=false annotation, but the description appropriately warns about the local removal behavior. It could note whether server-side content is ever modified.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded single-sentence purpose, then scoped behavioral detail, then an Args block and a Returns line. No wasted sentences; each clause adds operational value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter mirror tool with no output schema, the description covers target location, deletion semantics, and manifest recording. The 'Returns what was downloaded and removed' line partially covers output given no output schema. Could mention auth requirements or behavior when the local dir is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and there is only one parameter, so the schema fully documents projectId; the description adds nothing beyond restating it as required. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (mirror/download) and resource (Litewrite project into a local directory), and explicitly frames it as git-clone/pull style, which distinguishes it from siblings like litewrite_read_file or litewrite_list_files.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The git-clone/pull framing gives clear operational context and the manifest note implies pairing with litewrite_push, but it never explicitly names when to use this versus litewrite_pull vs. granular read tools, nor states prerequisites like authentication or a valid projectId existing locally.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools