The social MCP for your AI assistant. Query rich data on your business, competitors, and industry, and put the answers to work alongside everything else it knows about you.
How to connect
- 1
Open Claude Connectors
Open
Nectar in ChatGPT Install Google Antigravity
Open
Copilot in VS Code Connectors lives under Settings, in Claude desktop and on claude.ai.
Nectar is listed in the ChatGPT app directory, so there is no URL to paste.
Gemini connects to Nectar through Google Antigravity. Install it first.
Copilot's agent mode in VS Code connects to MCP servers. Update VS Code first.
- 2
Find
Nectar and connect Connect it in ChatGPT
Add
Nectar from the terminal Add
Nectar from the terminal Nectar is listed in Anthropic's directory, so there is no URL to paste.
On Nectar's page in ChatGPT, click Connect.
Run this once. It adds Nectar's server to Antigravity.
Run this once. It adds Nectar's server to VS Code.
Nectar Connect Nectar Connect agy mcp add nectar https://mcp.nectarsocial.com/mcpcode --add-mcp '{"name":"nectar","type":"http","url":"https://mcp.nectarsocial.com/mcp"}' - 3
Approve access in
Nectar Claude opens Nectar's sign-in. Authorize, then ask Claude about your accounts.
ChatGPT opens Nectar's sign-in. Authorize, then add Nectar to a chat from +.
Antigravity opens Nectar's sign-in. Authorize, then ask about your accounts.
VS Code opens Nectar's sign-in. Authorize, then ask Copilot in agent mode.
What can you ask it?
Ask in plain English. It runs the tools against your accounts and answers with the numbers cited.
FAQ
Nectar API vs Nectar MCP
The Nectar API and Nectar MCP give access to the same underlying data. They just serve different builders.
The API is built for engineers: your team writes and maintains integration code against REST endpoints, authenticated with one token per workspace. MCP is that same access built for AI agents instead of codebases. Instead of managing a token, you connect once via OAuth and grant permission, and from then on an assistant like Claude can access your Nectar data directly, with no integration code to maintain.
Nectar Agent vs Nectar MCP
Nectar Agent is Nectar's own agent. It lives inside the product as the chat, the composer, and the reporting surface. MCP runs the other direction. Nectar Agent and MCP share the same tool definitions under the hood, but MCP exposes a scoped subset of them so an assistant you already use, Claude, ChatGPT, Gemini or your own internal agent, can call them from outside Nectar's interface.
Nectar Agent is AI inside Nectar. MCP is Nectar inside your AI.
What can it actually do?
Today it reads. Search and summarize your owned content and analytics, search community mentions, run competitive listening, and list the workspaces, accounts and labels you can reach. Tomorrow it will write: publishing, replying, DMs, creator search and trends are on the roadmap, not in this release.
Who is this for?
Built for marketing, social, creator, and competitive intelligence teams and agencies who want faster, data-grounded decisions.
How is it secured?
OAuth. Admins see every authorised app in one place and can revoke access per user and per app. Revoking stops it everywhere, with nothing left connected in the background.
How is it priced?
We will take you through pricing on a call. Book a demo
See it on your
own accounts.
Connect it in Claude, ChatGPT or Gemini, or let us walk you through it.