Skip to main content
Hamla runs an MCP server, so an AI assistant can work your marketing account directly: create campaigns, read performance, look up customers. Connect once, then ask in plain language.

Connect

1

Create a Hamla account

Sign up at app.hamla.io. The Free plan is enough to try this.
2

Connect your business

Link your store, social accounts, or other tools. See Channels and tools for what each channel needs.
3

Add the server to your client

In Claude, search for Hamla in the Connectors Directory and click connect.In ChatGPT, or in any other MCP client — Claude Code, Cursor, VS Code, Windsurf, Zed, Goose, Gemini Enterprise — add the server URL:
Hamla is also listed in the official MCP registry as io.hamla/hamla, so clients that search the registry can find it without the URL.However you add it, you will be prompted to sign in with your Hamla account. If you have not set up a business yet, Hamla creates one for you from your email, and your assistant finishes the setup with you in conversation — it asks what the business is called and what it does, then saves that with updateBusiness.

Authentication

OAuth 2.1 with PKCE. You sign in with your own Hamla account and the assistant acts as you — there is no API key to paste or rotate, and access follows your normal permissions.

What it can do

The server exposes 34 tools. The full list, with the access and scope each one needs, is on MCP tools. Read-only tools cover businesses, campaigns, contacts, segments, templates, analytics and attribution. Write tools build and edit campaigns, create and edit segments, import contacts and record their consent, save plans and reports, and build decks. Every tool declares whether it reads, writes, or can undo something, and your client shows you that before it calls one. Two things are worth knowing before you ask for them:
  • Launching asks you first. controlCampaign can launch, resume or schedule a campaign — the step that starts sending to real people — but only on your explicit say-so: your client shows you a confirmation before the call, and Hamla refuses the call unless the assistant marks it as confirmed by you for that exact campaign. It runs the same checks as the dashboard’s Activate button (eligible, consented contacts; a channel the trigger supports; your plan’s monthly campaign allowance), so a campaign with no audience is told what to add, not sent to nobody.
  • Bulk contact writes are two steps. importContacts and grantConsent map and count without writing by default, and only commit when you say so — so you always see what is about to land before it does.

Data and privacy

  • The server reads only what a request actually needs
  • Nothing is retained beyond the session
  • All traffic is HTTPS/TLS
  • OAuth 2.1 with PKCE
See the privacy policy for the full terms.

Help

Email support@hamla.io.