speechmatics
Server Details
Transcribe audio and video with Speechmatics speech-to-text from Claude and any MCP client.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- m190/usefulapi-mcp
- GitHub Stars
- 0
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Score is being calculated. Check back soon.
Available Tools
7 toolsspeechmatics_delete_jobDelete jobDestructiveInspect
⚠️ Permanently deletes a job and its transcript. Set force=true to delete even while it is still running. Batch API: DELETE /jobs/{job_id}.
| Name | Required | Description | Default |
|---|---|---|---|
| force | No | Delete even if the job is still running. | |
| job_id | Yes | The job id to delete. |
speechmatics_get_jobGet jobRead-onlyInspect
Get a single job's details and status (running | done | rejected | deleted | expired). Poll this until status is "done", then fetch the transcript. Batch API: GET /jobs/{job_id}.
| Name | Required | Description | Default |
|---|---|---|---|
| job_id | Yes | The job id returned by speechmatics_transcribe_url. |
speechmatics_get_job_logGet job logRead-onlyInspect
Get a job's plain-text processing log — useful for debugging a rejected job. Batch API: GET /jobs/{job_id}/log.
| Name | Required | Description | Default |
|---|---|---|---|
| job_id | Yes | The job id. |
speechmatics_get_transcriptGet transcriptRead-onlyInspect
Get a completed job's transcript. format=txt (default, human-readable) | srt (subtitles) | json-v2 (structured words, timings, speakers, translations, summary). Only works once the job status is "done". Batch API: GET /jobs/{job_id}/transcript.
| Name | Required | Description | Default |
|---|---|---|---|
| format | No | Output format. Default txt for readability; use json-v2 for structured results. | |
| job_id | Yes | The job id. |
speechmatics_get_usageGet usageRead-onlyInspect
Get usage statistics (transcription minutes) for the account over a date range. Batch API: GET /usage.
| Name | Required | Description | Default |
|---|---|---|---|
| since | No | Start date, YYYY-MM-DD. | |
| until | No | End date, YYYY-MM-DD. |
speechmatics_list_jobsList jobsRead-onlyInspect
List transcription jobs (most recent first), with status/data_name/duration. Batch API: GET /jobs.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max jobs to return. | |
| created_before | No | RFC3339 date-time; only return jobs created before this time (for pagination). | |
| include_deleted | No | Include deleted jobs in the results. |
speechmatics_transcribe_urlTranscribe audio/video from URLInspect
Submit a publicly reachable audio/video URL for speech-to-text transcription (optionally with diarization, translation, and summarization). ASYNC: returns a job id immediately — poll speechmatics_get_job until status is "done", then call speechmatics_get_transcript. Batch API: POST /jobs.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Publicly reachable audio/video URL for Speechmatics to fetch and transcribe. | |
| domain | No | Domain-specific model hint, e.g. finance. | |
| language | No | Transcription language code, e.g. en, es, de, fr. | en |
| summarize | No | If true, also produce a summary of the transcript. | |
| diarization | No | Speaker labeling: speaker (who spoke) | channel (per audio channel) | none. | |
| summary_type | No | Summary layout (when summarize=true). | |
| output_locale | No | Output spelling locale, e.g. en-US, en-GB. | |
| summary_length | No | Summary length (when summarize=true). | |
| enable_entities | No | Emit formatted entities (numbers, dates) in results. | |
| operating_point | No | Accuracy/speed tradeoff. enhanced is more accurate; standard is faster/cheaper. | |
| additional_vocab | No | Custom vocabulary — strings, or objects like {"content":"gnocchi","sounds_like":["nyohki"]}. | |
| notification_url | No | Webhook URL to POST the transcript to when the job completes. | |
| fetch_auth_headers | No | Auth headers to send when fetching a private URL, e.g. ["Authorization: Bearer xyz"]. | |
| summary_content_type | No | Summary content style (when summarize=true). | |
| translation_target_languages | No | Language codes to also translate the transcript into, e.g. ["es","de"]. |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!