feat: add grok-tts tool (text-to-speech)

[hrco]

Summary

• PR 1 of 5 for issue feat: new tool areas — TTS, STT, Files API, Context Compaction, Batch #21 — adds the grok-tts tool per docs/issue-21-scope.md (from docs: scope issue #21 (TTS, STT, Files API, Context Compaction, Batch) #34).
• New constants: TTS_API_BASE, TTS_VOICES (eve/ara/rex/sal/leo), DEFAULT_TTS_VOICE.
• make_tts_request() — always sends with_timestamps: true internally so the API always returns the JSON+base64 shape, avoiding a content-type branch.
• handle_grok_tts() — validates text, returns AudioContent (base64 MP3) plus a TextContent summary, with an optional word-timestamp table when with_timestamps: true is requested by the caller.
• Tool schema registered in list_tools() / dispatched in call_tool().

v1 cut: no output_format codec/sample-rate customization — MP3 24kHz/128kbps default only (flagged in the scope doc as a follow-up if needed).

Test plan

• pytest tests/test_audio_tools.py -v — 8/8 new tests pass
• pytest tests/ — 142 passed, 51 pre-existing failures (known pytest-asyncio strict-mode baseline, unrelated to this change), 3 skipped — no regressions
• Verified grok-tts appears in list_tools() output (20 tools total, up from 19)
• Founder smoke test against real XAI_API_KEY

🤖 Generated with Claude Code

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

[coderabbitai]

Warning

Review limit reached

@hrco, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 2 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 3a3f87e4-f87d-43a0-9040-1a8e273e39ad

📥 Commits

Reviewing files that changed from the base of the PR and between 4bc4f45 and e316b15.

📒 Files selected for processing (3)

• CLAUDE.md
• tests/test_audio_tools.py
• xbridge_mcp/server.py

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/grok-tts

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}