Give Your Dot Your Marketing: Connecting Marqeable’s MCP Server to OpenAI Dots
A dot is only as useful as what it can reach. OpenAI’s dots, launched September 29, 2026, connect to apps through plugins, and the working part of most plugins is an MCP server. Marqeable has one. This post covers how to connect it, which tools to let a dot run freely, which to hold for approval, and what the dot cannot do under any setting.
Read this first. We wrote this on launch day, and dots had not reached our own account. The Marqeable side of this post is tested: the same server works in ChatGPT Developer mode, Claude, Claude Code and Codex today. The dot side comes from OpenAI’s documentation and launch coverage. We have not yet confirmed that a dot uses a custom connector during background runs. We will update this post when we have run it.
If you are new to dots, start with OpenAI dots for marketing.
What you need
| Requirement | Detail, as of September 2026 |
|---|---|
| A dot | Included with ChatGPT Pro and Business Premium in eligible markets |
| Developer mode | Needed for custom MCP connectors. Paid plans only, and in a workspace an admin may need to grant it |
| A Marqeable account | You sign in as yourself. The dot sees what your login can see |
| A desktop | Dots are created in the desktop app or a desktop browser |
Step 1: Add the connector in ChatGPT
Marqeable’s server address is:
https://app.marqeable.com/mcpIt is a remote server over HTTP with OAuth. No API key is stored anywhere.
- In ChatGPT, open Settings and turn on Developer mode. OpenAI’s Developer mode guide has the current location of the switch, which has moved between releases.
- Add a new connector, name it Marqeable and paste the address.
- Choose OAuth as the sign-in method and save.
- Sign in to Marqeable in the browser window that opens.
To confirm it works before involving a dot, open a normal chat, enable the connector and ask: “Run whoami and tell me which account I am signed in to.”
Step 2: Connect it to your dot
When you create a dot, onboarding asks you to connect apps, per OpenAI’s getting started guide. Add Marqeable there, or from the dot’s connected apps afterwards.
This is the step we have not been able to verify. If Marqeable does not appear for your dot, the connector is still usable in ordinary ChatGPT conversations, and scheduled tasks created from a chat can use plugins.
Step 3: Sort the tools into rules
Dots have Custom Rules with three settings per action: allow, require approval, prohibit. Here is how we would sort Marqeable’s tools. The server marks each tool as read-only or not, so an assistant can tell the two apart.
Allow: reads
These change nothing. Let them run freely, or the dot will ask you forty times a day.
| Tool | What it reads |
|---|---|
whoami, list_accounts | Who is signed in, and to which account |
get_business_context | Current focus, offers, audience and voice |
get_content_calendar | Calendar entries, planned content and suggested dates |
list_campaigns, get_campaign | Campaigns and their planned pieces |
search_content, get_content | Content pieces, briefs and current copy |
list_content_templates, search_image_library | Templates and existing images |
get_automation_overview, get_automation_plan | Automations, their steps and their numbers |
get_event_catalog, inspect_landing_pages | What an automation can start on, and page states |
check_account_setup, check_automation_readiness, validate_automation_plan | Checklists and dry runs |
get_brand_look | The account’s email look |
Allow once you trust the output: drafts and suggestions
Each of these creates or edits something a person reviews in Marqeable. Nothing reaches a customer.
| Tool | What it creates |
|---|---|
create_campaign_draft | A campaign in draft |
create_content_draft | A content piece in draft |
create_automation_draft, update_automation_draft | An automation draft, or a proposed revision a person publishes |
create_automation_step_content | Draft content for an automation’s empty steps |
add_content_suggestion | A suggested edit the owner accepts or dismisses |
update_content_brief | Changes to a draft’s brief |
request_content_changes | A change request at a build checkpoint |
Require approval: direct changes
These take effect without a review step in Marqeable, so put the review in the dot’s rules.
| Tool | Why it needs a yes |
|---|---|
add_calendar_entry, update_calendar_entry | Calendar changes feed the next plan directly |
adopt_suggested_date, dismiss_suggested_date | Same, for suggested dates |
approve_content_build | Moves a build forward and can generate images |
create_automation_trigger_page | Builds a landing page for an automation |
save_content_as_template, set_default_content_template | Changes what future pieces start from |
update_brand_look, reset_brand_look | Changes the look of every email |
Prohibit for background work
| Tool | Why |
|---|---|
set_feature_enabled | Turns account features on or off. A person’s decision |
switch_account | Should only happen when you explicitly ask for it |
What the dot cannot do, under any rule
There is no tool to send a message, publish content, launch a campaign or turn on an automation. There is no delete tool. A rule cannot allow an action that has no tool.
That is the point of the design. Rules are a setting, and settings drift. The tool list does not. The longer argument is in the draft-only rule.
One honest caveat: not everything is a draft. The calendar, brand look and template tools above make real changes. None of them reaches a customer, but they are why the approval group exists.
A first test
Once connected, give the dot a small job with a visible result.
You: Check my marketing calendar for the next four weeks against my current focus in Marqeable. If there is a gap, draft one campaign to fill it and send me the link. Do not change the calendar.
Expected result: Three or four reads, one campaign draft, and a link to review it in Marqeable.
Then open the Activity View and check the calls it made. You are looking for reads and one draft, with no call from the approval group.
Troubleshooting
| What you see | What to try |
|---|---|
| No Developer mode switch | Check your plan, or ask your workspace admin for custom connector permission |
| Sign-in succeeds but no tools appear | Remove and re-add the connector, then start a new chat |
| Dot asks before every read | Check the rule for read actions is set to allow |
| Wrong account | Ask the dot to run whoami. Switch accounts yourself, deliberately |
From here, five dot workflows for a marketing team of one puts the connection to work. The same server in a terminal is covered in Codex MCP for marketing.
Frequently asked questions
Can an OpenAI dot use a custom MCP server?
ChatGPT supports custom MCP connectors through Developer mode on paid plans, and dots work across the apps you connect. As of launch day, September 29, 2026, we have not yet been able to confirm on our own account that a dot uses a custom connector during background runs. We will update this post when we have.
What is the address of Marqeable’s MCP server?
https://app.marqeable.com/mcp. It is a remote server over HTTP with OAuth. You sign in with your normal Marqeable login, and the assistant sees exactly what your account can see.
Can a dot send a campaign through Marqeable?
No. Marqeable’s connector has no send, publish or launch tool. A dot can create campaign, content and automation drafts, and a person reviews and launches them in Marqeable.
Which Marqeable tools should a dot need approval for?
Anything that changes account-level settings: the brand look, the default template, turning features on or off, and switching accounts. Also approving a content build, because that step can generate images. Reads can run freely, and draft creation is a reasonable thing to allow once you trust the dot’s judgment.
The bottom line
Connecting a dot to your marketing is three decisions: which server, which tools run freely, and which tools wait for a yes. With Marqeable the first is one address, the second is every read, and the third is a short list of account settings. Sending is not a decision you have to make, because the tool does not exist.
See what the drafts become: Marqeable’s agents build and run your campaigns, run behavior-triggered automations across text and email, answer and qualify every visitor with AI website chat, and tie revenue to the exact message with attribution.
Marqeable runs your campaigns, answers every visitor, text, and email in seconds, and turns them into booked jobs and meetings - even at 9pm on a Saturday. We’re in private beta with a small early cohort. Get early access
