maark
Log inStart for free
AI Connections

Drive Maark from the tools you already live in.

Connect your own assistant — Claude, Cursor, claude.ai or ChatGPT — directly to your workspace over MCP, the open standard for letting an AI client talk to an external tool. Your assistant does the driving; Maark does the work. You do not install anything on a server.

How it connects

An open standard, two ways to sign in

Maark hosts an MCP endpoint. You add it as a connector in your client, and authenticate the way that fits the client.

The connection
Your AI client
Claude · Cursor · claude.ai · ChatGPT
Maark MCP endpoint
scoped · project-limited
Your workspace
the projects you selected
Your client talks to Maark's hosted MCP endpoint, which is scoped and limited to the projects you selected. Nothing runs on your infrastructure. This is the connection model shipping in the product today.

A scoped key (mk_…)

Mint a key in Maark and paste it into your client’s config. Best for Claude Code and Cursor. Shown once, revocable at any time to instantly cut off that connection.

A guided sign-in (OAuth)

Your client sends you to Maark to log in, pick your organization and projects, and approve access — no key to copy. Best for claude.ai and ChatGPT. Expired sessions are pruned automatically.
Access model

Scoped, so an assistant can only do what you allow

Every connection has exactly one scope, chosen when you mint a key or sign in.

Read
Default for non-admin members.
View your data — pipeline status, opportunities, coverage, evidence. No changes.
Propose
Admins can grant it.
Suggest changes that land in a Maark approval queue for a person to accept or reject.
Operate
Admins grant it to trusted connections.
Make direct changes within the connection’s project scope.

Write-capable actions default to a safe preview: the assistant shows what it would change before anything is committed. Every action taken over a connection is recorded, so you always have a trail of what ran, when, and under which scope.

What you can ask for

Real SEO work, in the words you already use

01"What should we build next?" — pull content opportunities and create a planned-page request for the ones you like.
02Chase striking-distance wins and turn them into refresh tasks.
03Review the evidence for a cluster and propose which page should own it.
04Import keywords from an external source — they ride the normal review pipeline.
05Get a client-ready pipeline health summary.
Boundaries

What an assistant can never do

Some capabilities are kept off the connection surface entirely — not as a setting, but by design.

Publishing to your site — that always goes through the human review flow, never over a connection.
Owner-only tooling — the internal marketing, outreach and audit systems are never exposed to a customer connection.
Reaching a project you did not select — there is no "all projects" backdoor.
Related

A connected assistant drives the same Keyword Universe and Content Autopilot you use in the dashboard — connecting one is optional, everything works from the dashboard too.

Connect your assistant

Add Maark to Claude, Cursor, claude.ai or ChatGPT and put your SEO workspace one message away.

Start for freeRead the setup guide