Skip to main content
Glama
kanishk393

MDM MCP

by kanishk393
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to MDM MCP

No user-submitted related servers found.

    Related Servers

    • agent-crm

      clayton
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to manage CRM data including companies, contacts, prospects, pipelines, forecasts, and tasks via typed MCP tools, with local SQLite storage and a JSON CLI.
      MIT

    • fancy-api

      carmelosantana
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that enables AI agents to read and write records in a live REST API generated from pasted data, with tools for listing, querying, inserting, updating, and deleting records.
      AGPL 3.0

    • Lumena MCP Server

      QuantmindSSI
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to store, search, assemble, and manage local-first memories through seven MCP tools, including conversation turns, feedback, status, and dashboard access without cloud dependencies.
      AGPL 3.0

    • ERP MCP Server

      mulangph
      F
      license
      Not graded
      quality
      C
      maintenance
      It enables LLMs to query enterprise data such as sales orders, stock levels, and vendor information through structured MCP-compliant tools, using localized JSON databases for demonstration.
      -

    • EpicMe MCP

      epicweb-dev
      F
      license
      C
      quality
      D
      maintenance
      An application that demonstrates the future of user interactions through natural language with LLMs, enabling user registration, authentication, and data interaction exclusively via Model Context Protocol (MCP) tools.
      11
      70
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.5/5.0

    Scored across 16 tools

    Disambiguation5/5

    Every tool targets a distinct resource and action: dataset discovery, schema manipulation, row CRUD, search, validation, aggregation, and file import/export. Even similar operations like update_rows, delete_rows, and search_rows are clearly separated by intent and behavior.

    Naming Consistency5/5

    All 16 tools follow a consistent verb_noun snake_case pattern (create_dataset, add_column, search_rows, export_rows, etc.). The few descriptive verbs like describe_dataset, summarize_dataset, and validate_rows still fit the same predictable convention.

    Tool Count4/5

    At 16 tools, the server is slightly above the ideal 3-15 band, but the count is well-justified by the full CRUD surface for datasets, columns, and rows plus import/export. Each tool has a non-overlapping purpose and earns its place.

    Completeness4/5

    The surface covers dataset lifecycle, column management, row CRUD, search, validation, summarization, and file import/export. Minor gaps exist, such as no rename/update-dataset-metadata operation, but agents can work around these without dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources