Skip to main content
Glama
enesjakozh
tatn

MCP Server Diff TypeScript

by tatn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

mcp-server-diff-typescript MCP 서버

통합된 diff 생성 기능을 제공하는 모델 컨텍스트 프로토콜 서버입니다.

이 TypeScript 기반 MCP 서버는 diff 생성 시스템을 구현합니다. 두 텍스트 문자열 간의 통합 diff를 생성하는 도구를 제공하며, 이는 텍스트 차이점을 비교하고 분석하는 데 유용합니다.

특징

도구

  • get-unified-diff - 두 텍스트 문자열 간의 통합 diff 생성

    • oldString 과 newString 필수 매개변수로 사용합니다.

    • 통합된 diff 형식으로 차이를 반환합니다.

    • 정확한 차이 감지를 위해 diff 패키지를 사용합니다.

    • 변경 사항에 대한 3줄의 맥락이 포함되어 있습니다.

Related MCP server: Git Stuff Server

설치

글로벌 패키지로서

지엑스피1

프로젝트 종속성으로서

npm install mcp-server-diff-typescript

용법

Claude Desktop과 함께 사용

Claude Desktop과 함께 사용하려면 서버 구성을 추가하세요.

MacOS의 경우: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows의 경우: %APPDATA%/Claude/claude_desktop_config.json

"mcpServers": {
  "mcp-server-diff-typescript": {
    "command": "npx",
    "args": [
      "-y",
      "mcp-server-diff-typescript"
    ]
  }
}

또는 다음 구성을 추가합니다.

git clone https://github.com/tatn/mcp-server-diff-typescript.git
cd mcp-server-diff-typescript
npm install
npm run build
"mcpServers": {
  "mcp-server-diff-typescript": {
    "command": "node",
    "args": [
      "/path/to/mcp-server-diff-typescript/build/index.js"
    ]
  }
}

디버깅

MCP 서버를 디버깅하려면:

npx @modelcontextprotocol/inspector npx -y mcp-server-diff-typescript
npx @modelcontextprotocol/inspector node /path/to/mcp-server-diff-typescript/build/index.js

Available Tools

1 tool
get-unified-diffB

Get the difference between two text articles in Unified diff format.

ParametersJSON Schema
NameRequiredDescriptionDefault
oldStringYesold string to compare
newStringYesnew string to compare

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions the output format ('Unified diff format') but lacks details on error handling, performance characteristics, or any constraints (e.g., input size limits). For a tool with no annotations, this leaves significant gaps in understanding how it behaves beyond basic functionality.

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?

The description is a single, efficient sentence that directly states the tool's function without unnecessary words. It is front-loaded with the core purpose and includes the output format, making it easy to understand quickly. Every part of the sentence contributes essential information.

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

Completeness3/5

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

Given the tool's moderate complexity (comparing two strings) and no output schema, the description is adequate but incomplete. It covers the basic purpose and output format but lacks details on behavioral aspects like error cases or performance. Without annotations, it should do more to compensate, but it meets the minimum viable threshold for a simple diff tool.

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?

The schema description coverage is 100%, with clear descriptions for both parameters ('old string to compare' and 'new string to compare'). The description adds minimal value beyond the schema by implying the parameters are text articles, but it doesn't provide additional context like format expectations or examples. Baseline 3 is appropriate as the schema does the heavy lifting.

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 clearly states the tool's purpose: 'Get the difference between two text articles in Unified diff format.' It specifies the verb ('Get'), resource ('difference'), and output format ('Unified diff format'), making the function unambiguous. However, since there are no sibling tools, it doesn't need to differentiate from alternatives, so it doesn't reach the highest score of 5.

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?

The description provides no guidance on when to use this tool versus alternatives. It states what the tool does but offers no context about scenarios where it's appropriate, prerequisites, or limitations. With no sibling tools, it could implicitly suggest this is the only diff tool, but explicit usage guidelines are missing.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool update
    • First observedget-unified-diff
Deploy Server
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

TDQS

B3.3/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined as generating unified diffs between text articles, making it impossible to confuse with other tools.

Naming Consistency5/5

The single tool name 'get-unified-diff' follows a clear verb-noun pattern (get + unified_diff). With only one tool, consistency is inherently perfect as there are no other names to compare against.

Tool Count2/5

A single tool is generally too few for most server purposes, as it limits functionality and scope. While this server focuses narrowly on diff generation, having only one tool feels thin and may not cover related operations like diff analysis or formatting options.

Completeness3/5

The tool provides a core diff generation function, but the surface is notably incomplete. There are obvious gaps, such as no tools for comparing files, handling different diff formats, or managing diff history, which limits the server's utility for broader text comparison tasks.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • MCP JSONDiff Kel

    YohanLiu
    F
    license
    C
    quality
    D
    maintenance
    An efficient MCP server for performing accurate, deep comparisons between JSON objects or strings using the deepdiff engine. It provides AI agents with standardized difference reports, supporting nested structures and various input formats to ensure precise data analysis.
    1
    -

  • Fast Diff MCP Server

    kweinmeister
    A
    license
    Not graded
    quality
    B
    maintenance
    A high-performance Model Context Protocol server that provides text diffing capabilities, enabling LLMs to compare two blocks of text and receive differences in unified diff format.
    6
    Apache 2.0

Appeared in Searches