Introduction

MCP (Model Context Protocol) lets AI agents interact with Nitty Music Social directly, listing integrations, scheduling posts, generating images and videos, clipping long videos into shorts, all through a standardized tool-calling interface.

This means you can connect Claude, ChatGPT, Cursor, or any MCP-compatible client to your Nitty Music Social account and manage your social media through natural language.

How It Works

Nitty Music Social exposes an MCP server that provides 13 tools to AI agents. The agent discovers these tools, understands their schemas, and calls them on your behalf.

sequenceDiagram
    participant Agent as AI Agent
    participant MCP as Nitty Music Social MCP Server
    participant Nitty Music Social as Nitty Music Social Backend

    Agent->>MCP: Connect with API key / OAuth token
    MCP-->>Agent: List available tools
    Agent->>MCP: Call tool (e.g., schedule post)
    MCP->>Nitty Music Social: Execute action
    Nitty Music Social-->>MCP: Return result
    MCP-->>Agent: Tool response

Available Tools

Tool	Description
`integrationList`	List all connected social media accounts (optionally filtered by group)
`groupList`	List all groups (customers) for your organization
`integrationSchema`	Get platform-specific posting rules and settings schema
`triggerTool`	Execute platform-specific helpers (e.g., list Discord channels)
`schedulePostTool`	Schedule, draft, or immediately publish posts
`postsListTool`	List the organization’s posts scheduled between two dates (with their current settings)
`postSettingsTool`	Update the provider settings of a scheduled post or draft that was not published yet
`generateImageTool`	Generate AI images for posts
`generateVideoOptions`	List available video generation options
`videoFunctionTool`	Get video generator settings (e.g., available voices)
`generateVideoTool`	Generate videos for posts
`clippingTool`	Turn a long YouTube video into captioned vertical clips and draft posts
`clippingStatusTool`	Check a clipping and get the finished clips

Authentication

There are two ways to authenticate with the MCP server:

API Key

Use it directly in the MCP endpoint URL, or as a Bearer token.

OAuth Token

If you’re building an app for other Nitty Music Social users, use OAuth2 to obtain tokens. OAuth tokens start with pos_ and work the same way as API keys.

Connecting

Bearer Token
API Key in URL

Use the /mcp endpoint with your API key or OAuth token as a Bearer token:

URL: https://social.nittymusic.com/api/mcp
Authorization: Bearer your-api-key

This method supports both API keys and OAuth tokens (prefixed with pos_).

Quick Example

Here’s what a typical interaction looks like when an AI agent uses Nitty Music Social MCP:

Agent calls integrationList, gets back your connected accounts (X, LinkedIn, etc.)
Agent calls integrationSchema with platform: "x" and learns X’s character limits, settings, and rules
Agent calls schedulePostTool, schedules your post with the correct format

All of this happens automatically when you tell your AI agent something like:

“Schedule a post to X for tomorrow at 10am: Excited to announce our new feature!”

FAQ

No. The MCP server just exposes Nitty Music Social’s tools. Your AI client (Claude, ChatGPT, Cursor, etc.) provides the model. Nitty Music Social only needs an OPENAI_API_KEY if you use Nitty Music Social’s own AI features (image generation, copilot) which are separate from the MCP tools surfaced to your client.

What happens when my API key expires or is rotated?

Nitty Music Social API keys don’t auto-rotate, but if you regenerate one in Settings → Developers → Public API, every MCP client using the old key stops working until you update its config. Update the URL or the Authorization header in your client config and reconnect.

Self-hosted: how do I expose the MCP endpoint?

The MCP server starts as part of the Nitty Music Social backend and is reachable at /mcp (Bearer auth), /mcp/:apiKey (key in URL), and /mcp-oauth (OAuth-protected). Your reverse proxy must forward these paths to the backend and support streaming HTTP (Transfer-Encoding: chunked). See Reverse Proxies.

Can MCP read or reply to comments?

Not today. The current tool set is read-only on integrations and write-only on posts/media. There is no getComments or replyToComment exposed via MCP. Comment replies must be triggered through the Nitty Music Social UI.