Textops Mcp

io.github.nexus-api-labPublished by GitHub account nexus-api-labv0.1.0Updated Oct 24, 2026

Exact text tools for AI agents: unified diff, patch apply, regex testing, grapheme counting.

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

A remote MCP server offering exact text operations: unified diff, patch application, regex testing, and grapheme counting.

What you can do
Textops Mcp exposes text-processing tools to an assistant over a remote streamable HTTP endpoint. According to its registry description, it provides unified diff generation, patch application, regex testing, and grapheme counting. These are deterministic string operations rather than general-purpose editing or file management.
When to use it
Useful when an assistant needs to compare two text versions, apply a patch, validate a regular expression, or count user-perceived characters accurately. It suits text-heavy coding or content workflows where exact, reproducible string results matter.
Requirements
A remote MCP client that supports streamable HTTP, plus network access to the provider's endpoint. No packages, environment variables, headers, or authentication are declared.
Before you install
The service is remote, so any text submitted for diffing, patching, or regex testing is sent to a third-party endpoint; avoid sending secrets or private content. No authentication is declared, so the endpoint is not shown to be access-controlled. Patch application can change text, so review results before relying on them.

Installation

In SourceWeft

  1. Open Textops Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.nexus-api-lab%2Ftextops-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "textops": {
      "type": "http",
      "url": "https://textops-mcp.dokasukadon.workers.dev/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.