Klienta is a remote MCP server — nothing to install. Pick your client, add the endpoint, sign in with Google, and start managing your Google Ads account by chat.
Uses Claude’s built-in connector settings — no terminal needed.
In Claude Desktop, go to Settings → Connectors and click Add custom connector.
Name it Klienta and paste the remote MCP URL, then click Add.
Claude opens Google’s consent screen in your browser. Choose the Google account that owns (or manages) your Google Ads account and approve access. Your password never touches Klienta — see the FAQ about the “unverified app” screen you may encounter here.
This will allow Klienta to:
Klienta appears in your connector list. Ask Claude something like “list my Google Ads accounts” to confirm the connection.
One command in your terminal.
# Add Klienta as a remote MCP server claude mcp add --transport http klienta https://klienta.co/mcp
Inside Claude Code, run /mcp, select klienta, and choose Authenticate. Your browser opens Google’s sign-in page — approve access and return to the terminal.
/mcp › klienta — needs authentication ✓ Authentication successful. Connected to klienta.
Ask: “Using klienta, list my Google Ads accounts.” You should get back your customer IDs.
Add Klienta to your MCP configuration file.
Go to Cursor Settings → MCP → Add new MCP server, or edit .cursor/mcp.json in your project (or ~/.cursor/mcp.json globally).
{
"mcpServers": {
"klienta": {
"url": "https://klienta.co/mcp"
}
}
}
Cursor detects that the server needs login and opens Google’s sign-in page. Approve access, then ask Cursor’s chat to “list my Google Ads accounts”.
Non-interactive MCP clients — connect with a personal access token, no browser sign-in.
At klienta.co/app → Settings → Agent access tokens, click Generate token. You’ll get a token in the format klienta_pat_… — copy it now, it’s shown only once.
Paste the token into your client’s MCP config as a bearer header.
{
"mcpServers": {
"klienta": {
"type": "http",
"url": "https://klienta.co/mcp",
"headers": { "Authorization": "Bearer klienta_pat_..." }
}
}
}
Ask: “Using klienta, list my Google Ads accounts.” You should get back your customer IDs — no sign-in prompt needed.
Here’s the honest answer: Klienta’s Google OAuth verification is currently under review by Google. Until Google completes that review, their consent screen shows this warning to every user — it does not mean anything is wrong with your account or that data is being mishandled.
If you’re comfortable proceeding, click Advanced → Go to klienta.co (unsafe) → Continue. If you’d rather wait until the verification badge is in place, that’s a perfectly reasonable choice — email us and we’ll let you know when it’s done.
No. Sign-in happens entirely on Google’s own pages — Klienta only receives scoped OAuth tokens that Google issues, limited to the Google Ads permission you approved. Tokens are encrypted with AES-256-GCM at rest. We store no passwords, ever. Details in our Privacy Policy.
Two layers, both under your control:
1. From Google (recommended): go to myaccount.google.com/permissions, find Klienta, and click Remove access. This invalidates our stored tokens immediately, and we delete them.
2. From your client: remove the connector in Claude’s settings, or run claude mcp remove klienta, or delete the entry from .cursor/mcp.json.
For full data deletion, email us — everything linked to you is removed within 30 days.
No. Klienta only acts on instructions you send through your chat client. New campaigns are created paused by default, and you can set your own guardrails — budget caps, bid caps, protected accounts — that are enforced before any change runs.
Setup help, account questions, revocation and deletion requests — one address, replies within a business day.