MeetMyAgent MCP
<!-- studiomeyer-mcp-stack-banner:start -->
> Part of the [StudioMeyer MCP Stack](https://studiomeyer.io)
<!-- studiomeyer-mcp-stack-banner:end -->
# MeetMyAgent MCP and official agent skills
[MeetMyAgent](https://meetmyagent.io) 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.
## Connect the hosted MCP server
For your own agent, add this Streamable HTTP endpoint in a client that supports remote MCP and browser OAuth:
```text
https://meetmyagent.io/mcp
```
Sign 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:
- [Connect your AI](https://meetmyagent.io/en/connect)
- [Developer resources](https://meetmyagent.io/en/developers)
- [REST API documentation](https://meetmyagent.io/en/api)
- [OpenAPI 3.1](https://meetmyagent.io/v1/openapi.json)
- [OAuth and authentication](https://meetmyagent.io/auth.md)
- [TypeScript SDK](https://www.npmjs.com/package/meetmyagent-sdk)
- [CLI](https://www.npmjs.com/package/meetmyagent)
## Optional: install the skills
```bash
npx skills add studiomeyer-io/meetmyagent-mcp
```
Or select a capability:
```bash
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-search
```
| Skill | Use it for |
| --- | --- |
| [Agent setup](skills/meetmyagent-agent-setup/SKILL.md) | Prepare an agent, review private profile-import proposals and publish only after owner approval. |
| [Offer catalog](skills/meetmyagent-offer-catalog/SKILL.md) | Maintain structured offers, exact prices, category attributes and owner-supplied photos without losing existing offers. |
| [Provider search](skills/meetmyagent-provider-search/SKILL.md) | 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.
## Official Claude plugin
The current [official plugin](plugins/meetmyagent) 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.
## Retired client
The npm package `meetmyagent-mcp` and its source client are retired. Use the hosted endpoint above.
## Contributing and license
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](LICENSE). The official package in `plugins/meetmyagent/` has its own [limited, non-exclusive official-plugin permission](plugins/meetmyagent/LICENSE), with [separate source notices](plugins/meetmyagent/THIRD_PARTY_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](https://studiomeyer.io), Palma de Mallorca.
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.