searchLABSCO 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
searchdiscovers API endpoints by tag, path, method or keywordexecuteruns JavaScript in a QuickJS WebAssembly sandbox where the only capability is an authenticatedaudius.request()clientplayopens a track in the Audius desktop app or the browsersubgraphqueries 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
Build from source — git clone https://github.com/glassBead-tc/audius-mcp-atris.git
USE CASES
01
Answering a question the API has no single endpoint for
Search for the endpoints, then chain them in one sandboxed script instead of several round trips.
02
Finding an artist and their best-performing tracks
Look the user up, then pull their tracks sorted by plays — two calls inside one execution.
03
Checking on-chain protocol state
Query staking and governance figures through the subgraph rather than the content API.
04
Listening to what you just found
Hand a track straight to the desktop app or the browser from the conversation.
4 tools
Listed in project docs. Your client may show a different list.
executeplaysubgraphBEFORE YOU INSTALL
What to know first
Tools you get
4 tools named in the project's documentation.
Requires
AUDIUS_API_KEY in your environment
Optional
GRAPH_API_KEY in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
This one is built from source rather than installed with a single command.
Server setup
TERMINAL
git clone https://github.com/glassBead-tc/audius-mcp-atris.git
cd audius-mcp-atris
pnpm installPut your Audius API key (created under Developer Apps at https://audius.co/settings) in .env:
TERMINAL
echo 'AUDIUS_API_KEY=<YOUR_AUDIUS_API_KEY>' > .envBuild and start the server — it listens at http://localhost:3000/mcp; add GRAPH_API_KEY to .env too if you want the subgraph tool:
TERMINAL
pnpm devMCP Clients
Claude Code
CLAUDE CODE · JSON
{
"mcpServers": {
"audius-mcp": {
"type": "http",
"url": "http://localhost:3000/mcp"
}
}
}
