Use Beacon from Claude or ChatGPT

Connect your Beacon account to Claude or ChatGPT to draft posts in your brand's voice, queue your own text, and check what is scheduled. Everything waits in Beacon for a person to approve.

The connector is being switched on account by account and is not available to every Beacon account yet. If, after you sign in, Beacon shows a “404: This page could not be found” page (or Claude or ChatGPT shows its own connection error), it is not switched on for your account yet; email support@1humanleft.com.

What the connector does

The Beacon connector lets Claude or ChatGPT work with your Beacon account while you chat. You can ask it to write a post in a brand's trained FingerPrintâ„¢ voice, save text you wrote yourself, show what is queued or scheduled, summarize recent performance, and, if you are a manager or admin, reject a post that is waiting for review.

  • Nothing is published from chat. The connector never publishes, schedules or approves a post. Every draft or text it saves lands in your Approvals queue in Beacon and waits for a person to approve it there.
  • Five platforms: LinkedIn, Facebook, Instagram (text caption only), X and Bluesky.
  • No images or video. It does not create images, videos, LinkedIn articles, blog posts or replies to comments.
  • Personal brands are LinkedIn-only. If a brand is set up as a Personal brand, the connector will only work with it for LinkedIn, the same rule Beacon applies everywhere.
  • Works with Claude and ChatGPT. These are the two AI apps Beacon accepts connections from.

Before you connect

  • You need a Beacon account that is active, with at least one brand you can access.
  • To have Beacon write a draft, the brand must be set up enough for Beacon to write in its voice. If it is not, the connector says so and gives you a link to finish setup. If the brand's FingerPrint is not trained yet, drafts use Beacon's general style and say so.
  • You must have signed in to Beacon within the last 12 hours to connect. If not, Beacon asks you to sign in again first.
  • Your role in Beacon decides what the connector can do for you. Viewers can read but cannot write drafts. Only managers and admins can reject posts.

How to connect

Beacon's connector address (the MCP server URL) is:

https://beacon.1humanleft.com/api/mcp

In Claude

  • Open Claude's connector settings and choose to add a custom connector.
  • Enter the address above and save it.
  • Choose to connect. Claude opens a Beacon page where you sign in and approve access (see below).

In ChatGPT

  • Open ChatGPT's connector or app settings and add Beacon as a custom connector with the same address.
  • Choose to connect. ChatGPT opens the same Beacon page to sign in and approve access.

Menu names in Claude and ChatGPT change from time to time and depend on your plan there. Check their own help pages if a menu looks different. In ChatGPT, whether you can add a custom connector depends on your plan, and it may need developer mode switched on or an admin to allow it. OpenAI's help centre has the current details.

The Beacon approval screen

Each time an app connects, Beacon shows its own approval screen. It is never skipped and Beacon does not remember past approvals. On it you:

  • See which app is asking and the address it will return to.
  • Choose which brands it may use. It can only ever see the brands you tick, and only brands you already have access to in Beacon.
  • Choose what it may do. Reading your queue, schedule and performance is always included. Writing drafts into Approvals is a separate box (not available to viewers). Rejecting posts is another separate box, shown only to managers and admins.
  • Select Allow to connect, or Cancel to refuse.

After you allow a connection, Beacon emails you to say which app was connected, for which brands, and what it can do. If a team member connects an app, the account owner is emailed too. The email links to the page where you can disconnect it.

If, after you sign in, Beacon shows a “404: This page could not be found” page instead of the approval screen (Claude or ChatGPT may show their own connection error instead), the connector is not switched on for your account yet. Email support@1humanleft.com.

What each tool does

The connector gives Claude or ChatGPT five tools. If you leave out the brand and your connection has more than one, it asks which brand you mean.

Draft a post in my brand's voice

draft_social_post · writes a draft

  • Beacon writes a post for one platform from your topic (10 to 1,500 characters) and an optional angle, using the brand's FingerPrint voice.
  • It saves one draft to the brand's Approvals queue. It is not published or scheduled, and it expires if nobody reviews it within the review window (72 hours by default).
  • It counts toward your account's daily AI usage. Limits: 10 drafts an hour and 30 a day per person, and 100 chat drafts and texts a day across your whole team.
  • Needs the drafts permission and the admin, manager or contributor role.

Put my exact post text in the Approvals queue

queue_post_text · writes a draft

  • Saves the text you give it word for word. Beacon does not rewrite it or apply the FingerPrint voice.
  • If the text is longer than the platform allows, Beacon refuses it instead of shortening it. Links that are not one of the brand's own are flagged for the reviewer.
  • An optional suggested time is only a note for the reviewer. Nothing is scheduled.
  • Limits: 10 an hour and 30 a day per person, 20 a day per brand, and the shared team limit above. Needs the drafts permission and the admin, manager or contributor role.

