Skip to content

MCP Quick Start

Connect the Nuelink MCP server to your AI assistant, then queue your first post by asking for it.

You’ll need:

  • A Nuelink account with at least one brand and one collection set up.
  • A Nuelink API key. Generate one from Settings → API in your dashboard.
  • An AI assistant that supports MCP: Claude, ChatGPT, Cursor, Manus, Codex, Cline, or any other MCP-compatible client.

The base MCP URL is:

https://mcp.nuelink.com/mcp

You authenticate in one of two ways, pick whichever your client supports best:

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

Option 2: Bearer token in the Authorization header

Section titled “Option 2: Bearer token in the Authorization header”
(when your client supports custom headers)
Section titled “(when your client supports custom headers)”
URL: https://mcp.nuelink.com/mcp
Header: Authorization: Bearer YOUR_API_KEY

The API key is the same one used for the REST API if you already have one, reuse it. Generate or manage keys from Settings → API.

Pick your client below. The shape is the same everywhere: paste the MCP URL (with your key embedded or as a header), then approve the tools.

  1. Open Settings → Connectors.
  2. Click Add custom connector at the bottom of the list.
  3. Set Name to Nuelink and Remote MCP server URL to https://mcp.nuelink.com/mcp?api_key=YOUR_API_KEY.
  4. Click Add, then open the connector and approve the six Nuelink tools.

If you prefer editing the config file directly, add this to claude_desktop_config.json:

{
"mcpServers": {
"nuelink": {
"type": "sse",
"url": "https://mcp.nuelink.com/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}

Or use the query-param form:

{
"mcpServers": {
"nuelink": {
"type": "sse",
"url": "https://mcp.nuelink.com/mcp?api_key=YOUR_API_KEY"
}
}
}

Restart Claude Desktop after editing the file.

  1. Open Settings → Connectors → Advanced and toggle Developer mode on (required to add custom MCP servers).
  2. Back on the Connectors screen, click Create.
  3. Set the Name to Nuelink, MCP Server URL to https://mcp.nuelink.com/mcp?api_key=YOUR_API_KEY, and Authentication to No authentication (the key is in the URL).
  4. Save and approve the tools.

Add this block to ~/.cursor/mcp.json (or your workspace’s .cursor/mcp.json). Either auth method works:

{
"mcpServers": {
"nuelink": {
"type": "sse",
"url": "https://mcp.nuelink.com/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}

Or, with the key in the URL:

{
"mcpServers": {
"nuelink": {
"url": "https://mcp.nuelink.com/mcp?api_key=YOUR_API_KEY"
}
}
}

Restart Cursor. The Nuelink tools will appear in the MCP panel.

  1. Open Settings → MCP Servers → Add server.
  2. Set the Name to Nuelink and the URL to https://mcp.nuelink.com/mcp?api_key=YOUR_API_KEY.
  3. Click Save. The six tools become available in your Manus workspace.

Add Nuelink to your Codex MCP configuration (typically ~/.codex/mcp.json or via Settings → MCP). Either auth method works:

{
"mcpServers": {
"nuelink": {
"type": "sse",
"url": "https://mcp.nuelink.com/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}

Any client that supports remote MCP servers over HTTP works the same way, point it at https://mcp.nuelink.com/mcp and pass your API key either as the api_key query param or as a bearer token in the Authorization header.

Once connected, ask your assistant:

“Which Nuelink account am I signed in as?”

It should call nuelink_get_me and respond with your account email and plan. If you see that, you’re set.

You don’t need to memorize tool names just describe what you want. Here’s the simplest path from zero to a queued post.

“List my Nuelink brands and the collections in each one.”

The assistant calls nuelink_list_brands and nuelink_list_collections, then summarizes what it found. Pick the collection you want to post to.

If you want to include media, either paste the image directly into the chat or point the assistant at a local file:

“Upload /Users/me/Desktop/launch.jpg to my Fernwood Botanicals brand.”

The assistant calls nuelink_upload_file and gets back a media ID it’ll remember for the next step.

“Add this to the queue for my ‘Product Launches’ collection, with the caption ‘New season, new scents 🌿 Available Friday.’ Use the image I just uploaded.”

The assistant calls nuelink_create_post with publishMode: QUEUE. The post lands in the collection’s next available time slot, ready to publish to every channel that collection is configured for.

The same prompt pattern works for all four modes. State your intent and the assistant picks the right publishMode:

You say…Mode used
”Add this to the queue…” / “Queue this for me…”QUEUE (default)
“Schedule this for Friday at 9am…”SCHEDULE
”Save this as a draft” / “Don’t publish yet, just save it”DRAFT
”Post this right now” / “Publish immediately”IMMEDIATE

Drafts are especially handy when working with an assistant, let it write and refine the caption with you, save as draft, then review and approve in the Nuelink dashboard before anything goes live.

Scheduled times are interpreted in the brand’s timezone (set in the Nuelink dashboard, not your computer’s local time). If you say “Friday at 9am,” the assistant uses 9am Friday in whatever timezone that brand is configured for. Mention a timezone explicitly if you want to be safe: “Friday at 9am Casablanca time.”