Klangio MCP integration for AI agents.
Connect AI agents to Klangio through 9 structured actions, including download job result, create beat tracking job, and create chord recognition extended job…
- ACTION CONTRACTS
- 9
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Klangio integration exposes
The Klangio Agent App exposes 9 provider-backed actions for ai and design & media work. Its current contract lets an authorized agent download a generated klangio job result file and upload it to local transit storage, create a klangio beat and downbeat tracking job from a url or base64 audio file, and create a klangio chord recognition job with extended key detection from a url or base64 audio file. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Klangio account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Klangio capabilities.
Showing 9 of 9 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
download_job_resultREADDownload a generated Klangio job result file and upload it to local transit storage.
INPUTS: jobId / resultType
create_beat_tracking_jobWRITECreate a Klangio beat and downbeat tracking job from a URL or Base64 audio file.
INPUTS: file / webhookUrl
create_chord_recognition_extended_jobWRITECreate a Klangio chord recognition job with extended key detection from a URL or Base64 audio file.
INPUTS: file / vocabulary / webhookUrl
create_chord_recognition_jobWRITECreate a Klangio chord recognition job from a URL or Base64 audio file.
INPUTS: file / vocabulary / webhookUrl
create_source_separation_jobWRITECreate a Klangio source separation job from a URL or Base64 audio file.
INPUTS: file / model / output / webhookUrl
create_strum_recognition_jobWRITECreate a Klangio guitar strum recognition job from a URL or Base64 audio file.
INPUTS: file / webhookUrl
create_transcription_jobWRITECreate a Klangio transcription job from a URL or Base64 audio file and requested score outputs.
INPUTS: file / model / outputs / title / composer
download_source_separation_audioREADDownload a Klangio source separation stem audio file and upload it to local transit storage.
INPUTS: jobId / stemType
get_job_statusREADFetch the current processing status for a Klangio job.
INPUTS: jobId
INPUT CONTRACTS
Know what the action needs before it runs.
download_job_result
jobIdOPTIONAL- The Klangio transcription job UUID.
resultTypeOPTIONAL- A generated output requested from Klangio.
create_beat_tracking_job
fileREQUIRED- An audio file uploaded to Klangio as multipart/form-data.
webhookUrlOPTIONAL- The webhook URL Klangio should call for job updates.
create_chord_recognition_extended_job
fileREQUIRED- An audio file uploaded to Klangio as multipart/form-data.
vocabularyREQUIRED- The chord recognition vocabulary used by Klangio.
webhookUrlOPTIONAL- The webhook URL Klangio should call for job updates.
create_chord_recognition_job
fileREQUIRED- An audio file uploaded to Klangio as multipart/form-data.
vocabularyREQUIRED- The chord recognition vocabulary used by Klangio.
webhookUrlOPTIONAL- The webhook URL Klangio should call for job updates.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Download Job Result
Download a generated Klangio job result file and upload it to local transit storage. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
download_job_resultControl Create Beat Tracking Job
Create a Klangio beat and downbeat tracking job from a URL or Base64 audio file. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_beat_tracking_jobVerify with Download Source Separation Audio
Download a Klangio source separation stem audio file and upload it to local transit storage. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
download_source_separation_audioSAFETY BOUNDARY
Operate Klangio with explicit limits
- Authorize Klangio with API key and grant only the provider access required by the selected actions.
- 6 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Klangio rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Klangio task completed successfully.
CONNECTION MODEL
API key
Klangio API key sent with the kl-api-key header. Apply for API access on the official Klangio API page: https://klang.io/api/ .
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 3
- WRITE SIGNALS
- 6
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Klangio.