Nectar MCP: your social data, inside the AI tools your team already uses

Today we are launching Nectar MCP, a Model Context Protocol server that lets an AI assistant read your Nectar workspace directly. Connect once with OAuth and the assistant can answer questions about your content, community, account performance and the competitors you track, sourced from the same data you see in the Nectar dashboard.

Marketing and growth teams increasingly want their AI tools, not only their dashboards, to understand their brand’s social presence. Until now that meant one of two things: working inside Nectar’s own interface, or asking an engineering team to mint API tokens, write integration code and maintain it. For agencies and multi-brand groups it also meant a separate token for every client workspace. MCP removes both. One connection covers every workspace you already have access to, so a team running twelve client accounts is not managing twelve tokens.

What you can ask it

Once the connection is live, you ask your assistant instead of opening a report:

• “What were our top Instagram posts last month, and why did they outperform?”
• “What are people saying about us compared with Competitor X this week?”
• “Summarise engagement across all our channels this week.”
• “Which competitor gained the most share of voice in the last 30 days?”

Nectar MCP exposes 16 tools, all read-only. You never call them by name: your AI assistant picks the ones it needs. This is the whole surface.

Your own content

• Owned content search: the posts you published from your connected accounts, with per-post metrics and the labels you applied.
• Owned content summary: the same set as totals and averages instead of the posts themselves, overall and per platform.
• Account metrics: account-level performance, including engagements, reach, views, followers, EMV and engagement rates.

Your community

• Community content search: user-generated content and mentions, including brand tags, story mentions and untagged posts, with sentiment, the creator and their follower count.
• Community content detail: everything the search returns for one post, plus the platform’s own id, language and total engagements.
• Community sentiment summary: totals and counts broken down by sentiment, platform, surface and source type.

Your competitors

• Competitor summary: headline metrics over a date window, overall and per competitor, with earned share of voice.
• Competitor comparison: competitors side by side on the metrics you choose.
• Competitor trend: those metrics over time, bucketed by day, week or month.
• Competitor content search: the posts behind the numbers.

Finding what to filter on

• Available workspaces, accounts, labels, products, competitors and competitor groups: six tools that list what your workspace has, so the assistant can resolve names to ids without asking you for them.

Connecting, and who can see what

The server is at https://mcp.nectarsocial.com/mcp. It is the same address for everyone, with no workspace-specific value to look up and no client secret to copy. In Claude, add it under Settings, Connectors then Authorize for OAuth access. Setup takes about a minute and needs no developer. This release is read-only: the connection can read your workspace and cannot post, reply or change anything in it.

Availability

Nectar MCP is available now to customers on our Premium tier. Book a demo to learn more.

To see it running, visit nectarsocial.com/mcp. Full tool-by-tool documentation lives in the Nectar docs.