Skip to content
Nuelink Nuelink Nuelink Docs

MCP Server Overview

Server URL: https://mcp.nuelink.com/mcp Transport: Streamable HTTP Server version: Nuelink MCP Agent v1.1.0 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.”

What changed in 1.3.0-alpha

Section titled “What changed in 1.3.0-alpha”

Six new tools, 17 in total. You can now reschedule, re-queue, or draft a post, delete one, list posts across a whole brand, read the weekly schedule, check the connection, and see what was published, with likes, comments, and shares.

nuelink_create_automation takes renamed fields: name, type, title, and caption. See Available Tools.

OAuth is still the path for new integrations, as it has been since 1.2.0-alpha. 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.

Which surface should you use?

Section titled “Which surface should you use?”

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.

What you can do with it

Section titled “What you can do with it”

Seventeen 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 collections: set up a new content folder with its channels and weekly queue, without leaving the chat.
  • Browse and create automations: see which feeds are importing content, and point a new automation at an RSS feed, YouTube channel, Shopify store, or another supported source.
  • 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’s timing: 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.
  • Delete posts: when the account owner has allowed sensitive actions.
  • Review results: see what went out to each channel, whether anything failed, and the likes, comments, and shares each post earned.

A post’s content can’t be edited from a prompt: change the caption or media in the dashboard.

Eleven tools are read-only (get_me, validate_token, get_schedule, and the eight list_* tools) and six write (create_collection, create_automation, upload_file, create_post, update_post, delete_post). That split is the basis for the permission recommendations in Available Tools.

Current limitations

Section titled “Current limitations”

Worth knowing before you build on this:

  • The OAuth lifecycle is not fully certified. Discovery, dynamic client registration, and the S256 PKCE authorization handoff are operational and verified. The complete logged-in consent, code-exchange, access-token, refresh, and revocation lifecycle still needs final acceptance certification. Report any failure at the login, callback, token, refresh, or revocation stage.
  • The api_key query parameter is deprecated, and remains available only for migration.
  • Session termination is defective. An MCP session DELETE can return HTTP 500 with Cloudflare Worker Error 1101. Treat the session as not cleanly terminated; avoid repeated termination retries and report reproducible cases.

Tool discovery metadata is not a limitation: the live tools expose titles, descriptions, input schemas, output schemas, and safety annotations. The Available Tools page adds workflow guidance and examples.

What a careful assistant does

Section titled “What a careful assistant does”

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 or deleting it, and prefer moving a post back to DRAFT over deleting it.

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
        ├── 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.

Next steps

Section titled “Next steps”