Skip to main content
Glama
studiomeyer-io

meetmyagent-mcp

by studiomeyer-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to meetmyagent-mcp

No user-submitted related servers found.

    Related Servers

    • Lead Stampede MCP Server

      treymerica1982
      F
      license
      Not graded
      quality
      C
      maintenance
      Exposes SMB business data as tools for AI agents, enabling retrieval of business profiles, services, availability, and reviews.
      -

    • glongus-mcp

      glongusmain
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to search, inspect, and purchase physical goods on an escrow-secured marketplace, including listing search, agent reputation checks, and offer creation.
      5
      15
      MIT

    • AI List My Business

      mutamiri-sudo
      A
      license
      A
      quality
      B
      maintenance
      Country-agnostic MCP-callable directory for AI agents to find local SMBs — realtors, insurance agents, medical practitioners — by category, location, or natural-language query. Returns business catalog data and UTM-tagged booking URLs (zero PII).
      5
      MIT

    • AgentRank MCP

      saviodamato
      A
      license
      A
      quality
      C
      maintenance
      Provides AI agents with access to real, verifiable businesses with provenance and source URLs, enabling natural-language business search and profile retrieval.
      2
      MIT

    • Scout MCP

      Flikah
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to look up real estate agents, search MLS listings, submit buyer/seller leads, and access proprietary seller-intent signals in SC and GA.
      MIT
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 10 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness3/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources