Giggy Speech MCP server

Giggy MCP — text-to-speech for AI agents

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:

• Official MCP Registry: server.json
• OpenAI / Codex: openai-plugin/
• Claude Code: .claude-plugin/plugin.json

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.

Install for AI coding agents

Agent Skill — Codex and Claude Code

npx skills add giggy-ai/giggy-mcp --skill giggy-speech

The skill provides Giggy speech-generation instructions. An MCP connection is still required.

Claude Code plugin

claude plugin marketplace add giggy-ai/giggy-mcp
claude plugin install giggy-speech@giggy

Codex

Follow the existing Codex MCP setup below.

Example prompt

"Use Giggy to list available English voices, generate a short Batch speech sample saying 'Hello from Giggy', and return the completed audio URL."

Discover Giggy

• Official MCP Registry
• Speech API docs
• Runnable examples
• Directory submission status

Quick setup

Use Giggy MCP with Codex

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

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

Use Giggy MCP with Claude Code

Set GIGGYAPIKEY, then configure:

{
  "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

https://giggy.ai/mcp

Transport:

Streamable HTTP

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

Authentication

Use a Giggy API key:

Authorization: Bearer $GIGGY_API_KEY

Giggy API keys begin with:

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:

list_voices
list_my_voices
generate_speech
get_speech_generation

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

Recommended speech workflow

1. Call listvoices or listmy_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 getspeechgeneration 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:

export GIGGY_API_KEY="giggy_sk_..."

Then add this to:

~/.codex/config.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:

examples/codex-config.toml

Shortened. The full README is on GitHub.