npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@rxreyn3/speak-mcp

v0.1.2

Published

Local MCP server for Ollama-rewritten macOS speech playback

Readme

Speak MCP

A local MCP server that rewrites text with Ollama for natural speech and reads it aloud with macOS say.

Requirements

  • macOS with the say command available.
  • Node.js 18 or newer.
  • Ollama running locally.
  • The configured Ollama model pulled locally.

Installation

You do not need to clone this repository to use Speak MCP. Install the published npm package globally, then configure your MCP client to run the speak-mcp binary.

npm install -g @rxreyn3/speak-mcp

Claude Desktop configuration

Edit ~/Library/Application Support/Claude/claude_desktop_config.json and add this server under mcpServers:

{
  "mcpServers": {
    "speak": {
      "command": "speak-mcp",
      "env": {
        "OLLAMA_HOST": "http://localhost:11434",
        "OLLAMA_MODEL": "qwen2.5:7b-instruct"
      }
    }
  }
}

Restart Claude Desktop after changing the config.

Local development

For local development from a clone:

npm install
npm run build

Then point your MCP client at the built entrypoint:

{
  "mcpServers": {
    "speak": {
      "command": "node",
      "args": ["/absolute/path/to/speak-mcp/dist/index.js"],
      "env": {
        "OLLAMA_HOST": "http://localhost:11434",
        "OLLAMA_MODEL": "qwen2.5:7b-instruct"
      }
    }
  }
}

Tools

speak_text

Reads explicit text aloud. The MCP client must pass the text; this server cannot read the client transcript itself.

{ "text": "Text to read aloud" }

The server rewrites the text with Ollama before playback. If Ollama is unreachable, returns an MCP tool error and does not speak raw text.

stop_speech

Stops the current macOS say playback, if any. This tool does not contact Ollama and does not start replacement audio.

Prompt

The server registers read_aloud, a user-selected prompt that instructs an MCP client to call speak_text with visible assistant response text when read-aloud behavior is requested.

Troubleshooting

  • If Claude Desktop does not show the server, confirm Node.js 18+ is installed and restart Claude Desktop after editing the config.
  • If speech does not start, confirm Ollama is running at OLLAMA_HOST and the model in OLLAMA_MODEL is pulled.
  • Do not add console.log to the server: stdout is reserved for MCP JSON-RPC messages. Use console.error for diagnostics.
  • Late say playback failures are logged to stderr and MCP logging; there is intentionally no speech_status tool in v1.