MCP server

Mynahcast runs a remote Model Context Protocol server so any MCP client (Claude Code, Claude Desktop, Cursor, Codex, Gemini CLI, OpenClaw, Hermes Agent and others) can draft, validate and schedule social media posts for your brand.

Endpoint

POST https://api.mynahcast.xyz/mcp

Transport

Streamable HTTP, stateless JSON-RPC 2.0 (initialize, tools/list, tools/call)

Auth

Authorization: Bearer myn_live_… on every request. Keys never go in the URL.

Tools

Named mynahcast_*, filtered by the key's scopes. Every tool that changes data accepts dry_run.

Approvals

Agent keys can't approve. Posts from agents wait in your Approvals queue.

Discovery

/.well-known/mcp/server-card.json · /.well-known/api-catalog

Connect in three steps

1. In the app, open Agents & API → Create key and pick the Agent preset. Copy the key; it's shown once.
2. Add the server to your client with the key as a bearer header (examples below, and one page per agent in Connect agents).
3. List the tools to check the connection, then ask your agent for a post. It lands in Approvals.

Client configs

Claude Code:

claude mcp add --transport http mynahcast https://api.mynahcast.xyz/mcp \
--header "Authorization: Bearer $MYNAHCAST_KEY"

Most clients that read an mcpServers file (Cursor, Kimi Code, Manus import):

{
"mcpServers": {
  "mynahcast": {
    "url": "https://api.mynahcast.xyz/mcp",
    "headers": { "Authorization": "Bearer myn_live_…" }
  }
}
}

Raw JSON-RPC, to see the tool list:

curl -X POST https://api.mynahcast.xyz/mcp \
-H "Authorization: Bearer $MYNAHCAST_KEY" \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Tools

• mynahcast_validate_postCheck a post against every target channel without saving it
• mynahcast_create_postCreate a post for one brand, fanned out to one or more channels
• mynahcast_get_postRead one post with its per-channel delivery state
• mynahcast_list_postsList posts
• mynahcast_update_postEdit a post (an edit voids an earlier approval)
• mynahcast_reschedule_postMove a post to a new time
• mynahcast_delete_postDelete a post that hasn't gone out
• mynahcast_get_post_timelineEvery attempt, approval and read-back for a post
• mynahcast_submit_for_approvalAsk a human to approve a post
• mynahcast_decide_approvalApprove or request changes (humans only; agents are refused)
• mynahcast_list_channelsConnected channels
• mynahcast_get_channel_capabilitiesLimits for one channel (characters, media, threads)
• mynahcast_request_uploadGet a signed URL to upload media
• mynahcast_complete_uploadMark an upload as finished
• mynahcast_get_brand_voiceRead the brand's voice profile
• mynahcast_update_brand_voicePublish a new voice version (publisher keys)

OAuth and ChatGPT

Same operations over REST

Every MCP tool maps one-to-one to a REST operation under /v1, described by https://api.mynahcast.xyz/v1/openapi.json. See the API reference.