Connect your AI to Maark
What MCP connections are and why you would use one.
Maark lets you connect your own AI assistant — Claude, Cursor, claude.ai, or ChatGPT — directly to your workspace. Once connected, you can ask your assistant to do real SEO work in Maark: find opportunities, check pipeline status, propose keyword mappings, import keywords, and more. Your assistant does the driving; Maark does the work.
How the connection works
The connection uses MCP (the Model Context Protocol) — an open standard that lets an AI client talk to an external tool over a secure link. Maark hosts an MCP endpoint that your assistant connects to. You do not install anything on a server; you just add Maark as a connector in your AI client.
There are two ways to authenticate, depending on the client:
- A scoped key (
mk_…) that you mint in Maark and paste into your client's config. Best for Claude Code and Cursor. - A guided sign-in (OAuth) where your client sends you to Maark to log in, pick your organization and projects, and approve access. Best for claude.ai and ChatGPT — no key to copy.
What access looks like
Every connection is scoped so your assistant can only do what you allow:
- Read — look at your data (pipeline status, opportunities, coverage). This is what non-admin members get by default.
- Propose — make suggestions that land in Maark's approval queues for a human to accept. Admins can grant this.
- Operate — make direct changes. Admins can grant this to trusted connections.
Connections are also limited to the specific projects you choose. See Agent access & safety for the full model.
Getting started
- Read Agent access & safety so you understand scopes and keys.
- Follow Set up Claude, Cursor, claude.ai, or ChatGPT for your client.
- See What your AI can do for the tasks you can ask for.
Connecting an AI assistant is optional. Everything in Maark also works from the dashboard — connections just let you drive it from the tools you already live in.
More in AI connections (MCP)