meetmyagent
Create
← Blog

Claude MCP connector, agent card and AI disclosure

The Claude MCP connector lets you run your business agent from the chat. Your agent also gets an A2A agent card and a visible AI label for Article 50.

A lot of businesses start with a custom GPT and then realize that an internal assistant and a public front desk are two different jobs. If Claude is already part of your workday, you want to run your business agent from the chat, not from a second admin screen. That's what the Claude MCP connector from MeetMyAgent is for. On top of that come the agent card and A2A for other AIs, plus a visible label that fits the transparency rules of the EU AI Act.

This article is for owners and teams who are comfortable with AI. The focus is the operator side: setting up the connector, the agent card, the AI label. The website widget only shows up as the result; the front desk for visitors is covered in the article on the AI agent for your website.

A custom GPT often isn't enough for customers on your website

Internal assistant vs. public front desk

A custom GPT (or a similar workspace assistant) helps you write, research and work with internal knowledge. Visitors to your website get nothing out of it: a custom GPT lives in its provider's account, not on your website. For the public customer channel, you need something else.

It helps to tell three kinds of solutions apart: rule-based bots, generic GPT bots and solutions built on business knowledge. The real question isn't "which model is the coolest" but: where do anonymous visitors talk to your business, and who runs the agent afterward?

What a real alternative needs to do

A custom GPT alternative for the customer channel should at least offer:

  • A chat window on your own website and a shareable agent page
  • Requests in your inbox
  • Control from your own AI instead of a click-only interface
  • Discoverability for other agents through open standards
  • A clear statement: this is an AI

That's where MeetMyAgent sits: a public business agent, operated from Claude (and other assistants), without your customers needing an AI account of their own. It doesn't replace a custom GPT inside OpenAI. It's the customer channel next to it.

Claude MCP connector: run your business agent from Claude (and other AIs)

MCP in one sentence

MCP (Model Context Protocol) is the connection that lets your assistant work with other services. Instead of clicking through the MeetMyAgent console, you talk to Claude (or another client), and the assistant calls the tools you approved.

Connector URL and sign-in

The connector URL is:

https://meetmyagent.io/mcp

The steps for Claude are on the Connect page and match Anthropic's help article Get started with custom connectors using remote MCP:

  1. Copy the connector URL
  2. In Claude, go to Connectors, add a custom connector, name it MeetMyAgent and paste the URL
  3. Sign in once (OAuth). After that, you see the tools you approved

When you connect, you decide what the assistant may do. tools/list only shows the approved tools. If something is missing, it's often not a fault but a permission you didn't grant. Details are in AGENTS.md.

Typical jobs: set up, add knowledge, go live with your OK, read the inbox

Over MCP you can, among other things:

  • check whether an agent exists yet and what's missing
  • create the agent as a draft or update it
  • add knowledge (text, FAQ, URL)
  • put it live, but only after your explicit OK
  • fetch the install details (card address, endpoint, page, chat snippet)
  • read and handle requests, and record an answer only after you approve it
  • pause it (offline everywhere, nothing deleted)

A first message could look like this (the example from the Connect page; adjust it to your business):

Set up my agent on MeetMyAgent. We're a hair salon doing cuts, color and bridal styling, and we answer in English and Spanish.

The AI asks about whatever is still missing. The agent only goes live once you agree. Made-up services or prices are off limits (AGENTS.md).

You can only get Business on the website. To cancel, use Stripe's customer portal. Canceling by email works too. Almost everything else around setup and requests happens in the chat.

Claude and other clients

For Claude, the path is fully documented and works on both MeetMyAgent plans. On Claude's side, custom connectors are available on the Free, Pro, Max, Team and Enterprise plans, with one custom connector on Free. ChatGPT only works with a work account (Business, Enterprise or Edu); with Cursor and Codex the available scope depends on the product and plan (details on the Connect page). Without an assistant, everything works right in your account on meetmyagent.io.

Agent card and A2A: so other AIs can find your business

The agent card as a machine-readable business card

A2A is the open standard AI agents use to talk to each other. An agent card is the small file that says who the agent is and how to reach it. For a business, that means other AIs can find your offer and leave requests without a human having to click through your website first.

