One connector address. Any MCP client.
MCP is an open standard — and Offloda is a standard remote MCP server. If your tool speaks MCP, it can drive your marketing workspace: same tools, same approval step, same scoping.
What the Any MCP Client is
The Model Context Protocol is doing for AI tools what HTTP did for documents: one standard, many clients. Offloda leans into that — the workspace exposes one remote connector address, secured by OAuth sign-in, and any conformant client gets the identical toolset. Claude and ChatGPT have dedicated guides; everything else follows the same three steps below.
What you can do
A hosted server over HTTPS with OAuth sign-in — no local processes, no API keys pasted into config files.
The toolset, the approval gate and the per-seat scoping are server-side — every client sees the same workspace.
Chat clients can approve writes; automation clients get reads only — the gate knows the difference.
How changes reach your MCP client
The gate is server-side: the preview diff, human confirmation, a second acknowledgement for high-risk changes and paused launches hold for every client — none of it can be negotiated away by a clever tool.
Setup
- 1
Copy your workspace's connector address from the MCP Access page.
- 2
Add it to your client as a remote MCP server and complete the OAuth sign-in.
- 3
The tools appear, scoped to your seat — ask, approve, done.
Best for: Anyone whose favorite MCP-capable tool doesn't have a dedicated page yet — it almost certainly just works.
The complete toolset — identical across clients, scoped per seat, your approval on every change.
Every change waits for your yes; every client stays in its own private workspace.
Security
OAuth connection — Offloda never sees your password. Tokens are scoped and encrypted at rest. Every client brand is in its own private workspace; nothing crosses between clients. No AI keys in the browser. Every action is on the record.
For agencies
Let every teammate use their preferred tool — the workspace under it stays one permission model, one record, one surface.
vs. a raw your MCP client MCP
Any MCP client can also reach raw single-platform servers — unsupervised, unscoped, one account each. One Offloda address replaces the pile, and adds the gate.
Frequently asked questions
My client isn't listed on this site. Will it work?
If it supports remote MCP servers with OAuth, yes. The connector is standard — client-specific pages exist for setup convenience, not compatibility.
Why does the connector need a sign-in?
Because scoping is per seat, not per agency. Your login determines exactly which brands and platforms the client can reach — same as the app.
Is there anything client-specific about the approval step?
No. The preview, the confirmation, the second acknowledgement for high-risk changes and the paused launch are enforced on our servers — no client can skip them.
Any MCP Client — approved by you, under your brand.
Runs on your own AI subscription · New campaigns start paused · One private workspace per client