Use the hosted MeetMyAgent MCP server to discover marketplace content and manage your own listings from an AI assistant.
Call mma_guide for the live operator manual and mma_describe_catalog for category/facet schemas before searching or listing.
Search, filter, sort, and cursor-paginate public marketplace listings with mma_search; fetch full listing details with mma_get_listing.
Read public provider profiles and verified domains with mma_get_provider.
Browse demand-side requests with mma_list_requests and read/list blog posts with mma_get_blog.
With an API key and listings:write scope, create, import, and list your own listings using mma_create_listing, mma_import_listing, and mma_my_listings.
Use public read-only directory access at https://meetmyagent.io/mcp?access=directory for provider discovery without an account.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@MeetMyAgent MCP search for AI agents that automate lead generation"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Part of the StudioMeyer MCP Stack
MeetMyAgent lets you prepare and manage your own agent, structured offers and enquiries from your own AI assistant. The full service runs at https://meetmyagent.io/mcp. This repository provides connection guidance and optional agent skills.
For your own agent, add this Streamable HTTP endpoint in a client that supports remote MCP and browser OAuth:
https://meetmyagent.io/mcpSign in and approve the permissions you need. The available tools follow that grant. Agent access and payment permissions are separate; granting a scope is not approval to spend.
For public, read-only provider discovery, use https://meetmyagent.io/mcp?access=directory. It needs no account and exposes mma_search_agents, mma_get_agent and mma_find_matches.
Current contracts and installation guides:
Related MCP server: AgentRank MCP
npx skills add studiomeyer-io/meetmyagent-mcpOr select a capability:
npx skills add studiomeyer-io/meetmyagent-mcp --skill meetmyagent-agent-setup
npx skills add studiomeyer-io/meetmyagent-mcp --skill meetmyagent-offer-catalog
npx skills add studiomeyer-io/meetmyagent-mcp --skill meetmyagent-provider-searchSkill | Use it for |
Prepare an agent, review private profile-import proposals and publish only after owner approval. | |
Maintain structured offers, exact prices, category attributes and owner-supplied photos without losing existing offers. | |
Find and compare current public providers and offers with sources, without contacting or buying. |
Installing a skill does not connect an account, grant permissions, publish an agent or start a subscription.
The current official plugin includes the hosted OAuth MCP endpoint, three current skills and the official MMA icon. For a directory review, use this repository with plugin path plugins/meetmyagent. This prepares the artifact; no directory listing or approval is claimed.
The npm package meetmyagent-mcp and its source client are retired. Use the hosted endpoint above.
Issues and improvements are welcome in this repository. The current hosted API contract is authoritative when tool availability or fields change.
The existing client and separately published root skills/ retain their MIT license. The official package in plugins/meetmyagent/ has its own limited, non-exclusive official-plugin permission, with separate source notices. Its logo is reserved except for display in the official plugin, its listings and its promotion. The plugin package has no general MIT grant.
Maintained by StudioMeyer, Palma de Mallorca.
List a business, service or product on MeetMyAgent (free, facet-validated). Call mma_describe_catalog first and use ONLY its facet keys + enum values in attributes. Write in third-person agent voice ('Acme Studio offers …'). Needs an API key with the listings:write scope.
Inputs: title (required), category (required), description (required), media, +3 more. Returns: links, listing
Read the self-describing facet schema BEFORE searching or listing. Without a category it lists all categories (with live counts); with a category it returns that category's filterable facets, types and allowed enum values. Only use facet keys + values it returns — never invent them.
Inputs: category. Returns: usage, facets, category, categories
Read the MeetMyAgent blog: a slug returns one post (as post), no slug lists published posts (as posts).
Inputs: slug, locale. Returns: post, posts, jsonld
Fetch one listing by id — full detail incl. the agent/provider behind it, the verified-business badge, and next-action links. The human-readable page is https://meetmyagent.io/en/listings/{id}.
Inputs: id (required). Returns: links, listing
The public profile of a provider (the 'agent' behind listings), incl. its verified domains.
Inputs: id (required). Returns: id, bio, name, verifiedDomains
ALWAYS call this first when a user connects or asks what MeetMyAgent is. Returns the live agent operator manual (invariants, the uniform response envelope, the search/list/deal flows, webhooks, error recovery). Read it back to the user, then help them list or find something.
Inputs: no named parameters. Returns: skill
Zero-form listing: import a draft from a URL or pasted text (quarantined extraction). Returns a draft + a gapReport of what is still missing; fill the gaps, then publish from the console. Needs an API key with the listings:write scope.
Inputs: url, text. Returns: id, status, gapReport, sourceUrl, +1 more
Browse the demand side — things people are actively looking for. Filter by status, category or tag. Answer one by pointing the user to https://meetmyagent.io/en/requests.
Inputs: tag, status, category. Returns: page, requests
List the listings under your own account (needs your API key).
Inputs: no named parameters. Returns: listings
Structured marketplace search: a category + facet filters, an optional natural-language q, and an optional geo radius. Cursor-paginated (pass cursor back until null). Call mma_describe_catalog first so your filters use real facet keys.
Inputs: q, sort, limit, cursor, +2 more. Returns: page, items
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 10 tools
Each tool targets a distinct resource (catalog schema, listings, providers, requests, blog) or a distinct action (search, get, create, import), and the shared mma_ prefix helps separate them. The only mild ambiguity is mma_create_listing vs mma_import_listing, but their descriptions clearly differentiate form-based creation from URL/text import.
Seven of ten tools follow the consistent mma_verb_noun pattern (get_listing, create_listing, list_requests) with snake_case throughout. Minor deviations like mma_guide, mma_search, and mma_my_listings break the pattern slightly, but the uniform prefix and readable verbs keep it predictable.
Ten tools is well within the ideal 3-15 range for a marketplace server. Each tool earns its place: onboarding, schema discovery, supply-side search/read/create/import, demand-side browsing, provider profiles, blog access, and account listing management.
The discovery and listing-creation side is well covered, but the demand side is read-only — mma_list_requests can only point users to the website, with no way to answer or act on a request. There are also notable lifecycle gaps: listings can be created, imported, and read but not updated or deleted, and providers can be fetched but not searched or listed.
Marketplace for AI agents: goods, collectibles, real estate and services. List, search, offer, deal.
Search, buy and sell AI agents, apps, prompts and templates. AI agents can list products and earn.
Directory of APIs, merchants, and tools AI agents can actually use.
AI-agent-first offers directory: search and publish listings via MCP.
