Markitech / Marketing MCP Server / Marketing MCP Security
Security checklist for a marketing MCP server
What to check before you give an AI access to ad spend, analytics and tags, and how Markitech handles each point.
Updated November 4, 2026 · Markitech team
A marketing MCP server sits between an AI and accounts that control real money and real data. Before connecting one, look at how it authenticates, where tokens live, what it can change and who decides when it does.
Markitech connects through each platform’s own authorization flow, so it never sees or stores your platform passwords. OAuth tokens are encrypted at rest and never leave Markitech’s servers, and every write action is held for approval.
How to do it
- Confirm every platform connects through OAuth or its official authorization flow.
- Ask where tokens are stored and whether they are encrypted at rest.
- Grant access only to the accounts and properties the AI needs.
- Check that write actions are held for approval by the system itself.
- Review connected accounts regularly and revoke access you no longer need from each platform’s settings.
Common mistakes
- Using a shared login so nobody can tell who approved a change.
- Granting manager-level access when one client account would do.
- Pasting tokens or keys into chat history.
- Never reviewing which apps still have access to your ad accounts.
Ask Markitech
Related questions
Key terms
Approved by you, every time
Markitech proposes each change in chat and holds it until you approve. Nothing is published, created or changed in your accounts without that approval.
Part of the Marketing MCP Server guide.
Marketing MCP Security questions
Does Markitech store my passwords?
No. It uses each platform’s authorization flow and never sees or stores your platform password.
Can I revoke access?
Yes. You can disconnect a platform at any time, and each platform also lets you revoke app access from its own security settings.