Roxels
Let your coding agent provision Roxels voice agents in meeting rooms and collect structured interview or call data while you build voice-first workflows or research automation.
Overview
ai.roxels/roxels-mcp is an MCP server for the Build phase that lets coding agents create Roxels voice agents in meeting rooms and return structured session data.
What is this MCP server?
- Create configurable voice agents via Roxels meeting rooms from an MCP tool surface
- Returns structured data suitable for downstream code and analytics
- PyPI package roxels-mcp v0.5.1 with uvx runtime hint and stdio transport
- Requires ROXELS_API_KEY (sk-...) from app.roxels.ai Settings → API Keys
- Optional ROXELS_API_URL override for self-hosted or development environments
- Server version 0.5.1
- PyPI identifier roxels-mcp with uvx runtimeHint
- Repository subfolder roxels_mcp on github.com/trebu-org/interviewer
What problem does it solve?
You want voice interviews or calls driven by your agent but lack an MCP bridge to spin up Roxels voice agents and capture structured results in your build loop.
Who is it for?
Indie builders adding voice data collection, async interviews, or agent-led calls on top of Roxels with API keys already in hand.
Skip if: Teams that only need text chat LLMs, or products that cannot use third-party voice APIs and meeting-room infrastructure.
What do I get? / Deliverables
Once configured with ROXELS_API_KEY, your agent can create meeting-room voice agents and feed structured outputs into your app logic, tests, and integration code.
- Programmatically created Roxels voice agents in meeting rooms
- Structured call or interview payloads usable in application code
- Repeatable agent-driven integration tests against Roxels API
Recommended MCP Servers
Journey fit
Creating configurable voice agents through an API is build-time integration work—you wire Roxels into the product or internal agent stack before ship and launch. Integrations subphase is the right shelf for MCP that spins up third-party voice rooms and returns structured payloads to your codebase.
How it compares
Voice-agent provisioning MCP integration, not a local speech-to-text CLI or generic calendar skill.
Common Questions / FAQ
Who is ai.roxels/roxels-mcp for?
Solo builders and small teams implementing voice-agent workflows with Roxels who want Claude Code, Cursor, or Codex to create rooms and pull structured data via MCP.
When should I use ai.roxels/roxels-mcp?
Use it during build integrations while you implement voice interviews, qualification calls, or research bots that must be created and tuned from your repository via API.
How do I add ai.roxels/roxels-mcp to my agent?
Install or run roxels-mcp via uvx per PyPI, set ROXELS_API_KEY and optional ROXELS_API_URL, and add the stdio MCP server entry in your agent client using transport settings from the registry package block.