MAP Audio developer resources

The MAP Audio workspace lets an MCP Apps client play a recording, inspect its waveform and spectrogram, loop a region and add timeline annotations. Connect through Streamable HTTP at https://audio.map.audio/mcp. This is a testing preview; availability in an app directory is separate.

Use open_audio_workspace to open the player, open_demo_audio for a synthetic example, or display_audio_file for a supported attachment or an existing audio ID. Playback format support depends on the browser. The hosted workspace does not generate audio or control a desktop plugin.

Imports are limited to 32 MiB and remain accessible for one hour. Anyone with the audio ID or download link can read the recording during that time. Download returns the original file.

The public API is read-only and does not require authentication. It exposes a service description at /api/public/status and the public PAM preset-pack catalog at /api/packs.json. Customer accounts, purchases, license activation, downloads, and admin routes are outside this public contract.

curl -sS https://map.audio/api/public/status
curl -sS https://map.audio/api/packs.json

Read the machine-readable OpenAPI 3.1 specification for operation IDs, parameter types, response schemas, and error objects. Clients should honor each endpoint’s HTTP cache headers.

Public API errors use JSON with a stable code, a human-readable message, a resolution hint, and a link back to these docs. An unknown endpoint returns HTTP 404. A known endpoint called with the wrong method returns HTTP 405 and an Allow header.

{
  "error": {
    "code": "not_found",
    "message": "No public API endpoint matches this path.",
    "resolution": "Use an endpoint listed in the MAP Audio OpenAPI document.",
    "docs": "https://map.audio/developers"
  }
}

Every public API response carries an API-Version header, currently 1. Send the same header to pin a request; an unknown value returns HTTP 400 with the error object above. Additive changes such as new fields or endpoints keep the version number. A breaking change ships as a new version under a new URL path prefix while the previous version keeps answering.

A retiring version or endpoint announces itself with Deprecation and Sunset response headers at least 90 days before removal, and the change is listed on this page. There are no deprecations in effect.

The PAM and MFX MCP servers are local stdio bridges. They are the right interface when an agent must load content, inspect plugin state, edit parameters, trigger notes, work with patterns, or manage presets in a plugin instance already running on the user’s computer. They are separate from the public website API and do not expose a remote control endpoint on map.audio.

• @map-audio/pam-mcp-server for PAM and development builds that need multi-product discovery.
• @map-audio/mfx-mcp-server for MFX only.

Start with llms.txt for a short MAP Audio brief and when-to-use guidance. llms-full.txt contains the longer product and support reference. agent-instructions.md explains which interface to choose and the boundaries agents should preserve. The API catalog links these resources in a machine-readable linkset.