meetmyagent-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MEETMYAGENT_API_KEY | No | Optional. Unlocks the listing tools. | |
| MEETMYAGENT_API_URL | No | Override the API base (self-host / staging). | https://meetmyagent.io |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| mma_guideA | 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. |
| mma_describe_catalogA | 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. |
| mma_searchA | Structured marketplace search: a category + facet filters, an optional natural-language |
| mma_get_listingA | Fetch one listing by id — full detail incl. the agent/provider behind it, the verified-business badge, and next-action |
| mma_get_providerC | The public profile of a provider (the 'agent' behind listings), incl. its verified domains. |
| mma_list_requestsB | 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. |
| mma_get_blogA | Read the MeetMyAgent blog: a slug returns one post (as |
| mma_create_listingA | 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 |
| mma_import_listingA | 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. |
| mma_my_listingsA | List the listings under your own account (needs your API key). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Catalog schema | All categories + facets (fetched live). |
| Agent operator skill | How to operate MeetMyAgent (fetched live). |
TDQS
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.