MCP Text Transform Server

Created By
msv2017a year ago
Overview

What is MCP Text Transform Server?

MCP Text Transform Server is a C# .NET 9 implementation of the Model Context Protocol (MCP) that provides tools for transforming text into different formats, such as Capital Case and Snake Case.

How to use MCP Text Transform Server?

To use the server, clone the repository, build it using .NET 9 SDK, and run it. You can then integrate it with Claude Desktop by configuring the server in the application settings.

Key features of MCP Text Transform Server?

  • CapitalCase Tool: Converts text to Title Case format, intelligently adding spaces.
  • SnakeCase Tool: Converts text to snake_case format, handling various input formats.
  • Compliance with the Model Context Protocol for easy integration with MCP clients.

Use cases of MCP Text Transform Server?

  1. Transforming user input text for better readability.
  2. Integrating with applications that require text formatting.
  3. Providing text transformation services in chat applications.

FAQ from MCP Text Transform Server?

  • Can I add new transformation tools?

Yes! You can add new tools by implementing methods in the TextTransformTools class.

  • Is there a health check endpoint?

Yes, a health check endpoint is available at /health to verify the server status.

  • What are the prerequisites for running the server?

You need .NET 9.0 SDK or later and Claude Desktop for testing.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
msv2017
Star
0
Language
C#
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