svara-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SVARA_API_KEY | Yes | Your Svara API key |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| upload_audioA | Upload a local audio file (MP3, M4A/AAC, OGG/Opus, WAV or WebM, max 4 MB) to Svara. Returns an audio_url to pass to send_linkedin_voice_note. Uploading does not send anything. |
| send_linkedin_voice_noteA | Send a native LinkedIn voice note to a person via Svara. WARNING: when dry_run is false this sends a REAL LinkedIn voice message to a real person, from the user's own LinkedIn account. It cannot be unsent. Only call with dry_run=false when the user has explicitly asked you to send this voice note to this recipient. dry_run defaults to true, which validates the request without sending anything. The recipient must be someone the user can already message on LinkedIn (for example a 1st-degree connection); pass their LinkedIn profile URL (preferred) or the name part after /in/ (not their display name). Provide exactly one of audio_url (from upload_audio) or file_path (a local audio file, uploaded first). Delivery requires the Svara Chrome extension to be installed and the user to be signed in to LinkedIn in Chrome. Returns a message id; check delivery with get_send_status. |
| get_send_statusA | Get the delivery status (queued, sent, failed or expired) of a voice note sent with send_linkedin_voice_note. |
| get_usageA | Get the current Svara plan usage and limits for this API key. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool targets a distinct step in the workflow: uploading audio, sending a voice note, checking delivery status, and viewing account usage. There is no meaningful overlap or ambiguity between them.
All tools follow a clear verb_noun pattern: upload_audio, send_linkedin_voice_note, get_send_status, get_usage. The get_ prefix is used consistently for read-only operations.
Four tools is well-scoped for this server's narrow purpose: upload, send, check status, and view usage. Each tool earns its place, and none feel redundant or missing as core operations.
The main workflow of upload, send, and verify delivery is fully covered, plus usage tracking. Minor gaps exist such as no ability to list past sends or manage uploaded audio, but these are not critical for the stated purpose.