Skills give Claude Code your playbook. A context file gives it your product. Neither gives it your calendar, your campaigns, or a place to put the draft. One command does. Everything it writes is a draft in Marqeable; nothing it can call will send.
One command adds the server for your user. Sign in once and every project on the machine can use it.
Steps verified against the Claude Code MCP docs on 1 September 2026. Vendors rename menus often; if a step looks different, the server URL is the part that does not change.
Add the server. The user scope makes it available in every project.
claude mcp add --transport http --scope user marqeable https://app.marqeable.com/mcpStart Claude Code, run /mcp, pick marqeable, and finish sign-in in the browser.
Run the first prompt below. Reads run without a prompt; each draft write asks unless you allow it.
Commit a .mcp.json at the repo root and everyone who opens the project gets the connector.
{"mcpServers":{"marqeable":{"type":"http","url":"https://app.marqeable.com/mcp"}}}Same server, one file: .cursor/mcp.json in the project.
{"mcpServers":{"marqeable":{"url":"https://app.marqeable.com/mcp"}}}Start with a read so you can see the assistant using your real business context. Then ask for one draft and open Marqeable to find it waiting for approval.
whoamiget_business_contextget_content_calendarcreate_campaign_draftEvery write is a draft. No send, launch, or delete tools.
A Monday 8am routine that drafts the week runs connector tools, including writes, without asking. That is fine only if the worst case is a draft you delete. Here it is.
Keep the marketing skills for the playbook and the CLAUDE.md for the product. Use the connector for anything that changes weekly: calendar, campaigns, what is live.
The changelog, the release branch, and the launch email live in the same session. Draft the announcement from the diff, then approve it in Marqeable when the release is out.
Judge any connector by its tool list. This is ours, in full. There is no send, launch, or delete tool, so a bad prompt, a scheduled run, or a poisoned web page can never reach your list. The gate is structural, not a permission click.
get_business_contextBrand, voice, offer, audience, what you sell and to whom.get_content_calendarWhat is scheduled, so a draft never collides with a send.list_campaignsEvery campaign and its status.get_campaignOne campaign, all its pieces.search_contentFind last quarter's launch email before rewriting it.get_contentOne piece, full copy and brief.get_automation_overviewWhich automations are live and who is inside them.get_automation_planThe steps, timing, and triggers of one automation.search_image_libraryImages you already own, so nothing is regenerated by accident.whoamiWhich user and account the assistant is acting as.create_campaign_draftA campaign with its pieces, saved as a draft.create_content_draftOne email, post, or page. Copy first, no image spend.create_automation_draftA follow-up sequence, assembled but not launched.update_automation_draftChange a step or the timing on a draft.update_content_briefAdjust the brief before the copy is written.add_content_suggestionLeave a note on a draft for whoever reviews it.request_content_changesSend a draft back with what to fix.approve_content_buildSay yes to the images for a draft you have already read.Sign-in is OAuth 2.1 per user, so no API key is ever pasted into a chat. Multi-account users also get list_accounts and switch_account.
Marketing skills give Claude Code your playbook and a context file gives it your product. Neither gives it your calendar or campaigns. The one-command setup that does.
Read articleRoutines run connector tools, including writes, without asking. That is fine only if nothing can send. Build the Monday 8am routine that drafts the week and leaves it for approval.
Read articlePermission prompts are the wrong safety layer. Judge a connector by its tool list, learn from the 2025-2026 MCP incidents, and adopt the draft-only rule.
Read articleMarqeable is in private beta with a small early cohort. Connect your assistant on day one; hands-on onboarding is included.