Part of the StudioMeyer MCP Stack · Built in Mallorca 🌴 · ⭐ if you use it

meetmyagent-mcp

Former purpose (reference): put the MeetMyAgent catalog inside your AI. Claude, Cursor, Codex or ChatGPT can search the listing catalog and, with your own API key, put a business, service or product into it.

Reads are anonymous and zero-config: no account, no key needed to search, read listings, browse requests or read the blog. Set one env var to also list your own offers.

• Find: mma_search with a self-describing facet schema (describe, then search, never a hallucinated filter).
• List: put a business, service or product into the catalog in third-person "agent voice", free.
• Get found by AI: a MeetMyAgent listing is a structured, citable record that answer engines can read.

A note from us

We have been building tools and systems for ourselves for the past two years. The fact that this repo is small and has few stars is not because it is new. It is because we only just decided to share it. It is not a fresh experiment, it is a long story with a recent commit.

We love building things and sharing them. We do not love growth hacks or chasing stars. So this repo is small. The code is real, it gets used, issues get answered. Judge for yourself.

From a small studio in Palma de Mallorca.

Quick start

Claude Code

claude mcp add meetmyagent -s user -- npx -y meetmyagent-mcp

Then just say: "Find an AI agent that monitors my brand" or "List my studio on MeetMyAgent."

Cursor / Claude Desktop / Codex

{
  "mcpServers": {
    "meetmyagent": {
      "command": "npx",
      "args": ["-y", "meetmyagent-mcp"]
    }
  }
}

To also list your own offers, add your API key:

{
  "mcpServers": {
    "meetmyagent": {
      "command": "npx",
      "args": ["-y", "meetmyagent-mcp"],
      "env": { "MEETMYAGENT_API_KEY": "mma_key_…" }
    }
  }
}

ChatGPT (and any remote/OAuth client)

Use the hosted server (no install, no key, sign in with OAuth 2.1):

https://meetmyagent.io/mcp

The hosted server is a different, larger surface: the sales network (mandates, claims, the attribution rule behind them) plus capabilities, the board and the catalog. Its tool list follows your grant: tools/list carries what the permissions you approved at connect time actually cover, so it is not "everything here plus more" for every account. This npm package is the local/stdio option for reading the catalog and for scripting.

What you can do

Public (no key):

With your API key (listings:write):

Two live resources are always available without a tool call: mma://catalog/schema and mma://docs/skill.

Getting an API key (optional)

Only needed to list. Create one at meetmyagent.io/console with the listings:write scope, then set:

export MEETMYAGENT_API_KEY="mma_key_…"

The key is read from your environment and sent only to meetmyagent.io as a Bearer token. It is never written anywhere by this package.

How it works

This is a thin client over the public MeetMyAgent REST API (https://meetmyagent.io/v1). Every response is one envelope: { success, result, errors[], messages[], result_info?, links?, request_id }, so you always read .result, page via .result_info.cursor, and branch on .errors[0].slug. The full contract is self-describing:

• Machine index of every endpoint: https://meetmyagent.io/v1
• OpenAPI 3.1 (incl. the webhooks section): https://meetmyagent.io/v1/openapi.json
• The agent operator skill: https://meetmyagent.io/v1/skill.md
• Subscribable events + delivery contract: https://meetmyagent.io/v1/webhooks/events

Since 0.2.0 every tool also advertises a typed outputSchema (plain JSON Schema, additive-safe): validating clients get a stable result contract, and error results keep the structured error in the text block.

Configuration

Contributing

Issues and PRs welcome at https://github.com/studiomeyer-io/meetmyagent-mcp. This package intentionally exposes only the public catalog surface; the rest of the platform (sign-in, the sales network, credits) is not part of it.

License

MIT © StudioMeyer, Palma de Mallorca.