matmcp
Related Servers
Alternatives to matmcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables automating materials science research workflows through a multi-agent AI platform, including literature discovery, knowledge extraction, simulation, and document generation.MIT
- AlicenseNot gradedqualityBmaintenanceProvides computed (DFT) materials structures and thermodynamic properties through the Pipeworx MCP gateway, enabling AI agents to query materials data via natural language or tool calls.381 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI-driven first-principles calculations for quantum chemistry and materials science using ABACUS, with tools for SCF, structure optimization, molecular dynamics, band structure, and intelligent parameter suggestions.9GPL 3.0
- AlicenseNot gradedqualityDmaintenanceEnables LLMs to verify the novelty and validity of invented battery materials, with support for searching and validating against a materials database.2MIT
- AlicenseAqualityCmaintenanceAn interactive MCP server for FAIRChem and ASE simulations that allows LLM agents to load a model once and steer relaxations, MD, NEB, phonons, and minima searches mid-flight, with live monitoring and code introspection.171MIT
- FlicenseBqualityAmaintenanceA fail-closed MCP verification layer for DFT-to-MLIP workflows, gating Quantum ESPRESSO data ingestion, MACE/RuNNer dry-run command plans, model comparison, and reference validation behind scientific, software, and numerical checks with explicit PASS/WARN/FAIL/QUARANTINE/NOT_RUN statuses.8-
TDQS
Scored across 5 tools
fetch, fetch_many, and fetch_all all retrieve material information and could be confused at a glance, but their descriptions clearly delineate scope (single, list up to 100, entire database). search and get_phase_diagram_from_elements target distinct operations.
Names use consistent snake_case and verb-based conventions (fetch, fetch_many, fetch_all, search, get_phase_diagram_from_elements). The get_ prefix on one tool is a minor deviation from the fetch_ family but remains readable and predictable.
Five tools is a lean but coherent set for a materials-data retrieval server, with each tool earning its place. It leans slightly thin, with no tools for filtering or property-based queries.
Retrieval is well covered across single/list/all scopes plus search and phase diagrams, but the surface lacks property-based or structural queries and requires client-side filtering after fetch_all, leaving notable gaps for a materials database domain.