Skip to main content
Glama
rocnubie

WordCast MCP Server

by rocnubie
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
JavaScript
Remote

WordCast MCP Server

MCP server for WordCast

MCP Badge License: MIT Node Read Only MCP

A Model Context Protocol server that exposes the canonical WordCast knowledge surface — voice and TTS workflows, blog topics, FAQ, official links — to MCP-compatible AI clients such as Claude Desktop, Cursor, Windsurf, and Continue. Read-only, no API keys, no quota, ~50 ms cold start.

Official website: https://wordcast.app

🎙️ About WordCast

WordCast is a browser-based text-to-speech reader that converts written content into audio entirely on your device. There is no backend server involved: text, files, and URLs are processed locally using the speech synthesis voices already installed on your operating system. The result is a tool that starts playing in under a second, works without creating an account, imposes no character limits or usage caps, and remains completely free. It accepts a wide range of input types — pasted text, uploaded documents, or a web URL — and outputs clear, natural-sounding audio through any of the voices available on your system.

Related MCP server: earscribe-mcp

Key Features

  • Local processing only — text and files never leave the device; computation happens entirely in the browser using OS-native speech synthesis

  • Broad format support — accepts PDF, DOCX, EPUB, RTF, TXT, MD, and HTML file uploads, as well as pasted text and URLs pointing to online articles

  • 200+ voices across 60+ languages — leverages the full set of voices pre-installed on the user's operating system, covering a wide range of languages and accents

  • Instant playback — audio begins in under one second with no loading screens, server round-trips, or queued processing

  • Playback controls — adjustable reading speed, lock-screen media controls, and media session integration for a consistent listening experience across devices

  • No account required — no signup, no subscription tier, no usage tracking

Use Cases

  • Commute listening — paste a long article or upload a document before leaving, then listen hands-free during travel

  • Proofreading by ear — authors and editors use the read-aloud function to catch awkward phrasing and errors that are easy to miss when reading silently

  • Language learning — hear native pronunciation of words and sentences across dozens of languages using region-specific voices

  • Handling sensitive documents — legal, medical, or personal documents can be listened to without uploading them to any external service

  • Accessibility support — users with dyslexia, ADHD, or visual fatigue benefit from audio rendering of written content without installing dedicated software

Who Is It For

WordCast is well suited to anyone who regularly reads long-form text and prefers listening as an alternative or complement to silent reading. Researchers working through papers, writers editing their own drafts, students reviewing study materials, and language learners practicing pronunciation are all natural users. The privacy-first design makes it a practical choice for professionals handling confidential documents — lawyers, therapists, and medical staff who need to process sensitive text without routing it through third-party cloud services. Because there is no account system and no paywall, it is also accessible to users in environments where cloud-based tools are restricted or where bandwidth is limited.

Tools

list_voices

Return the canonical voice and TTS configuration exposed on the site. (WordCast)

Input: no parameters. Returns: text/markdown.

get_official_links

Return the canonical list of official links for WordCast (website, support, docs when available).

Input: no parameters. Returns: text/markdown.

Resources

  • site://wordcast/voices — Supported voices, languages, and TTS modes.

  • site://wordcast/faq — Short FAQ generated from public site metadata.

  • site://wordcast/links — Canonical URLs to share with users.

Prompts

tell_me_about_wordcast

Summarize what the site is, who it's for, and how it works. — WordCast

read_aloud_demo_wordcast

Plan a read-aloud workflow with the site's voices. — WordCast

Installation

Install via Smithery

npx -y @smithery/cli install wordcast-mcp --client claude

(Replace claude with cursor, windsurf, or continue for those clients.)

Install from source

git clone https://github.com/rocnubie/wordcast-mcp.git
cd wordcast-mcp
pnpm install

Then add to your MCP client config (claude_desktop_config.json for Claude Desktop, mcp.json for Cursor / Windsurf / Continue):

{
  "mcpServers": {
    "wordcast-mcp": {
      "command": "node",
      "args": [
        "/absolute/path/to/wordcast-mcp/src/index.mjs"
      ]
    }
  }
}

Debug with MCP Inspector

npx @modelcontextprotocol/inspector node src/index.mjs

Official Links

Development

pnpm install
pnpm start                 # run the server over stdio

License

MIT

Available Tools

2 tools
list_voicesA

Return the canonical voice and TTS configuration exposed on the site. (WordCast)

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

TDQS

A4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. 'Return' implies a read-only operation, but it does not disclose any side effects, permissions, or limitations (e.g., whether the config is static or could change). For a simple list tool, this is adequate but not rich in detail.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, front-loaded with the verb 'Return', and includes a parenthetical '(WordCast)' for context. It is concise and to the point with no unnecessary words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (0 params, no output schema, no annotations), the description is largely sufficient. It clearly states what is returned, though it does not elaborate on the meaning of 'canonical' or potential variations in the output.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has zero parameters, and the description correctly adds no parameter information. Per the rubric, zero parameters receives a baseline of 4.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Return') and the resource ('canonical voice and TTS configuration exposed on the site'). This distinguishes it from the sibling tool get_official_links, which presumably deals with links.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage when voice/TTS config is needed, but provides no explicit when-to-use or when-not-to-use guidance. No alternatives are mentioned, and the sibling tool get_official_links is not cross-referenced.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 2 tool updatesv0.1.0
    • First observedget_official_links
    • First observedlist_voices
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A4/5.0
Disambiguation5/5

The two tools are clearly distinct: one provides voice and TTS configuration, while the other returns official links. There is no overlap in purpose or output, so an agent can easily choose the correct tool.

Naming Consistency5/5

Both tools follow a consistent verb_noun pattern (list_voices, get_official_links) and use clear, descriptive verbs. The naming is uniform and predictable, making it easy to infer functionality from the name alone.

Tool Count3/5

With only two tools, the server feels minimal. For a server that presumably handles WordCast TTS configuration, two informational tools are borderline and leave the impression that more functionality could be exposed.

Completeness2/5

The tools only provide static configuration and link information. There is no tool for actual TTS operations such as synthesizing speech or managing voices, which is a significant gap for a server named WordCast. The surface is incomplete for any practical TTS workflow.

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rocnubie/wordcast-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server