Noice.work

work.noicePublished by noice.workv1.0.0Updated Oct 25, 2026

Operate one Noice.work site with role-scoped tools for content, media, workflows, and publishing.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowFiles & Storage

Overview

AI-generated overview

A remote MCP server that lets an assistant operate a single Noice.work site: content, media, workflows and publishing, using a role-scoped management key.

What you can do
Manage content on one Noice.work site through role-scoped tools, including creating and editing items and publishing them live. Handle media assets associated with the site. Run and manage workflows defined on the site. All actions are limited to the single site the key belongs to and to the permissions that key carries.
When to use it
Use it when you run a Noice.work site and want an assistant to draft, edit, publish or organize its content and media, or to drive its workflows, without switching to the site's own interface.
Requirements
A remote endpoint at the site's own address, reached over streamable HTTP. A Noice.work management key, sent as a bearer token in the Authorization header; the key is scoped to one site and to a role.
Before you install
The management key grants write and publish access to a live site, so treat it as a secret and store it only in the client's header configuration. Publishing and workflow actions change public-facing content; review them before letting an assistant run them unattended. Scope the key to the narrowest role that still does the job.

Installation

In SourceWeft

  1. Open Noice.work in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

39% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.