Noble Content Studio

io.github.thenoblesocietyPublished by GitHub account thenoblesocietyv1.1.0Updated Nov 14, 2026

Create, review and publish watch and bag listings in The Noble Society editorial demo catalog.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Creates, reviews and publishes watch and bag listings in The Noble Society editorial demo catalog.

What you can do
  • Create watch and bag listings in the demo catalog
  • Review existing listings before they go out
  • Publish listings to the catalog
  • No tool list, instructions or README is supplied, so the exact operations and their inputs are not documented here.
When to use it
Worth considering if you work with The Noble Society editorial demo catalog and want an assistant to draft, check and publish watch or bag listings without switching tools.
Requirements
A remote endpoint at content.thenoblesociety.workers.dev, or the npm package @thenoblesociety/content-mcp run locally over stdio. OAuth authentication is required. No environment variables or headers are declared.
Before you install
Publishing changes the state of a live catalog, so review drafts before letting an assistant publish. OAuth grants the server access to your account; check which scopes it requests. The catalog is described as a demo, so treat its data accordingly.

Installation

In SourceWeft

  1. Open Noble Content Studio in the dashboard and add it to a workspace.
  2. Connect the required 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.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.thenoblesociety%2Fnoble-content/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "noble-content-studio": {
      "type": "http",
      "url": "https://content.thenoblesociety.workers.dev/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.1.0LatestNov 14, 2026

Score

60% 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
  • 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.

  • License10 pts

    Declare a license in the repository or the registry entry.