Skip to main content

Connect an AI Assistant to Your Social Media With MCP, Step by Step

Add your Blendin MCP address to an AI assistant, sign in with OAuth, choose scopes, run a dry run and widen access safely, with you in control through scopes.

By The Blendin team7 min read
Overprint cover: a violet hub connected to four nodes on a dark block, with the words Plug in your assistant.

Imagine asking an assistant, in plain words, “What is on my calendar this week, and which day is empty?” and getting an answer from your real schedule. Or asking it to draft a post in your brand voice, run a dry run and tell you what would be published. That is what MCP makes possible, and it takes about ten minutes to set up. This guide walks through it, and it keeps you in control at each step.

What you are actually connecting

MCP is an open standard for letting an AI assistant use tools in another service. Blendin runs an MCP server that speaks over Streamable HTTP and signs you in with OAuth 2.1, with discovery, dynamic registration, PKCE and rotating refresh tokens, so you never paste a password. The assistant gets a scoped key behind the scenes, and that key can do only what the scopes allow. Think of the scopes as the buttons you choose to hand over.

Before you start

  • A Blendin account on any plan, Free included.
  • At least one connected account, so there is something to read.
  • An AI assistant that supports MCP servers or custom connectors.
  • Five minutes to decide what you want it to do first.
The framework
The scope ladder: crawl, walk, run
  1. 1Look
    Untick publish when you sign in so the connection is read only (accounts:read, plus the calendar and brand kit resources). Ask questions, change nothing.
  2. 2Draft
    Add the generate scope so the assistant can draft in your brand kit. Drafts use your plan's monthly pieces, the same as in the app. Keep publish off while you check them.
  3. 3Dry run
    Use publish with a dry run to see exactly what would go out. A dry run never publishes.
  4. 4Schedule
    Switch publish on once the dry runs look right. From then on the assistant can schedule or publish when you ask, so keep the requests specific.
  5. 5Answer
    Opt in to comments or inbox scopes last, and only if you want the assistant near conversations.

Move one rung at a time and stay on a rung until it feels boring.

Step 1: find your MCP address

Open the avatar menu in the Blendin app and choose Developers (on a phone, More, then Developers). The MCP section shows the address of the server, which ends in /api/mcp, and a second address for assistant directories. Copy the first one. You do not need a key for this route, because the sign in is OAuth. If you would rather call the API directly from your own code, the Developers area also mints scoped keys that start with bln_live_ and stores them hashed.

Step 2: add it in your assistant

The menu names differ between assistants, so look for the setting that adds a custom connector, an integration or an MCP server. Paste the address, give it a name you will recognise, and save. The assistant discovers the connection details itself, which is what OAuth discovery does, and opens a Blendin sign in window.

Step 3: sign in and pick scopes

Sign in to your Blendin account and read the scope list before you approve. By default a connection gets publish and accounts:read. Every other scope is opt in, so nothing about your inbox, analytics or comments is shared unless you tick it. If you only want to look around today, untick publish.

Step 4: ask a harmless question first

Start with something that changes nothing, and confirm the answer matches reality. The calendar and your brand kits are exposed as resources, and there is a ready made prompt called plan_my_week.

First prompts to try

  • You: Which of my accounts are connected, and which networks are they on?
  • You: Show what is on my calendar this week and tell me which day is empty.
  • You: Run plan_my_week and suggest three posts in my brand voice. Do not publish anything.
Three read only prompts. If the assistant answers from your real data, the connection works.

Step 5: run a dry run before you trust it

Before you allow real scheduling, ask the assistant to prepare a post as a dry run. A dry run goes through the same checks as a real publish and reports what would happen, but it never publishes. Read the result the way you would read a post in the scheduler: the network, the account, the time, the caption. When you see two or three clean dry runs in a row, widen access.

Step 6: widen access slowly

Each new scope is a decision. Add one, use it for a week and see how it behaves. A good order follows the ladder above: generate, then dry runs, then scheduling, then comments. Skip inbox access unless you want an assistant reading conversations. If a scope never gets used, take it away. You can revoke a connection or a key at any time from the Developers area, and keys are stored hashed, so a lost key can be cut off without exposing anything.

What it is good for, honestly

An assistant is good at the parts of social media that are organisational: finding the empty day, suggesting a week of ideas in your brand voice, checking a caption against your last posts, turning a long note into three post drafts. It is not a replacement for your judgment about what to say. Keep your hand on the scopes, and ask for drafts instead of finished posts. If you want to go further with code, the API page covers the publishing endpoint, dry runs, scheduling, cancel and idempotency keys, and signed webhooks.

If something does not work

  • The assistant cannot find the server. Check that you copied the full address, including the part after the domain.
  • The sign in window opens and closes. Try again signed in to the right Blendin account in the same browser.
  • A tool is missing. It is probably a scope you did not grant. Reconnect and tick it, or use the directory address if you expected a generative tool, because that address leaves them out.
  • It says you are going too fast. The limit is 120 requests a minute across every key and connection. Ask for fewer things at once.
Safe setup checklist
  • I connected through OAuth, not a pasted key.
  • I approved the smallest set of scopes that does the job.
  • My first prompts were read only, and the answers matched my real data.
  • I ran a dry run before allowing any scheduling.
  • I know where to revoke the connection in the Developers area.
  • I know publish is a default scope, and I unticked it until I wanted the assistant to publish.

Frequently asked questions

What is MCP?

MCP, the Model Context Protocol, is an open standard that lets an AI assistant use tools and read data from another service through a defined connection. For Blendin it means an assistant can look at your calendar, your brand kits and your accounts, and take the actions you allow, from a chat.

Do I need a paid plan?

No. MCP over OAuth works on every plan, Free included. Hand made API keys follow your plan instead: Free has none, Creator allows 2, Pro 5 and Business 10. If you sign in through OAuth you do not need a key at all.

Can the assistant post without my say so?

Yes, if the publish scope is on, which it is by default: an assistant with that scope can publish or schedule when you ask it to, without a further click from you. A dry run never publishes. Untick publish when you sign in and the assistant is read only. Approval in the Blendin app is a different path: in Create and the scheduler you press the button yourself. Through MCP, your control is the scopes you grant, dry runs and a connection you can revoke at any time from the Developers area.

Which scopes are on by default?

Two: publish and accounts:read. Every other scope is opt in, including inbox, brand kits, analytics, comments, generate, library, Lead Flows, Link in bio and webhooks, plus the broad read and write scopes. Start with the smallest set that does the job.

What is the directory endpoint?

A second MCP address that serves every tool except the generative ones. It exists for assistant directories, which should not expose tools that create content. The standard address serves the full tool set allowed by your scopes.

Are there limits?

Yes. The API and MCP allow 120 requests a minute per account, counted across every key and MCP connection together. Webhooks are signed and retried, and counts of keys and webhooks depend on your plan.

If you are planning content for your assistant to arrange, start with scheduling a month in one sitting, and keep voice and colours consistent with your brand kit.