Text Tools Mcp

io.github.mrfentmenPublished by GitHub account mrfentmenv1.0.0Updated Oct 24, 2026

Slugify, convert case, and encode text locally. No network and no key.

VerifiedSTDIODesktop onlyDeveloper Tools

Overview

AI-generated overview

A local MCP server that lets an assistant slugify, change the case of, and encode text without network access.

What you can do
Text Tools Mcp exposes small text-transformation utilities to an assistant: turning strings into slugs, converting between letter cases, and encoding text. It runs as a local process over stdio, so the transformations happen on the user's own machine. The registry description states it needs no network and no key.
When to use it
Worth adding when an assistant regularly needs to normalize titles or filenames into slugs, switch text between cases, or encode strings during local editing work. It is a narrow utility, so it only makes sense if those transformations come up often.
Requirements
Runs as a local process on the user's machine, installed from the npm package text-tools-mcp over stdio. Desktop only; no web executable. No authentication, environment variables, or headers are declared, and the description says no network and no key are needed.
Before you install
No credentials, payments, or third-party data flows are indicated; the description says processing is local with no network. The manifest does not list the individual tools, so the exact transformations and whether any of them write files cannot be confirmed from the available information.

Installation

In SourceWeft

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

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.0LatestSep 22, 2026

Score

25% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 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.

  • License10 pts

    Declare a license in the repository or the registry entry.