work.noice/noice-work MCP Server
This MCP server operates one Noice.work site and provides role-scoped tools for working with content, media, workflows, and publishing. Its purpose is to connect those capabilities to an MCP client so developers can manage Noice.work tasks through structured tool calls.
🛠️ Key Features
- Operates one Noice.work site
- Role-scoped tools
- Tools cover content, media, workflows, and publishing
🚀 Use Cases
- Managing Noice.work content through MCP tools
- Handling Noice.work media assets
- Running or updating workflow steps
- Publishing content via the server’s publishing tools
⚡ Developer Benefits
- Focused scope on a single Noice.work instance
- Clear separation of supported areas: content, media, workflows, publishing
- Role-scoped access via the server’s tool set
⚠️ Limitations
- Limited to one Noice.work site (as stated)