Mynahcast

xyz.mynahcastPublished by mynahcast.xyzOfficial publisherv1.0.0Updated Oct 27, 2026

Agent-first social scheduler: drafts in your brand voice via MCP, human approval, verified posts.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Remote MCP endpoint for Mynahcast, an agent-first social scheduler that lets an assistant draft brand-voice posts for human approval.

What you can do
  • Draft social media posts in your brand voice through the MCP connection.
  • Route drafts into a human approval step before anything is published.
  • Work with verified posts in the Mynahcast scheduling app.
  • No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Useful when you want an assistant to prepare social media content in a consistent brand voice while a person still reviews and approves each post before it goes out.
Requirements
A remote MCP endpoint at the provider's API host, reached over streamable HTTP. A Mynahcast account and an API key created in the app under Agents & API, sent as a bearer token in the Authorization header.
Before you install
The connection requires a Mynahcast API key in the Authorization header; treat it as a secret and keep it out of shared logs. Drafts are intended for human approval, so review content before it is published. Post content is sent to the Mynahcast service.

Installation

In SourceWeft

  1. Open Mynahcast 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.

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/xyz.mynahcast%2Fmynahcast/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": {
    "mynahcast": {
      "type": "http",
      "url": "https://api.mynahcast.xyz/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

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.0LatestOct 23, 2026

Score

67% 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.

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