checksocialsNaar dashboard →
Documentation

CheckSocials connector for Claude and ChatGPT

Last updated: 6 October 2026

The CheckSocials connector is a remote MCP server that links Claude or ChatGPT to your CheckSocials account. It works in two directions:

  • Company context in. Your assistant already knows a lot about your company from earlier conversations. It can send that to CheckSocials as a proposal, so the social posts and blogs CheckSocials writes for you are based on it. Nothing changes until you approve it.
  • Content out. Your assistant can fetch blogs and posts you approved in CheckSocials and put them on your own website, for example a Next.js site on Vercel that Claude Code or ChatGPT already works in. It then reports the live URL back to CheckSocials.

1. Before you start

  • A CheckSocials account with AI connections switched on for your account
  • Claude on a plan that supports custom connectors, or ChatGPT with Developer mode available
  • For publishing to your website: a tool your assistant can use to change your site, such as Claude Code, or a GitHub or Vercel connector

Not sure whether AI connections are on for your account? Open Account > AI-koppelingen in CheckSocials, or email info@checksocials.com.

2. Connect

The connector URL is https://checksocials.com/mcp. You can also copy it from Account > AI-koppelingen in CheckSocials.

Claude

  1. Go to Settings > Connectors and choose Add custom connector
  2. Paste the connector URL and click Connect
  3. Log in to CheckSocials in the window that opens
  4. Pick the CheckSocials account the assistant may use and the permissions it gets
  5. Click Toestaan (Allow)

ChatGPT

  1. Turn on Developer mode under Settings > Plugins
  2. Go to chatgpt.com/plugins and add a plugin with the connector URL
  3. Log in to CheckSocials, pick the account and permissions, and click Toestaan

Every connection is tied to exactly one CheckSocials account. If you manage several accounts, connect again and pick the other one.

3. Permissions

On the consent screen you choose what the assistant may do. Tools that belong to a permission you did not grant are not available to the assistant.

  • Read company profile (context:read): read what CheckSocials already knows about your company
  • Propose company information (context:write): send a proposal that you approve first
  • Read content (content:read): read approved blogs and posts
  • Report publication (content:write): record the URL where a blog was published

4. Tools

Read-only

  • checksocials_ping: checks that the connector is reachable. Reads no account data
  • get_company_context: returns the company profile CheckSocials uses to write posts and blogs: description, target audiences, services, USPs, positioning, tone of voice, goals, competitors and fixed facts
  • list_blog_posts: lists finished blog articles, newest first. Drafts are not included
  • get_blog_post: returns one article in full, as Markdown and HTML, with slug, SEO title, meta description, public image URLs, FAQ and JSON-LD
  • list_social_posts: lists finished social posts: single image posts, carousels and LinkedIn text posts. Drafts are not included
  • get_social_post: returns one social post in full: caption, hashtags, call to action, public image URLs and, for carousels, every slide

Write

  • propose_company_context: sends a company profile as a proposal: description, target audience, services, USPs, tone of voice, positioning, competitors, goals, content preferences and fixed facts. It never overwrites anything directly
  • mark_blog_published: records the URL where a blog article went live, so CheckSocials knows where it is published

None of the tools delete data, and none of them post to your social media accounts.

5. Example prompts

Share your company context

“Look through our earlier conversations and what you remember about my company. Check what CheckSocials already knows first, then send a company profile to CheckSocials with target audience, services, USPs, tone of voice, positioning, competitors, goals and content preferences. Leave a field empty if you are not sure.”

Put a blog on your website

“Get the latest finished blog from CheckSocials and add it as a new page on my website. Use the slug, SEO title, meta description, images and JSON-LD from CheckSocials. Show me the change before you publish, and report the URL back to CheckSocials afterwards.”

6. Approving company information

A proposal from your assistant shows up as a banner on Over mijn bedrijf in CheckSocials. Click Bekijken to compare the current value with the proposed value for every field.

  • Choose per field what to take over. Fields you leave unticked stay unchanged
  • Fields the assistant marked as inferred or uncertain are labelled and not selected by default
  • You can undo an approval right after taking it over
  • A newer proposal replaces an older one you have not reviewed yet

7. Publishing on your own website

CheckSocials does not change or deploy your website. Your assistant does that with its own tools, such as Claude Code or a GitHub or Vercel connector, and you stay in control of what gets published. CheckSocials provides everything needed to build the page and records the URL once it is live. If CheckSocials hosts your blog for you, you do not need this.

8. Disconnect

Open Account > AI-koppelingen in CheckSocials and click Ontkoppelen next to the connection. Access stops immediately. You can also remove the connector in Claude or ChatGPT. The same page shows recent activity: which tool was called, by which assistant, and whether it succeeded.

9. Security and privacy

  • Authentication uses OAuth 2.1 with PKCE. You never share a password or API key
  • Tokens are stored as a hash. Access tokens expire after one hour, refresh tokens after 30 days at most
  • A connection can only reach the one CheckSocials account you picked
  • Your social media accounts, access tokens, statistics and payment details are not reachable through the connector
  • CheckSocials does not read your conversations or the memory of Claude or ChatGPT. It only receives what the assistant sends to the connector at your request
  • Requests are rate limited

Read the privacy policy for details on what we store and for how long.

10. Limitations

  • Company context only reaches CheckSocials when you ask your assistant to send it. It is not synced automatically
  • Only finished, approved content is available. Drafts are not
  • The connector does not publish to social media. Use CheckSocials itself for planning and posting

11. Support

Questions or problems? Email info@checksocials.com. Please mention which assistant you use and roughly when the problem happened.