Handbook and guides

How to work with Feinwerk Campaigns, step by step.

Choose with the arrow keys, open with Enter, close with Esc.

All articles
Handbook / Getting started

Connect AI assistants

For Owners, Admins, Editors, Viewers and agencies 4 minutes Updated November 2026

With an AI assistant such as Claude you ask your campaigns in your own words: how the autumn campaign is doing, which campaigns start next month or what the newsletter link for the winter sale looks like. The assistant reads through MCP with your rights in Feinwerk Campaigns Live . It cannot change, create or delete anything.

What you need

  • An account with a confirmed e-mail address.
  • Your company has allowed access through AI assistants. Access is off by default. For members of an agency, both the company and the agency must allow access.
  • Claude with custom connectors. They are available on all Claude plans, one on the free plan.

Demo accounts cannot be connected.

Allow access for your company

A company admin does this once:

  1. Open the user menu at the top right, then Settings and there AI assistants.
  2. Switch on Allow access through AI assistants. If you administer several companies, there is one switch per company.

After that, people in your company can connect their own assistant. The data an assistant reads goes to that assistant's provider. If you switch access off again, every connection stops working at once.

Connect Claude

  1. In Claude, open Customize > Connectors and choose + Add, then Add custom connector.
  2. Enter a name, for example "Feinwerk Campaigns", and https://app.campaigns.feinwerk.io/mcp as the MCP server address. Choose Continue.
  3. Under Authentication choose Sign in now, and under OAuth client choose Register automatically. Then choose Add.
  4. Claude opens the Feinwerk Campaigns sign-in. Sign in as usual, with a passkey or two-factor sign-in if you have set one up.
  5. On the page saying that Claude would like to access Feinwerk Campaigns you see your account and your companies. Choose Allow.

Under OAuth client, Claude recommends Use Claude's published identity. It does not work with Feinwerk Campaigns yet; choose Register automatically.

Only allow if you have just started the connection in your assistant yourself.

On Claude's Team and Enterprise plans, owners add the connector for everyone: under Organization settings > Connectors with Add, Custom and Web. You then choose Connect next to the connector under Customize > Connectors and sign in.

In a chat, switch the connector on through + and Connectors.

What you can ask

  • "Which campaigns run next month, and who is responsible for them?"
  • "How many visits did the autumn campaign have in the last 30 days, and what exactly counts?" With every figure the platform supplies its "What counts here?" sentence.
  • "Build me a newsletter link for the winter sale page." The link follows your naming convention and is a preview. It is saved only once you create it in Feinwerk Campaigns.
  • "Which values in the campaign report do not follow our convention?"
  • "What is the trade fair campaign still missing before it is ready to start?"

The assistant sees only what you see in the platform. An agency sees only its own campaigns.

Disconnect

  • Under the user menu, Settings, AI assistants, Connected assistants lists all your connections with Connected since and Last used. Revoke access ends a connection.
  • If you change your password, all your assistants are disconnected. Connect them again afterwards.
  • If you delete your account, all connections end as well.

If it does not work

  • "… has not allowed access through AI assistants yet." The message names the organisation that has not allowed access yet. Ask an admin there to switch it on under Settings, AI assistants. For agencies this can be the company or the agency itself.
  • Sign-in fails: confirm your e-mail address first. It does not work with a demo account.
  • The assistant finds nothing: check that the connector is switched on in the chat and that you have access to the workspace in the platform.

How we protect the connection and what data we store for it is described in the platform privacy policy.

Was this page helpful?