Skip to content

MCP Server Overview

Server URL: https://mcp.nuelink.com/mcp Transport: Streamable HTTP Protocol: 2025-06-18

The Nuelink MCP Server lets you publish posts, manage media, build collections and automations, 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.”

Six new tools, 24 in total. You can now edit a collection, add or remove its channels, add or delete its time slots, and pause or activate an automation. nuelink_update_post can also change a post’s caption.

OAuth is still the path for new integrations, as it has been since 1.2. Configure https://mcp.nuelink.com/mcp without a credential in the URL. The api_key query parameter is deprecated: it still works so existing connections don’t break, but it shouldn’t appear in new setups. See Authentication for the migration.

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

APIMCP ServerCLI
ForDevelopers writing codeAnyone using an AI assistantTerminal and CI users
InterfaceHTTP requestsNatural languageShell commands
Best forCustom apps, automations, integrationsDrafting, scheduling, day-to-day postingScripts, pipelines, one-off ops
AuthAPI key in Authorization headerOAuth; deprecated query-key compatibility for migrationAPI key via flag, env var, or saved config

You can use all of them. MCP tools map to the underlying REST operations, while MCP adds its own transport, OAuth, session, and protocol envelopes.

Twenty-four tools cover the full publishing workflow:

  • Identify yourself: confirm which Nuelink account is connected, and that its token is still valid.
  • Browse your workspace: list brands and the connected channels inside each.
  • Browse your collections: see the collections in a brand, the default channels each one publishes to, and its weekly queue slots.
  • Read the schedule: see every time slot in a brand’s week, across all its collections.
  • Create and edit collections: set up a new content folder with its channels and weekly queue, then rename it, pause it, add or remove channels, or change its time slots, without leaving the chat.
  • Browse, create, and pause automations: see which feeds are importing content, point a new automation at an RSS feed, YouTube channel, Shopify store, or another supported source, and pause or activate one.
  • Browse and upload media: list what’s in a brand’s library, or push new images, videos, and PDFs into it.
  • List posts: see what’s queued, scheduled, drafted, or published, in one collection or across a brand, filtered by state, type, or date.
  • Create posts in four modes:
    • Queue: 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.
  • Change a post: edit its caption, reschedule it, put it back in the queue, move it to the front or back of the queue, or turn it back into a draft.
  • Move posts: send up to 100 posts to another collection in the same brand.
  • Delete posts: when the account owner has allowed sensitive actions.
  • Review results: see what went out to each channel, whether anything failed, and how each post performed: likes, comments, shares, views, saves, engagement, clicks, impressions, and reach, depending on what each platform reports.

Eleven tools are read-only (get_me, validate_token, get_schedule, and the eight list_* tools) and thirteen write (create_collection, update_collection, add_collection_channel, remove_collection_channel, add_collection_queue_slot, delete_collection_queue_slot, create_automation, update_automation_status, upload_file, create_post, update_post, move_posts, delete_post). That split is the basis for the permission recommendations in Available Tools.

Worth knowing before you build on this:

  • A post’s media and options can’t be edited from a prompt, and polls can’t be edited at all. Change them in the dashboard.

If you’re evaluating the server, or writing a system prompt around it, this is the behavior worth enforcing:

  1. Resolve the brand and collection by name instead of guessing IDs.
  2. Show the chosen collection’s channels before any non-draft post.
  3. Default ambiguous publishing requests to DRAFT.
  4. Require explicit intent for QUEUE, SCHEDULE, and IMMEDIATE.
  5. Confirm the brand’s timezone before scheduling.
  6. Confirm the feed and collection before creating an automation, which keeps running afterwards.
  7. Read the resource back with a list tool after creating or changing it.
  8. Name the exact post before updating, moving, or deleting it, and prefer turning a post back into a DRAFT over deleting it.
  9. Show the destination collection’s channels before moving posts into it.
  10. Name the exact collection before changing its channels or time slots: both change where and when its posts go.

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
├── Automations (feeds that create posts for you)
└── Media (the brand's image and video library)

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.