say-mcp-server

Created By
bmorphisma year ago
MCP server for macOS text-to-speech functionality
Overview

what is say-mcp-server?

The say-mcp-server is an MCP server designed to provide text-to-speech functionality using macOS's built-in say command, enabling applications to convert text into spoken words.

how to use say-mcp-server?

To use say-mcp-server, install it via npm and configure your MCP settings to point to the server's command. You can then use the speak tool to convert text to speech.

key features of say-mcp-server?

  • Utilizes macOS's native text-to-speech capabilities.
  • Supports extensive customization options for speech, including voice selection, rate adjustment, and volume control.
  • Allows background speech processing for simultaneous actions.

use cases of say-mcp-server?

  1. Reading aloud text from applications or documents.
  2. Providing audio feedback in interactive applications.
  3. Integrating with other services to read content aloud, such as YouTube transcripts or search results.

FAQ from say-mcp-server?

  • Is say-mcp-server compatible with all macOS versions?

Yes, it requires macOS with Node.js version 14.0.0 or higher.

  • Can I customize the voice used for speech?

Yes! You can choose from various voices available on your macOS system.

  • Is there a way to adjust the speaking rate?

Yes, you can specify the speaking rate in words per minute as a parameter.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
bmorphism
Star
-
Language
-
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
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.

31 minutes ago