Summary

A tool budget of four instead of a hundred.

The trade is context for indirection: the model writes code instead of picking a tool, which means one round trip can chain several API calls that would otherwise be several. The sandbox is where to look before you trust it — no filesystem, no network, no environment variables, only `audius.request()` pinned to the Audius host, a 64MB memory cap and a 30s default timeout, with no state carried between executions.

What it is

A code-mode server for the Audius music platform. Rather than registering a tool per endpoint, it exposes a searchable index of the API and a sandbox that executes the model's JavaScript against an already-authenticated client — so the API key never enters the prompt and the tool list stays short.

What you get

`search` discovers API endpoints by tag, path, method or keyword
`execute` runs JavaScript in a QuickJS WebAssembly sandbox where the only capability is an authenticated `audius.request()` client
`play` opens a track in the Audius desktop app or the browser
`subgraph` queries on-chain protocol data — staking, governance, node registry — through The Graph

Requirements

The npm package audius-mcp-atris, version 2.4.0, either run from a clone with pnpm or launched from the compiled entry point. AUDIUS_API_KEY is required, created under Developer Apps in your Audius account settings; the API secret is only needed for write operations. GRAPH_API_KEY is optional and only the subgraph tool fails without it. Transport is streamable HTTP at POST /mcp, with PORT defaulting to 3000.

Setup effort

One command plus a key — pnpm install, then supply credentials