See what's queued and scheduled

list_scheduled_content · read-only

  • Lists scheduled posts and posts waiting for review for a brand, for the next 1 to 30 days (7 by default), with the platform, time, status and a short excerpt. It shows up to 25 items.
  • Managers and admins see scheduled posts and the review queue. Contributors and viewers see scheduled posts only.
  • It cannot change, approve, reschedule or delete anything. Needs only the read permission.

Last week's performance summary

get_weekly_performance · read-only

  • Summarizes posts Beacon published for a brand: impressions, likes, comments, shares, engagement rate, a breakdown by platform, the best post, and a comparison with the period before.
  • Choose the last 7 days, the previous Monday-to-Sunday week, or the last 30 days.
  • It only covers posts Beacon published and only platforms whose analytics Beacon can read. Posts with no analytics yet are noted. Needs only the read permission.

Reject a post waiting in Approvals

reject_post · changes a post's status

  • Rejects one post that is waiting for review, using the same reasons as rejecting in the Approvals screen. A short note is optional, and required when the reason is "other". The rejected post stays in Beacon.
  • It only rejects. It never approves, schedules, edits or publishes anything. Blog articles are rejected in Beacon, not from chat.
  • Only available to managers and admins, and only if you ticked the rejection permission when you connected.

What data it reads and writes

What it can read

  • The names of the brands you allowed.
  • For those brands: scheduled posts and, for managers and admins, posts waiting for review, as short excerpts with platform, time, status and where the post came from.
  • Performance numbers for posts Beacon published, and an excerpt of the best post.
  • The brand's FingerPrint voice is used by Beacon to write a draft. It is not handed to the AI app.

What it can write

  • New items in the Approvals queue, waiting for a person to review.
  • A rejection on a post that is waiting for review, if you gave it that permission.

What it can never do

  • Publish, schedule or approve a post.
  • Send replies or messages.
  • Change settings, billing, your team or your connected social accounts.
  • Delete anything.
  • Your access is checked on every request. Beacon rechecks your role and the brands you can reach each time the app calls it. If you lose access to a brand, or leave the team, the connection stops working for it.
  • What Beacon keeps. For each request Beacon keeps a log entry with the tool used, the brand, the result, the length of what was sent (not the text itself), and the IP address and browser or app user-agent of the request. These logs are kept for 13 months, including after an account is deleted, and then deleted. A draft's topic (the first 200 characters) is stored with the draft in your queue.
  • How sign-in is protected. Approval uses OAuth with PKCE. Beacon stores only hashed access and refresh tokens. An access token lasts 1 hour. A connection stops working after 30 days without use, and at the latest 90 days after it was made, even if it is in regular use. Then it has to be connected again.
  • What the AI app sees. Claude or ChatGPT receives what the tools return, such as brand names, post excerpts and performance numbers. How they handle it is covered by their own terms and privacy policies. See also Beacon's Privacy Policy and Terms of Service.

How to disconnect and revoke access

  • In Beacon, open Settings and go to Connected AI apps. Each connection shows the app, the brands, what it can do, when it was connected and when it was last used.
  • Select Disconnect on a connection. It stops working immediately: the app's next request is refused. If you have more than one connection, Disconnect all ends them all at once.
  • Account owners and admins see and can disconnect every connection in the team. Everyone else sees and can disconnect their own.
  • Also remove Beacon from Claude or ChatGPT's connector settings. Removing it there does not reliably tell Beacon, so the Connected AI apps list in Beacon is the place where a connection truly ends.

Connections also end by themselves when you change or reset your password, when a team member is removed, when an account is deleted, when every brand on the connection is deleted, after 30 days without use, and at the latest 90 days after the connection was made.

If something does not work

  • "This Beacon account isn't active, so Beacon can't do this right now." The account owner needs to resolve the account in Beacon's billing settings.
  • "This brand isn't set up enough for Beacon to write in its voice yet." Finish the brand's setup in Beacon, then ask again.
  • "Your Beacon role can view content but not write drafts." Ask an admin or manager on your team.
  • "This connection was not given permission to do that." Disconnect and reconnect, and tick the permission you need on the approval screen.
  • A limit message. The draft and request limits above reset over time. Try again later.
  • "Brand access removed. Reconnect Beacon." Connect again and choose the brands you want.

Need help?

Email support@1humanleft.com and tell us which app you are connecting from.