Content Handling Guide

io.github.Wxt-aiPublished by GitHub account Wxt-aiv1.0.7Updated Oct 8, 2026

Set handling guidance for a content item

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

A remote MCP server that provides handling guidance for a content item, letting an assistant set how that content should be handled.

What you can do
Set handling guidance for a content item. The server exposes a single capability: an assistant can record handling guidance tied to a specific content item. No further tools, resources or documentation are published, so the exact inputs and outputs are not described.
When to use it
Consider it only if you need an assistant to attach handling guidance to a content item and you are comfortable with an undocumented remote service. Most workflows will find no clear use for it.
Requirements
A remote streamable HTTP endpoint; no package, environment variables or headers are declared. No authentication is declared, and the endpoint is a temporary-looking cloudflare tunnel hostname, so availability is uncertain.
Before you install
No authentication is declared, so anyone with the endpoint may be able to reach it, and content details you send go to a third-party host. The service is undocumented and hosted on a temporary tunnel address, so it may disappear or change without notice.

Installation

In SourceWeft

  1. Open Content Handling Guide in the dashboard and add it to a workspace.
  2. 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.Wxt-ai%2Fcontent-handling-guide/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.

{
  "mcpServers": {
    "content-handling-guide": {
      "type": "http",
      "url": "https://openings-vote-drilling-initially.trycloudflare.com/mcp/content-handling-guide"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.7LatestSep 16, 2026

Score

28% 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

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

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