MCP Character Counter

Created By
webreactiva-devsa year ago
A lightweight Model Context Protocol (MCP) server that provides detailed character analysis for text.
Overview

What is MCP Character Counter?

MCP Character Counter is a lightweight Model Context Protocol (MCP) server designed to provide detailed character analysis for text, including counts of total characters, characters without spaces, letters, numbers, and symbols.

How to use MCP Character Counter?

To use the MCP Character Counter, you need to clone the repository, install the necessary dependencies, and configure it with either Claude Desktop or GitHub Copilot. After setup, you can analyze text character counts by sending commands to the server.

Key features of MCP Character Counter?

  • Count total characters in text
  • Count characters excluding spaces
  • Count letters (a-z, A-Z)
  • Count numbers (0-9)
  • Count symbols (non-alphanumeric characters)
  • Detailed breakdown of character types

Use cases of MCP Character Counter?

  1. Analyzing character composition in user inputs.
  2. Counting characters for text validation in applications.
  3. Providing insights into text data for developers and researchers.

FAQ from MCP Character Counter?

  • What programming language is MCP Character Counter built with?

It is built with JavaScript and requires Node.js v17 or higher.

  • Can I use it with any IDE?

Yes, it can be integrated with Claude Desktop and GitHub Copilot for various development environments.

  • Is there a license for this project?

Yes, it is licensed under the MIT License.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
webreactiva-devs
Star
0
Language
JavaScript
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

6 hours ago
Tavily Mcp
@tavily-ai

JavaScript
a year ago