MDM MCP
Related Servers
Alternatives to MDM MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables 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
- AlicenseBqualityBmaintenanceProvides an AI assistant with local tools to manage company profiles, financial records, employees, and notes through MCP clients like Cursor, Claude Desktop, and OpenCode, storing data entirely in local files without cloud services or API keys.11MIT
- AlicenseNot gradedqualityDmaintenanceMCP 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
- AlicenseNot gradedqualityBmaintenanceEnables 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
- FlicenseNot gradedqualityCmaintenanceIt 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.-
- AlicenseNot gradedqualityDmaintenanceDynamically generates MCP tools from any OData or OpenAPI spec, enabling natural-language queries via SAP AI Core.MIT
TDQS
Scored across 16 tools
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.
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.
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.
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.