audius-mcp-dev

Extend and maintain the Audius MCP server for LLM access to Audius APIs.

5|2|Updated Feb 1, 2025
One-click install
npx skills add https://github.com/glassBead-tc/audius-mcp-atris --skill audius-mcp-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audius-mcp-dev
Source: https://github.com/glassBead-tc/audius-mcp-atris/tree/main/.claude/skills/audius-mcp-dev
Command: npx skills add https://github.com/glassBead-tc/audius-mcp-atris --skill audius-mcp-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Developers extend and maintain the Audius MCP server to provide LLMs with controlled access to Audius and Open Audio Protocol APIs via the two meta-tools: search and execute. This skill frames the MCP as an extensible, production-grade platform for building, testing, and evolving agent interactions with web APIs.

Core Features & Use Cases

  • Architecture overview: an Effect-TS service layered server that wires API discovery, sandboxed execution, spec loading, and transport.
  • Tooling and patterns: guidance on how the MCP wires AppConfig, SpecLoader, SpecIndex, AudiusClient, and tool handlers to compose a robust runtime.
  • Use cases: adding new tools, extending the sandbox, updating the transport layer, or modifying the spec loader within the audius-mcp-atris codebase.
  • References: extensive in-repo references to guide development in this skill.

Quick Start

Begin by exploring the audius-mcp-atris codebase and starting the development server to experiment with MCP components.

Frequently Asked Questions about audius-mcp-dev

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add new tools to an MCP server using Effect-TS?

To add new tools to an MCP server using Effect-TS, you extend the Audius MCP architecture by wiring new tool handlers into the layered service, ensuring they compose with AppConfig, SpecLoader, and AudiusClient for a robust runtime.

How does sandboxed execution work in an MCP server for LLM API access?

Sandboxed execution in an MCP server uses a QuickJS environment to provide deterministic execution, enabling safe LLM access to Audius and Open Audio Protocol APIs while enforcing strict tool-level error handling.

Can I use TypeScript to build an extensible MCP server for web APIs?

Yes, you can use TypeScript to build an extensible MCP server for web APIs by leveraging Effect-TS to wire API discovery, spec loading, and transport layers into a production-grade platform for agent interactions.

What is the best way to update the spec loader in an Audius MCP codebase?

The best way to update the spec loader in an Audius MCP codebase is to modify the SpecLoader and SpecIndex components within the audius-mcp-atris repository, ensuring they correctly feed API discovery into the layered server runtime.

Why does my MCP server need tool-level error handling for web API interactions?

Your MCP server needs tool-level error handling for web API interactions to maintain safe, controlled LLM access, preventing unhandled exceptions during sandboxed execution from breaking the deterministic runtime environment.

Does the Audius MCP server support the latest MCP protocol?

Yes, the Audius MCP server enforces MCP protocol 2025-11-25, ensuring that tool development, spec loading, and sandboxed execution comply with the latest standard for LLM-to-web-API communication.