MCP Server

Drive Tinct from your AI assistant. The Tinct MCP server lets Claude, Claude Code and other MCP-capable tools create campaigns, generate landing pages, edit them and publish them — in a conversation, with your own Tinct account.

MCP (Model Context Protocol) is the open standard AI assistants use to work with external tools. Tinct exposes its landing-page workflow through it, so any assistant that speaks MCP can connect — no plugin, no install. You act as yourself: the assistant can only do what your role in the workspace already lets you do in the Tinct app.

What you can do

Tinct has two kinds of campaign, and the assistant can drive both:

• Generate a new landing page. Tinct designs, writes and hosts a page from a brief and your brand. Best when you don't have a page for the initiative yet.
• Personalize the landing page you already have. Tinct identifies the personalizable blocks of your own page and generates one version per target company, served through the Tinct snippet on your site. Best for account-based campaigns on an existing page.

Everything a tool changes is visible in the Tinct app immediately, and vice-versa — the MCP server is just another way in. The full list is in the tool reference.

Connect your assistant

Pick your client. The URL and the sign-in flow are the same for all of them: the client opens Tinct in your browser, you log in (if you aren't already) and click Allow.

# register the server for your user, available in every project
claude mcp add --transport http --scope user tinct https://api.tinct.ai/mcp

# register the server for the current project only (default scope)
claude mcp add --transport http tinct https://api.tinct.ai/mcp

# write it to .mcp.json at the project root so teammates get it from git
claude mcp add --transport http --scope project tinct https://api.tinct.ai/mcp

# equivalent .mcp.json entry, if you prefer editing the file by hand
{
  "mcpServers": {
    "tinct": {
      "type": "http",
      "url": "https://api.tinct.ai/mcp"
    }
  }
}

Generate a new landing page

The server ships its own instructions, so the assistant already knows the order of operations. You just describe what you want. A typical opener:

Behind that one message, the assistant walks this flow:

Useful follow-ups once the preview is up:

Editing & publishing

Every generated page is made of named sections (hero, features, cta, …) containing addressable blocks (hero.h1, cta.cta-primary, …). The assistant reads the structure with list_blocks and then uses the narrowest tool for the change you describe:

Each edit produces a new immutable version. Nothing is lost: list_versions shows the history and any earlier version can be published again. Ask "show me the versions" or "go back to the one before the layout change".

Personalize your existing landing page

You already have a landing page and a list of target accounts. The assistant turns that into one personalized version of your page per company, each with its own link. Everything runs through a campaign created with the page URL, and the assistant knows the order of operations. A typical opener:

Which link is which

A personalized page has several links, and each one is meant for a different reader. The assistant gets them ready-made from the tools, so ask for the one you need by name:

The two previews on your site require the page to be published and the snippet installed; until then they are not returned at all.

Useful follow-ups:

Add a company to a live campaign

Day to day the campaign is already published and one more company shows up in your CRM. Just ask; the assistant imports the company into the campaign's audience, waits for the import, finds the new page, generates it and publishes it, without touching the pages already live:

Under the hood: import_leads → get_job → find_audience_leads → list_pages with the lead → regenerate_page → get_page until ready → publish_page. Importing a company that is already in the audience is harmless.

The logos in the "trusted by" blocks come from your customers library, which is separate from the audience. Ask to add a customer and the assistant runs import_customers → get_job → rematch_campaign_logos so the live pages pick up the new logo without regenerating; removing one (remove_customer) updates the pages by itself.

Tool reference

What your assistant sees. Ids are UUIDs and always come from a previous tool result — you never need to type one.

The server exposes tools only — no MCP resources or prompts.

Access & security

• You act as yourself. Every tool call is checked against your own permissions in the workspace, exactly like the app. A viewer can list and inspect; creating campaigns, editing and publishing pages each require the corresponding role permission. A refused call comes back to the assistant as Error: permission denied. — not as a disconnect.
• Only your workspaces. list_my_organizations returns the workspaces you are a member of, and every other tool is confined to them.
• No secrets to store. There is no API key. The client holds a rotating refresh token for you, scoped to the MCP server alone (see tokens).
• Confirmation gates. Generation waits for your explicit confirmation of the brief, and nothing is published unless you ask. Your assistant may add its own approval prompts on top (Claude Code, for instance, asks before each write tool unless you allow it).
• Registrations are rate-limited (10 new client registrations per hour per IP) and unused registrations are purged after 30 days.

Disconnecting

• Claude: Settings → Connectors → Tinct → Remove (or Disconnect to keep the connector but drop the login).
• Claude Code: claude mcp remove tinct (add --scope user or --scope project to match how it was added), or clear just the login from /mcp → tinct → Clear authentication.
• Lost or shared device: removing the connector from the client is what revokes its tokens, and you can't do that from a device you no longer have. Contact Tinct support with the client name and the approximate time you connected so the registration can be revoked server-side; any access token still in flight expires within 15 minutes.

Troubleshooting

MCP vs. service accounts

Tinct has two ways to work outside the app. They don't overlap — pick by who is doing the work:

Appendix: how sign-in works

For the curious and for IT teams reviewing the connection. You never handle a credential yourself; this is what the client does when that browser tab pops up:

1. The client calls /mcp without a token and gets a 401 pointing at Tinct's OAuth metadata.
2. It registers itself as an OAuth client (public client, PKCE, scopes mcp and offline_access) and opens the authorization page.
3. You log in to Tinct if needed — the same login as the app — and see a consent screen: which client is asking (e.g. "Claude"), which account you're signed in as, and what it will be able to do (use Tinct on your behalf, stay connected). Click Allow.
4. The client receives a short-lived access token and a refresh token, and connects.