Skip to main content
Glama
Sign In
kit-mcp

kit-mcp

by luanpdd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

sync

Projects the kit into IDE-specific layouts for Claude Code, Cursor, and Codex. Handles install, remove, and status actions.

Instructions

Project the kit into an IDE-specific layout (markdown references by default).

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": {
      "action": "<action>"
    },
    "name": "sync"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoDefault: reference
actionYes
dryRunNo
targetNoIDE id (e.g. claude-code, cursor, codex). Use action=targets to list.
autoSpawnNoOn action=install: auto-start the sidecar UI (kit ui) if not running and stream progress to it.
projectRootNoDefaults to cwd

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.29.0
  2. Removedv1.22.0
  3. Addedv1.21.0
  4. Removedv1.15.0
  5. Changed1 schema field changedv1.2.0
    • addedInput schema / properties / autoSpawn
      Added value: +{
+  "description": "On action=install: auto-start the sidecar UI (kit ui) if not running and stream progress to it.",
+  "type": "boolean"
+}
  6. First observedv0.4.1

TDQS

C2.9/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. It only mentions projection and default mode, but does not disclose whether actions are destructive, if it requires network, or what happens to existing data. Behavioral traits like install/remove actions are not explained.

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

Conciseness4/5

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

Single 12-word sentence is very concise and front-loaded. However, it cuts off critical information, earning a 4 rather than 5.

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

Completeness2/5

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

With 6 parameters, no output schema, and no annotations, the description is insufficient to fully understand the tool's behavior and constraints. It does not cover actions, dryRun, autoSpawn, etc.

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 description coverage is 67%, so baseline is 3. The description adds some value by noting default mode (markdown references), but does not elaborate on action enums, target, or other parameters meaningfully beyond schema.

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

Purpose4/5

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

The description uses specific verb 'Project' with resource 'kit' into 'IDE-specific layout', and mentions default mode (markdown references). It distinguishes from sibling 'reverse-sync' and others by focusing on projecting to IDE layout, but could be more explicit.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives like install, reverse-sync, etc. The description does not provide context for when sync is appropriate or what prerequisites exist.

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