Skip to content
Nuelink Nuelink Nuelink Docs

Nuelink API/MCP Changelog

1.1.0-alpha (2026-05-12)

Section titled “1.1.0-alpha (2026-05-12)”
Section titled “Introducing the Nuelink MCP Server.”

You can now connect Nuelink to Claude, ChatGPT, Cursor, Manus, Codex, Cline, and any other MCP-compatible AI assistant. Instead of writing code against the REST API, 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 shipped

Section titled “What shipped”
  • MCP server endpoint: https://mcp.nuelink.com/mcp
  • Two auth methods: API key as a query parameter (?api_key=YOUR_API_KEY) or as a bearer token in the Authorization header. Same key as the REST API.
  • Six tools, each mapping 1:1 to an existing API endpoint:
    • nuelink_get_me → GET /me
    • nuelink_list_brands → GET /brands
    • nuelink_list_collections → GET /brands/{id}/collections
    • nuelink_list_channels → GET /brands/{id}/channels
    • nuelink_create_post → POST /brands/{id}/collections/{id}/posts
    • nuelink_upload_file → POST /brands/{id}/media
  • Public-URL media support: in addition to uploaded files, you can pass Google Drive, Dropbox, OneDrive, Unsplash, or any other publicly accessible URL directly into the post’s media array, no upload step needed.

Docs

Section titled “Docs”
  • New MCP Server section with Overview, Quick Start, Authentication, Available Tools, and Example Prompts.
  • Rewritten Introduction with two-surface framing (API + MCP).

Underlying API

Section titled “Underlying API”

No breaking changes to the REST API. The MCP server is a thin wrapper over the same public endpoints; anything you can do via MCP, you can also do via the API, and vice versa.

1.0.0-alpha (2026-04-21)

Section titled “1.0.0-alpha (2026-04-21)”
  • Initial alpha release.
  • Endpoints included:
    • GET /me
    • GET /brands
    • GET /brands/{id}/collections
    • GET /brands/{id}/channels
    • POST /brands/{id}/media
    • POST /brands/{id}/collections/{id}/posts

Known gaps in alpha

Section titled “Known gaps in alpha”

The following are explicitly not available in the alpha and are planned for later releases:

  • Listing, updating, or deleting posts (GET /posts, PATCH /posts/{id}, DELETE /posts/{id}).
  • Retrieving analytics or post performance.
  • Webhooks for publish success / failure events.
  • Targeting a subset of channels within a collection (today, posts go to all channels in the collection).
  • Listing or deleting previously uploaded media.
  • Per-platform caption or comment customization (caption and auto-comment are global; non-content options like Instagram collabs and YouTube tags can be set per platform).
  • Per-channel publishing status in the create-post response (check the Nuelink dashboard for delivery status).

If any of these are blockers for your integration, let us know and we’ll prioritize accordingly.

Feedback

Section titled “Feedback”