Giggy Speech MCP

io.github.GRQDigitalCapitalv1.0.0更新于 Oct 8, 2026

Giggy speech tools for AI agents: discover voices and generate text-to-speech.

已验证Streamable HTTP可网页运行Media & Design

概览

AI 生成的概览

让助手浏览 Giggy 语音并提交文本转语音任务,再轮询获取生成完成的音频链接。

功能
这是一个远程 Streamable HTTP MCP 服务器,提供 Giggy 语音工具:list_voices 和 list_my_voices 用于发现可用语音 ID,generate_speech 用于提交文本转语音任务,get_speech_generation 用于查询任务状态。生成是异步的:工具返回持久化的元数据和生成 UUID,而不是实时音频字节,任务状态变为 completed 后可从结果链接获取音频。该端点为无状态,接受 POST 请求。
适用场景
当助手或编程代理需要通过 Giggy 把文本转为语音时使用,例如为生成的内容配音,或把语音输出接入代理工作流。适合能够轮询任务直到完成的客户端,而不是期望在工具响应中直接拿到音频的场景。
运行要求
远程 MCP 端点 Streamable HTTP,无需本地包或运行时。需要 Giggy API 密钥,以 Authorization bearer 令牌发送,通常在客户端配置中通过 GIGGY_API_KEY 环境变量提供。需要访问 giggy.ai 的网络连接。
安装前请注意
Authorization bearer 令牌是密钥,不要写入提示词、提交到版本控制或嵌入浏览器 JavaScript,也不要提交已配置的客户端文件。语音生成是 Giggy 的付费服务,使用可能产生费用。服务器会提交生成任务并在账户上写入生成记录,每次新的生成应使用新的幂等键以避免重复。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Giggy Speech MCP,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

{
  "mcpServers": {
    "giggy-mcp": {
      "type": "http",
      "url": "https://giggy.ai/mcp"
    }
  }
}

README

Giggy MCP — text-to-speech for AI agents

[MCP Docs CI]

Giggy MCP is a remote Streamable HTTP Model Context Protocol (MCP) server for using Giggy text-to-speech from coding agents and AI clients.

It provides Giggy speech tools to Codex, Claude Code, Cursor, VS Code, Cline, Windsurf-compatible clients, and other MCP clients.

MCP registry and plugin directories

Giggy's remote speech MCP endpoint is:

https://giggy.ai/mcp

This repository contains the publication artifacts for:

See directory submission status and requirements.

A public registry listing, plugin submission, and approved plugin publication are separate steps. Consult the submission document for verified status.

Quick setup

Use Giggy MCP with Codex

Set GIGGY_API_KEY in your environment, then add to ~/.codex/config.toml:

toml
[mcp_servers.giggy-speech]url = "https://giggy.ai/mcp"bearer_token_env_var = "GIGGY_API_KEY"

Use Giggy MCP with Claude Code

Set GIGGY_API_KEY, then configure:

json
{  "mcpServers": {    "giggy-speech": {      "type": "http",      "url": "https://giggy.ai/mcp",      "headers": { "Authorization": "Bearer ${GIGGY_API_KEY}" }    }  }}

Keep API keys out of configuration files committed to source control.

Remote MCP server

text
https://giggy.ai/mcp

Transport:

text
Streamable HTTP

The current Giggy MCP endpoint is stateless and accepts POST requests.

Authentication

Use a Giggy API key:

text
Authorization: Bearer $GIGGY_API_KEY

Giggy API keys begin with:

text
giggy_sk_

Keep the key in your MCP client's secret or environment configuration.

Do not:

  • put it in ordinary prompts
  • commit it to source control
  • embed it in browser JavaScript

Speech tools

This repository documents these Giggy speech tools:

text
list_voiceslist_my_voicesgenerate_speechget_speech_generation

The MCP server may expose other Giggy tools outside the speech scope of this repository.

Recommended speech workflow

  1. Call list_voices or list_my_voices.
  2. Select the exact returned voice_id.
  3. Call generate_speech.
  4. Supply a fresh idempotency_key for each new intended generation.
  5. Save generation.generation_uuid.
  6. Call get_speech_generation while the status is queued or processing.
  7. When the status becomes completed, use generation.result.url.

Do not resubmit a new generation while polling an existing generation.

Use Giggy MCP with Codex

Set:

bash
export GIGGY_API_KEY="giggy_sk_..."

Then add this to:

text
~/.codex/config.toml
toml
[mcp_servers.giggy-speech]url = "https://giggy.ai/mcp"bearer_token_env_var = "GIGGY_API_KEY"

A ready-to-copy version is included at:

text
examples/codex-config.toml

Verify:

bash
codex mcp list

Use Giggy MCP with Claude Code

Set:

bash
export GIGGY_API_KEY="giggy_sk_..."

A project MCP configuration is included at:

text
examples/claude-code.mcp.json

Its contents are:

json
{  "mcpServers": {    "giggy-speech": {      "type": "http",      "url": "https://giggy.ai/mcp",      "headers": {        "Authorization": "Bearer ${GIGGY_API_KEY}"      }    }  }}

Copy that configuration to:

text
.mcp.json

in the project where Claude Code should use Giggy.

Then run:

bash
claude mcp list

or use:

text
/mcp

inside Claude Code.

Other MCP clients

Ready-to-copy client configurations are included for:

Cursor

Set:

bash
export GIGGY_API_KEY="giggy_sk_..."

Copy or merge:

text
examples/cursor.mcp.json

into:

text
.cursor/mcp.json

for project configuration, or:

text
~/.cursor/mcp.json

for global configuration.

VS Code

Copy or merge:

text
examples/vscode.mcp.json

into:

text
.vscode/mcp.json

VS Code will prompt securely for the Giggy API key.

Cline

Open Cline's MCP server configuration and copy the contents of:

text
examples/cline.mcp.json

Replace:

text
YOUR_GIGGY_API_KEY

in your local configuration only.

Do not commit the configured file.

Windsurf-compatible clients

For installations that use:

text
~/.codeium/windsurf/mcp_config.json

merge the contents of:

text
examples/windsurf.mcp.json

and replace:

text
YOUR_GIGGY_API_KEY

in the local configuration only.

Raw MCP examples

Set:

bash
export GIGGY_API_KEY="giggy_sk_..."

Initialize:

bash
./examples/initialize.sh

List tools:

bash
./examples/list-tools.sh

List public voices:

bash
./examples/list-voices.sh

Important behavior

generate_speech returns durable generation metadata.

It does not return live MP3 or PCM audio bytes through MCP.

For progressive PCM audio, use:

text
POST https://giggy.ai/v1/text-to-speech

with:

text
mode=streamingoutput_format=pcm_24000

Developer resources

Speech API documentation:

text
https://giggy.ai/docs/speech-api

OpenAPI:

text
https://giggy.ai/v1/openapi.json

Runnable examples:

text
https://github.com/GRQDigitalCapital/giggy-examples

Pricing:

text
https://giggy.ai/pricing

Official SDK and runnable examples:

来源:README.md,提交 5f84f4e

工具

0
工具元数据尚未被收录。

版本历史

1
  1. v1.0.0最新Oct 8, 2026