MCP Chunk Editor

Created By
dwymarka year ago
An MCP server providing an efficient and safe text editor for LLMs
Overview

what is MCP Chunk Editor?

MCP Chunk Editor is a Model Context Protocol server that provides chunk-oriented text file editing capabilities for Large Language Models (LLMs). It allows LLMs to edit files using semantically meaningful chunks instead of traditional line numbers, enhancing the editing experience.

how to use MCP Chunk Editor?

To use MCP Chunk Editor, you can install it via pip or run it using uv. After installation, you can interact with the server using various commands to read, replace, undo, create, or delete file chunks.

key features of MCP Chunk Editor?

  • Semantic Chunking: Identifies meaningful code structures for efficient editing.
  • Immediate Application: Changes are applied instantly with a preview for verification.
  • Simple Undo: Easily revert the last change made to a file.
  • Efficiency: Optimized for LLM token usage with incremental updates.

use cases of MCP Chunk Editor?

  1. Editing code files with semantic awareness.
  2. Quickly applying changes to large text files.
  3. Reverting changes in collaborative coding environments.

FAQ from MCP Chunk Editor?

  • Can MCP Chunk Editor handle all file types?

Yes, it can handle various text files as long as they are compatible with the chunking process.

  • Is there a limit to the chunk size?

By default, the maximum chunk size is 100 lines, but it can be customized.

  • How do I install MCP Chunk Editor?

You can install it via pip using the command pip install mcp-chunk-editor.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
dwymark
Star
0
Language
Python
License
MIT license

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago