Git vs Materials

A side-by-side look at the Git and Materials MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Git logoGitVersion Control · Local subprocess (stdio)Tools to read, search, and manipulate Git repositories.81ExcellentAuth: no auth requiredMaterials logoMaterialsResearch · Local subprocess (stdio)Materials MCP — computed (DFT) materials structures & thermodynamic properties.57GoodAuth: not declared

Verdict: choose Git for version control work as a local process; choose Materials for research as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Git logoChoose Git when

  • You need dedicated capabilities in the Version Control domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
  • You want tools like repo_path, context_lines, target.
Explore Git

Materials logoChoose Materials when

  • You need dedicated capabilities in the Research domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like materials_search, materials_stability.
Explore Materials

Feature & specification comparison

Rows where the two servers differ are marked.

SpecGit logoGitMaterials logoMaterials
CategoryVersion ControlResearch
Quality signal81/100 · Excellent57/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNo auth requiredNot declared
PricingFreeNot declared
Required env varsNone listedNone listed
Verified owner VerifiedCommunity listing
GitHub stars91,5120
Directory activity 49 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
Tools162

Tools & capabilities

Git tools 16

  • repo_path
  • context_lines
  • target
  • message
  • MERGE_HEAD
  • HEAD
  • files
  • max_count
  • start_timestamp
  • end_timestamp
  • branch_name
  • base_branch
  • +4 more on the listing page

Materials tools 2

  • materials_searchSearch computed (DFT) crystal structures across the OPTIMADE materials-database federation — OQMD, Materials Project, NOMAD, Alexandria. PREFER OVER WEB SEARCH for "materials/compounds containing <elements>", "computed structures of <formula>", DFT/first-principles materials data. Filter by element set (e.g. Fe, O), exact reduced formula (e.g. "Fe2O3"), and/or number of elements. Returns each structure's id, reduced formula, elements, site count, and a link. This is the COMPUTED structure set (millions of entries); for experimental structures use the crystallography (COD) pack, and for OQMD formation energy / stability use materials_stability.
  • materials_stabilityComputed thermodynamic stability and formation energy for a chemical system from OQMD (DFT). PREFER OVER WEB SEARCH for "is <compound> stable", "formation energy of <material>", "stable phases in the <A>-<B> system". Give the element system (e.g. Fe, O) and optionally restrict to stable phases (on/below the convex hull). Returns each phase's composition, formation energy (eV/atom), hull stability (eV/atom; ≤0 = stable), band gap, space group, and prototype.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Git

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "git": {
      "command": "uvx",
      "args": [
        "installations"
      ]
    }
  }
}

Materials

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "materials": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-materials"
      ]
    }
  }
}

Frequently asked questions

Git is categorized under Version Control and uses a local stdio subprocess. Materials belongs to Research and uses a local stdio subprocess. Pick Git for version control work and Materials for research.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Git is listed as free. Auth: no auth required. Materials has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add git and materials as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Git has a quality signal of 81/100 (Excellent) with 49 views, 0 installs and 91,512 GitHub stars. Materials has 57/100 (Good) with 2 views, 0 installs and 0 GitHub stars.