mcp-oqmd
OQMD (Open Quantum Materials Database) MCP.
Part of Pipeworx — an MCP gateway connecting AI agents to 1683+ live data sources.
Agenten stärken
Die eigene URL des Herausgebers. Kein PlugMCP-Endpunkt.
Host a copy with our keys and logs.
https://gateway.pipeworx.io/oqmd/mcpDie Claude-Schaltfläche oben öffnet Claude mit ausgefülltem Namen und ausgefüllter URL. Sie bestätigen dort noch.
claude mcp add --transport http io.github.pipeworx-io-oqmd https://gateway.pipeworx.io/oqmd/mcpRun in a terminal.
{ "mcpServers": { "io.github.pipeworx-io-oqmd": { "command": "npx", "args": [ "-y", "mcp-remote", "https://gateway.pipeworx.io/oqmd/mcp" ] } }}claude_desktop_config.json
Remote-URL oder ein Befehl auf Ihrem Rechner? Worin sich die beiden Installationen unterscheiden
Auf PlugMCP ausführen
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
StartenVom Herausgeber
OQMD (Open Quantum Materials Database) MCP.
Part of Pipeworx — an MCP gateway connecting AI agents to 1683+ live data sources.
OQMD (Open Quantum Materials Database) MCP.
| Tool | Description |
|---|
search_materials | Search the Open Quantum Materials Database for DFT-computed inorganic materials by composition and/or constituent elements, with optional band-gap and thermodynamic-stability filters. Returns formation energy (eV/atom), energy above the convex hull (stability), band gap, space group, and prototype. Keyless. Provide at least composition or element_set. |
get_material | Fetch a single OQMD material by its entry_id (e.g. 16525 = the Pbcn polymorph of Fe2O3). Returns formation energy (eV/atom), stability above hull, band gap, space group, prototype, cell volume, atom/element counts, ICSD id, and generic composition. Keyless. |
stable_phases | List the ground-state (on-hull) phases of a chemical system — the thermodynamically stable compounds in OQMD for a given set of elements. e.g. "Fe-O" returns FeO, Fe2O3, Fe3O4. Restricts to materials made ONLY of the given elements with stability <= ~0 (on the convex hull). Keyless. |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"oqmd": {
"url": "https://gateway.pipeworx.io/oqmd/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/oqmd/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
Both URLs reach the same gateway and the same 1683+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
curl -X POST https://gateway.pipeworx.io/v1/tools/search_materials \
-H 'Content-Type: application/json' \
-d '{"composition":"Fe2O3"}'
No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/search_materials. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.
This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:
{
"mcpServers": {
"oqmd": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-oqmd"]
}
}
}
Or run it directly to confirm it starts:
npx -y @pipeworx/mcp-oqmd
It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call
for only this pack's tools — none of the shared meta-tools the gateway
connection above adds. Same source, same tools, no ask_pipeworx routing.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Oqmd data" })
The gateway picks the right tool and fills the arguments automatically.
MIT
{ "mcpServers": { "io.github.pipeworx-io-oqmd": { "url": "https://gateway.pipeworx.io/oqmd/mcp", "headers": {} } }}Tools
Noch keine Tool-Liste. Remote-Server erhalten eine nach dem ersten Health-Check.
FAQ
Kopieren Sie auf dieser Seite die http-Konfiguration für Cursor, Claude Desktop, Claude Code oder VS Code. Sie nutzt die Installation des Herausgebers, keinen PlugMCP-Proxy.
Der Herausgeber nennt diese Umgebungsvariablen: PIPEWORX_API_KEY.
Oqmd wird über HTTP erreicht.
Zuletzt geprüft: 2026-11-11. OQMD (Open Quantum Materials Database) MCP.