# MeetMyAgent [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/studiomeyer-io/meetmyagent-mcp  
**GitHub Stars:** 0  
**npm Downloads (last month):** 89  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/meetmyagent

## Description
MeetMyAgent: search the free AI-native marketplace and list your offers, from any MCP client.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "meetmyagent": {
    "command": "npx",
    "args": ["-y","meetmyagent-mcp"],
    "env": {
      "MEETMYAGENT_API_KEY": "",
      "MEETMYAGENT_API_URL": ""
    }
  }
}
```

**Requires environment variables:** `MEETMYAGENT_API_KEY`, `MEETMYAGENT_API_URL` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What MeetMyAgent MCP server does

The MeetMyAgent MCP server package was a local MCP client for MeetMyAgent’s former listing catalog. It connected MCP clients such as Claude Code, Cursor, Claude Desktop, and Codex to the public REST API at `https://meetmyagent.io/v1`. Its intended use was to search listings, inspect providers, browse demand requests, read the blog, and optionally publish a business, service, or product.

The package is retired. The catalog tools described in its reference implementation no longer have an API behind them, so new integrations should not depend on this npm package for live catalog operations.

## How it works

The reference client used stdio and could be launched with `npx -y meetmyagent-mcp`. Public reads were designed to work without an account or API key. Listing operations required an API key with the `listings:write` scope, supplied as an environment variable and sent to MeetMyAgent as a Bearer token.

Responses from the former REST API used an envelope containing fields such as `success`, `result`, `errors`, and pagination information. Clients read returned data from `.result`, used `.result_info.cursor` for pagination, and inspected structured error slugs when an operation failed. The package also advertised JSON output schemas for its tools and provided two MCP resources: `mma://catalog/schema` and `mma://docs/skill`.

For the current MeetMyAgent product, the documented connection is the hosted MCP server at `https://meetmyagent.io/mcp`. It uses OAuth 2.1 and exposes capabilities according to the permissions approved during connection; its available tools are not necessarily the same as the retired package’s catalog surface.

## Setup and configuration

The historical local setup used a standard MCP stdio configuration:

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

`MEETMYAGENT_API_KEY` was optional for public reads and required for the former listing-write tools. `MEETMYAGENT_API_URL` defaulted to `https://meetmyagent.io` and could override the API base for staging or self-hosted deployments. The README directed users to create listing keys through the MeetMyAgent console.

## Tools and capabilities

The reference implementation listed these public tools:

- `mma_guide` for the platform’s operating instructions.
- `mma_describe_catalog` for the catalog’s facet schema.
- `mma_search` for category, facet, semantic-query, and geographic searches.
- `mma_get_listing` and `mma_get_provider` for individual records and provider profiles.
- `mma_list_requests` for browsing posted demand.
- `mma_get_blog` for reading blog content.

With the former write scope, it also exposed `mma_create_listing`, `mma_import_listing`, and `mma_my_listings`. These capabilities should be treated as reference documentation rather than a currently supported catalog integration.

## Limitations and notes

The MeetMyAgent MCP server package is explicitly retired, and its catalog backend is no longer available through the code shown in the repository. The local package did not cover MeetMyAgent’s sign-in flow, sales network, credits, or other platform areas. ChatGPT and other remote clients were directed to the hosted OAuth server instead of the npm package. The repository states that the package is licensed under MIT.

_Full upstream README: https://allmcps.com/mcp/meetmyagent/readme_