Skip to content
Nuelink Nuelink Nuelink Docs

MCP Server Overview

MCP Server

Section titled “MCP Server”

Server URL: https://mcp.nuelink.com/mcp?api_key=YOUR_API_KEY

The Nuelink MCP Server lets you publish posts, manage media, and browse your brands from any AI assistant that supports the Model Context Protocol including Claude, ChatGPT, Cursor, Manus, Codex, and Cline.

Instead of writing code against the REST API, you describe what you want in plain English and the assistant calls the right tools for you:

“Queue this product photo to my Product Launches collection, with the caption I just wrote.”

API or MCP, which should you use?

Section titled “API or MCP, which should you use?”

Both surfaces talk to the same Nuelink account and the same underlying endpoints. The right one depends on who’s driving:

APIMCP Server
ForDevelopers writing codeAnyone using an AI assistant
InterfaceHTTP requestsNatural language
Best forCustom apps, automations, integrationsDrafting, scheduling, day-to-day posting
AuthAPI key in Authorization headerSame API key, passed as a query param on the MCP URL

You can use both. The MCP server is a thin wrapper around the public API.

What you can do with it

Section titled “What you can do with it”

The current alpha exposes six tools that cover the core publishing workflow:

  • Identify yourself: confirm which Nuelink account is connected.
  • Browse your workspace: list brands and the connected channels inside each.
  • Browse your collections: see the collections in a brand, their default channels, and their queue settings.
  • Upload media: push images and videos to a brand’s media library.
  • Create posts in four modes:
    • Queue (recommended default): adds the post to the collection’s next available time slot. Set up your weekly schedule once, and every queued post just slots in.
    • Schedule: publish at a specific date and time, interpreted in the brand’s timezone.
    • Save as Draft: save the post without publishing or scheduling. Useful when you want to review in the dashboard before anything goes live.
    • Publish immediately: push it out right now.

Listing, editing, and deleting existing posts will arrive in a later release, matching the API roadmap.

How the pieces fit together

Section titled “How the pieces fit together”

The MCP server inherits Nuelink’s hierarchy. A quick refresher:

Account
  └── Brand (e.g. "Fernwood Botanicals")
        ├── Channels     (Instagram, X, TikTok, ...)
        └── Collections  (content folders with default channels and a weekly queue)
              └── Posts

When you ask the assistant to publish something, it picks a brand, picks a collection inside that brand, and creates the post there. The collection decides which channels the post goes to, you don’t pick channels directly.

If you’re new to this structure, the Introduction page has a fuller breakdown.

Next steps

Section titled “Next steps”