Skip to main content
The MCP server is stateless and never stores your credentials — your API key is read from each request and forwarded to the Rime API. Get a key from the API Tokens page; it’s the same key you use for the REST API.

​
Accepted headers

Two headers are accepted, checked in this order:
HeaderNotes
Authorization: Bearer <key>Preferred
X-Rime-Api-Key: <key>Convenience alternative for clients that reserve the Authorization header

​
Tools that work without a key

ToolAPI key
list_voicesNot required
get_voice_detailsNot required
generate_integrationNot required
check_dictionaryRequired
normalize_textRequired
synthesize_speechRequired
If a key-gated tool is called without a key, it responds with a pointer to sign up rather than an error — so a keyless connection is still useful for exploring the catalog and generating integration code.
synthesize_speech calls the Rime API with your key, so generated samples consume credits like any other API request.