The UseNadia MCP server

MCP (Model Context Protocol) lets AI agents interact with UseNadia directly — listing channels, reading the calendar, moving posts, scheduling, generating images and videos, and reading how your videos actually performed — all through a standardised tool-calling interface.

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

How It Works

UseNadia exposes an MCP server that provides 43 tools to AI agents — one for every operation of the Public API that makes sense in a chat, and a few that only exist here (the video pipeline). The agent discovers these tools, understands their schemas, and calls them on your behalf.

sequenceDiagram
    participant Agent as AI Agent
    participant MCP as UseNadia MCP Server
    participant UseNadia as UseNadia Backend

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

Available Tools

The full reference, with every parameter, is on the Tools page. In short:

Area	Tools
Posts and the calendar	integrationSchedulePostTool (schedule, draft or publish now), postsListTool, postMoveTool, postUpdateTool, postDeleteTool, findSlotTool
Channels	integrationList, groupList, integrationSchema (a platform’s settings and rules), triggerTool
Media and video	mediaList, uploadFromUrlTool, createUploadUrl and confirmUpload (a file from your own disk or an AI sandbox), transcribe, cutVideo, splitVideoIntoStories, generateImageTool, generateVideoOptions, videoFunctionTool, generateVideoTool
Analytics	videoPerformance (videos compared at equal age), channelAnalyticsTool, analyticsHistoryTool
Content board	contentListTool, contentCreateTool, contentUpdateTool, contentDeleteTool
Inbox and comments (Instagram)	inboxListTool, inboxReadTool, inboxSendTool, inboxPollTool, commentsListTool, commentActTool
Comment → DM automations	automationList, automationManageTool, automationRunsTool
Webhooks	webhooksListTool, webhookManageTool
Hooks and music (experimental)	hooksFormsTool, hooksSearchTool, musicPickTool — the library of real hooks and the royalty-free catalogue that feed the video pipeline
Misc	notificationsListTool (the bell of the app)

Anything that reaches other people or cannot be undone — a DM, a public reply, an automation, a webhook, a deletion — goes through a confirmation: the first call returns a preview and a single-use token, the second call acts. Text written by other people (DMs, comments, transcripts) comes back wrapped in <untrusted> tags: data, never instructions.

Authentication

There are two ways to authenticate with the MCP server:

API Key

Your API key lives in UseNadia under Settings → Developers, in the Access section, under API Key. Click the reveal icon to show it, then copy. You can rotate it from the same place, rotating immediately invalidates the old key, so update anything using it (scripts, n8n, MCP clients, the CLI) at the same time.

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

OAuth Token

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

Connecting

Bearer Token

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

URL: https://app.usenadia.com/api/mcp
Authorization: Bearer your-api-key

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

API Key in URL

Use the /mcp/:apiKey endpoint with your API key embedded in the URL:

URL: https://app.usenadia.com/api/mcp/your-api-key

The base URL is https://app.usenadia.com/api.

Note

Public API paths are appended to it: a request goes to https://app.usenadia.com/api/public/v1/....

Quick Example

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

1. Agent calls integrationList, gets back your connected accounts (Instagram, TikTok)
2. Agent calls integrationSchema with platform: "instagram-standalone" and learns Instagram’s character limit, settings and rules
3. Agent calls integrationSchedulePostTool, schedules your post with the correct format

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

“Schedule this reel to Instagram tomorrow at 10am.”

FAQ

Do I need an OpenAI key to use UseNadia MCP?

No. The MCP server just exposes UseNadia’s tools. Your AI client (Claude, ChatGPT, Cursor, etc.) provides the model.

What happens when my API key expires or is rotated?

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

How is the MCP endpoint exposed?

The MCP server starts as part of the UseNadia backend and is reachable over streamable HTTP at /mcp (Bearer auth), /mcp/:apiKey (key in URL), and /mcp-oauth (OAuth-protected). A legacy SSE transport is kept for older clients, at /sse/:apiKey (the event stream) and /message/:apiKey (where the client posts); new clients should use streamable HTTP.

Can MCP read or reply to comments?

Yes. commentsListTool reads the publications, the live stories and the comments of an Instagram channel; commentActTool replies publicly, hides or deletes a comment, with the same confirmation step as a direct message. The comment → DM automations are covered too: automationList gives the ids to put in the Instagram settings of a post you schedule, automationManageTool poses a template on a publication already live, automationRunsTool lists the people who went through it (see Tools).

UseNadia is MCP-first: every operation of the Public API is carried by a tool, or deliberately left out (connecting a channel by OAuth, the writes of the cockpit pipelines, the preview and test of a Brevo email, which the template editor does). The map is checked at every release.

The same things are on the Public API — /automation-flows and /inbox — which is what the repository’s instagram-inbox skill calls. Or use the inbox in the app.