macOS に組み込まれているsayコマンドを使用してテキスト読み上げ機能を提供する MCP サーバー。
macOS（組み込みのsayコマンドを使用）
Node.js >= 14.0.0
Related MCP server: Edge TTS MCP
MCP 設定構成ファイルに次の内容を追加します。
{
"mcpServers": {
"say": {
"command": "node",
"args": ["/path/to/say-mcp-server/build/index.js"]
}
}
}npm install say-mcp-serverspeakツールは、広範なカスタマイズ オプションを備えた macOS のテキスト読み上げ機能へのアクセスを提供します。
macOS のテキスト読み上げ機能を使用して、テキストを読み上げます。
パラメータ:
text （必須）: 読み上げるテキスト。サポート対象:
プレーンテキスト
休止のための基本的な句読点
自然な区切りのための改行
[[slnc 500]] 500msの無音
[[rate 200]] テキストの途中で速度を変える
[[volm 0.5]] テキストの途中で音量を変える
強調のための[[emph +]]と[[emph -]]
ピッチ調整用の[[pbas +10]]
voice (オプション): 使用する音声 (デフォルト: "Alex")
rate （オプション）：1分あたりの単語数での発話速度（デフォルト：175、範囲：1〜500）
background （オプション）：MCPとのさらなる対話を可能にするために、バックグラウンドで音声を実行します（デフォルト：false）
音声変調:
use_mcp_tool({
server_name: "say",
tool_name: "speak",
arguments: {
text: "[[volm 0.7]] This is quieter [[volm 1.0]] and this is normal [[volm 1.5]] and this is louder",
voice: "Victoria"
}
});動的なレートの変更:
use_mcp_tool({
server_name: "say",
tool_name: "speak",
arguments: {
text: "Normal speed [[rate 300]] now speaking faster [[rate 100]] and now slower",
voice: "Fred"
}
});強調とピッチ:
use_mcp_tool({
server_name: "say",
tool_name: "speak",
arguments: {
text: "[[emph +]] Important point! [[emph -]] [[pbas +10]] Higher pitch [[pbas -10]] Lower pitch",
voice: "Samantha"
}
});余白検索付き:
// Search for a topic and have the results read aloud
const searchResult = await use_mcp_tool({
server_name: "marginalia-mcp-server",
tool_name: "search",
arguments: { query: "quantum computing basics", count: 1 }
});
await use_mcp_tool({
server_name: "say",
tool_name: "speak",
arguments: {
text: searchResult.results[0].description,
voice: "Daniel",
rate: 150
}
});YouTube トランスクリプト付き:
// Read a YouTube video transcript
const transcript = await use_mcp_tool({
server_name: "youtube-transcript",
tool_name: "get_transcript",
arguments: {
url: "https://youtube.com/watch?v=example",
lang: "en"
}
});
await use_mcp_tool({
server_name: "say",
tool_name: "speak",
arguments: {
text: transcript.text,
voice: "Samantha",
rate: 175
}
});複数のアクションを伴う背景音声:
// Start long speech in background
await use_mcp_tool({
server_name: "say",
tool_name: "speak",
arguments: {
text: "This is a long speech that will run in the background...",
voice: "Rocko (Italian (Italy))",
rate: 69,
background: true
}
});
// Immediately perform another action while speech continues
await use_mcp_tool({
server_name: "marginalia-mcp-server",
tool_name: "search",
arguments: { query: "parallel processing" }
});Apple Notes の場合:
// Read notes aloud
const notes = await use_mcp_tool({
server_name: "apple-notes-mcp",
tool_name: "search-notes",
arguments: { query: "meeting notes" }
});
if (notes.length > 0) {
await use_mcp_tool({
server_name: "say",
tool_name: "speak",
arguments: {
text: notes[0].content,
voice: "Karen",
rate: 160
}
});
}例：
use_mcp_tool({
server_name: "say",
tool_name: "speak",
arguments: {
text: "Hello, world!",
voice: "Victoria",
rate: 200
}
});システムで利用可能なすべてのテキスト読み上げ音声を一覧表示します。
例：
use_mcp_tool({
server_name: "say",
tool_name: "list_voices",
arguments: {}
});MCP 設定構成ファイルに次の内容を追加します。
{
"mcpServers": {
"say": {
"command": "node",
"args": ["/path/to/say-mcp-server/build/index.js"]
}
}
}macOS（組み込みのsayコマンドを使用）
Node.js >= 14.0.0
バートン・ローズ ( @bmorphism ) - barton@vibes.lol
マサチューセッツ工科大学
List available text-to-speech voices
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action but doesn't describe what the output looks like (e.g., list format, voice attributes), whether it's cached, or any rate limits. This leaves significant gaps for an agent to understand the tool's behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence with no wasted words. It's appropriately sized for a simple tool and front-loads the core purpose immediately.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple, parameterless tool with no output schema, the description is minimally adequate. However, it lacks details about the output format or behavioral traits, which would help an agent use it correctly. Without annotations, the description should do more to compensate.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has 0 parameters, and schema description coverage is 100% (though empty). The description doesn't need to add parameter details, so it meets the baseline expectation for a parameterless tool without compensation needed.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb ('List') and resource ('available text-to-speech voices'), making the tool's purpose immediately understandable. It doesn't explicitly differentiate from its sibling 'speak', but the distinction is reasonably implied (listing vs. using voices).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus its sibling 'speak' or any alternatives. The description only states what it does, not when it should be selected over other options.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Use macOS text-to-speech to speak text aloud
| Name | Required | Description | Default |
|---|---|---|---|
| background | No | Run speech in background to unblock further MCP interaction | |
| rate | No | Speaking rate (words per minute) | |
| text | Yes | Text to speak | |
| voice | No | Voice to use (e.g., "Alex", "Victoria", "Daniel") | Alex |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries full burden. It discloses the core behavior (speaking text aloud) but lacks details about permissions needed, whether speech blocks interaction (though the 'background' parameter hints at this), error conditions, or what happens on completion. The description doesn't contradict any annotations since none exist.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence that front-loads the core purpose. Every word earns its place with no redundancy or unnecessary elaboration.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with 4 parameters, 100% schema coverage, and no output schema, the description provides adequate context about what the tool does but lacks details about behavioral aspects like error handling, platform dependencies, or interaction blocking. It's minimally complete but could be more informative given the absence of annotations.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema already documents all four parameters thoroughly. The description adds no parameter-specific information beyond what's in the schema, meeting the baseline for high schema coverage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the specific action ('speak text aloud'), the technology used ('macOS text-to-speech'), and the resource ('text'). It distinguishes from the sibling tool 'list_voices' by focusing on speech output rather than voice enumeration.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage context (macOS text-to-speech functionality) but doesn't explicitly state when to use this tool versus alternatives or any prerequisites. It mentions the sibling tool 'list_voices' only indirectly through the voice parameter example.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
v1.0.0list_voicesspeakScored across 2 tools
The two tools have clearly distinct purposes: list_voices retrieves available options, while speak performs the core text-to-speech action. There is no overlap or ambiguity between them, making it easy for an agent to select the correct tool.
Both tools follow a consistent verb_noun pattern (list_voices and speak), with clear, descriptive names that align with their functions. There are no deviations or mixed conventions in the naming style.
With only two tools, the server feels thin for a text-to-speech domain. While it covers basic functionality (listing and speaking), it lacks operations like stopping speech, adjusting voice parameters, or managing speech queues, which are common in such systems.
The tool surface is severely incomplete for a text-to-speech server. It provides list and speak functions but misses essential operations such as pausing, resuming, or canceling speech, and offers no control over voice settings like rate or volume, limiting agent workflows.
Text to speech for your AI. Your AI can send text to Doc Player to read it aloud. You will see a reader window with the text and you can control the playback sentence by sentence. Find an example here: https://documentplayer.com/connect-ai/
Text-to-speech API: neural voices, pay-per-credit in Bitcoin sats via BTCPay.
AI voice generation: text-to-speech and voice cloning from any MCP client.
Audio for your agent: transcribe, speak, translate, summarise, plus sound effects and music.