Every MeetMyAgent business agent has an A2A address and a card. The platform itself has MCP, REST and a platform card of its own. Live agents land in the directory, next to agents connected from elsewhere (llms.txt, AGENTS.md).

The well-known path and your MeetMyAgent card

You can make the card visible on your own domain:

  • a copy at /.well-known/agent-card.json (replace it after every change), or
  • a 301 redirect from that path to the card address MeetMyAgent gives you (stays current by itself)

Cards are signed and can be verified against the platform's JWKS. MeetMyAgent doesn't offer streaming or push notifications over A2A; AGENTS.md says so explicitly.

Already run an A2A agent? Add it by its card

If you already run an agent elsewhere that speaks A2A, enter the address of its card (or your domain) under Connect. According to the Connect page, the check covers:

  • a valid A2A card (version 1.0; 0.3 is recognized)
  • the signature and a key from the card's own domain, if the card is signed
  • whether the address the card names can be reached
  • name and description passing the content check
  • a fresh check every day after that

If the agent passes, it's listed in the directory.

EU AI Act Article 50: a label people can see

In effect since August 2, 2026

Article 50 of the EU AI Act sets out transparency obligations; its first paragraph, which covers AI systems that interact with people, has applied since August 2, 2026. For those systems, the point is to make clear that an AI is talking. Practical guides such as the one from IHK Frankfurt (in German) point out that the notice should be visible at the start of the interaction and that terms of service alone often aren't enough.

This isn't legal advice. Which obligations, if any, apply to your specific setup is for you to check, on your own or with professional advice. The operator stays responsible.

How the product behaves: the agent says it's an AI

A hosted MeetMyAgent agent says visibly that it's an AI: on its page and in every chat window. The product FAQ and the terms describe this as a fixed feature, not an optional footer. For labeling chatbots under the EU AI Act, that's the support on the product side. It doesn't replace a compliance review of your whole website or your processes.

Why this fits a B2B agent

If you explain offers and collect requests, you shouldn't pretend to be human. MeetMyAgent is a B2B front desk for your offer, not a companion product. The label protects trust and makes the whole setup more credible to customers. The same goes for other AIs that are supposed to pass answers on (AGENTS.md: keep a hosted agent's answers recognizable as AI).

How it fits together: Claude runs it, customers chat, other AIs discover it

Three roles in brief

  1. Owner's assistant (MCP): you set up, maintain knowledge, go live, read the inbox.
  2. Visitors: people chat on the agent's page or in the website widget. They don't need Claude.
  3. A2A / other AIs: other agents find the card, ask questions or leave requests.

You decide what goes live

Nothing goes live and no answer is recorded for you without your OK. MeetMyAgent requires that of every connected assistant. You stay in charge of the front desk; the agent and your assistant are tools.

Platform hosting: Hetzner in the EU. Model calls: Anthropic for chat answers, OpenAI for embeddings and search (privacy policy). Conversations are deleted after 24 hours; archived requests are deleted once they're older than 90 days.

Getting started without a big project

Connect plus Create; Free for testing

Two ways in:

  • Connect: set up MCP once, then keep working in the chat with Claude
  • Create: create the agent right on the website

Free costs €0: 50 answers a month, 5 knowledge sources, all languages, a MeetMyAgent note in the chat, no email for new requests. No payment details. For businesses only.

When Business makes sense

Business costs €39 a month or €390 a year: 2,000 answers a month, 50 sources, all languages, the chat without the MeetMyAgent note and an email to you for every new request. Final prices, no VAT charged (small business under § 19 UStG); cancel any time, effective at the end of the billing period (homepage).

Business pays off when the agent answers questions every day, you need email notifications, or you need more sources. The MCP route stays open on both plans.

Bottom line: Claude MCP connector, agent card and AI label

The Claude MCP connector turns MeetMyAgent into a business agent you run from your own AI. The agent card opens the same agent up to A2A and the directory. The visible AI label supports transparency under Article 50 without replacing legal advice. As a custom GPT alternative, this only covers the public customer channel plus control from Claude, not every internal GPT workflow.

Next step: set up the connector or create your agent. For the visitor side (widget, explaining your offer, requests), have a look at the homepage and the front desk article.

Sources