MDEngine MCP server
Commit 29 Okt 2026Memungkinkan AI client untuk menginspeksi trajektori dinamika molekuler, merender video simulasi, dan menjalankan simulasi LAMMPS sebagai detached background jobs.
Juga dikenal sebagai forcefieldsilicon/mdengine
- Stars
- 0
- Tools
- —
- Unduhan, 30 hari
- —
- Versi terbaru
- 0.7.1
- Commit terakhir
- 29 Okt 2026
- Lisensi
- —
Apa itu MDEngine MCP?
MDEngine adalah MCP server. Memungkinkan AI client untuk menginspeksi trajektori dinamika molekuler, merender video simulasi, dan menjalankan simulasi LAMMPS sebagai detached background jobs.
Ringkasan dibuat dari README proyek
Tentang MDEngine MCP server
MDEngine menyediakan workbench khusus untuk dinamika molekuler, yang memungkinkan AI agent untuk menginspeksi trajektori dan mengelola simulasi. Developer dapat menggunakan local macOS stdio server untuk menjalankan simulasi LAMMPS sebagai detached background jobs yang tetap berjalan meskipun mesin dalam mode sleep. Sistem ini mencakup tools untuk menganalisis jumlah atom, bounding boxes, dan rentang muatan, serta analisis kedalaman khusus untuk proses oksidasi atau deposisi.
Bagi pengguna Windows atau Linux, atau mereka yang tidak memiliki hardware lokal, tersedia hosted GPU tier melalui HTTP transport. Hal ini memungkinkan client seperti Claude Code atau Cursor untuk mengirimkan simulation decks ke remote endpoint dan menerima hasil tanpa perlu instalasi lokal apa pun. Pengguna dapat mengelola remote jobs ini menggunakan tools untuk memeriksa status, melihat log, atau membatalkan proses yang sedang berjalan. Akses ke hosted tier memerlukan API key yang terhubung dengan paket kredit, yang dapat dikelola melalui proses consent OAuth 2.1.
Apa yang bisa Anda lakukan dengannya
- 1Analisis kedalaman simulasiAI agent dapat menghitung kedalaman penetrasi sebuah probe selama proses oksidasi.
- 2Generate visualisasi simulasiDeveloper dapat meminta video MP4 atau GIF animasi dari sebuah trajektori molekuler.
- 3Jalankan simulasi GPU jarak jauhSeorang agent dapat mengirimkan LAMMPS deck ke GPU berbasis cloud untuk melakukan komputasi berat.
- 4Inspeksi data saat proses berjalanSeorang peneliti dapat memeriksa file trajektori saat simulasi masih aktif menulis data ke dalamnya.
Ditulis berdasarkan README proyek. Setiap use case diperiksa terhadap kutipan dari README tersebut.
Cara menginstal MDEngine MCP
Format diverifikasi 10 Nov 2026Tambahkan ke CursorTambahkan ke GooseInstal MDEngine MCP di Claude Code
$ claude mcp add --transport http mdengine https://api.forcefieldsilicon.com/mcpInstal MDEngine MCP di Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"mdengine": {
"url": "https://api.forcefieldsilicon.com/mcp"
}
}
}Instal MDEngine MCP di VS Code
.vscode/mcp.json
{
"servers": {
"mdengine": {
"type": "http",
"url": "https://api.forcefieldsilicon.com/mcp"
}
}
}Instal MDEngine MCP di VS Code CLI
$ code --add-mcp '{"name":"mdengine","type":"http","url":"https://api.forcefieldsilicon.com/mcp"}'Instal MDEngine MCP di Codex
$ codex mcp add mdengine --url https://api.forcefieldsilicon.com/mcpInstal MDEngine MCP di Codex config.toml
~/.codex/config.toml
[mcp_servers.mdengine] url = "https://api.forcefieldsilicon.com/mcp"
Instal MDEngine MCP di Gemini CLI
$ gemini mcp add -s user --transport http mdengine https://api.forcefieldsilicon.com/mcpInstal MDEngine MCP di Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"mdengine": {
"url": "https://api.forcefieldsilicon.com/mcp",
"type": "http"
}
}
}Pengecekan otomatis
Berjalan 14 Nov 2026Laporan lengkap →Belum diverifikasi. Sebuah server memerlukan skor 80, tidak ada temuan serius, dan data yang cukup untuk kami periksa. Cara kerja checks · Yang perlu diperbaiki untuk menambah poin
- Source repository terhubung dan dapat dijangkauforcefieldsilicon/mdengine is public and reachablegithub.com/forcefieldsilicon/mdengine ↗Lolos
- Nama paket mencantumkan repositori ini sebagai sumbernyaTidak diperiksa
- Provenance build (atestasi Sigstore)Tidak diperiksa
- Lisensi open source (OSI)No licenseTemuan
- Ada commit atau release dalam satu tahun terakhirLast commit or release 2026-10-29github.com/forcefieldsilicon/mdengine ↗Lolos
- OpenSSF ScorecardTidak diperiksa
- Nama package tidak mirip dengan package populerTidak diperiksa
- Tidak ada advisory kritis pada paket atau dependensinyaTidak diperiksa
- Tidak ada instruksi tersembunyi untuk model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersLolos
- Tools yang bersifat destruktif telah diberi labelTidak diperiksa
- Endpoint remote merespons handshake MCPinitialize answered with protocol 2025-06-18 in 471 msLolos
README
Lihat di GitHubMDEngine
by ForceField Silicon
A molecular-dynamics workbench with a LAMMPS MCP server for Claude and other agents: a native macOS Metal trajectory viewer, a command-line tool, and an MCP server that inspects trajectories and runs LAMMPS simulations as detached background jobs. The hosted tier runs the same jobs on a GPU: Claude sends a deck to the molecular dynamics MCP server at api.forcefieldsilicon.com and gets the results back, with nothing to install.
Start here
- Claude Code:
claude mcp add --transport http mdengine-cloud https://api.forcefieldsilicon.com/mcp - claude.ai: add a custom connector with the URL
https://api.forcefieldsilicon.com/mcp - Claude Desktop: install the
.mcpbbundle from the GitHub release - Your key comes with a credit pack at https://forcefieldsilicon.com/mdengine
- Campaign guides for mineral processing and protein work: https://github.com/forcefieldsilicon/mdengine-plugins
Status: 0.7.1 released. Signed and notarized macOS app, command-line tool, Claude Desktop bundle, and the hosted GPU tier. Release notes: https://github.com/forcefieldsilicon/mdengine/releases
Parts
| Product | What it is |
|---|---|
| MDEngine.app | Metal viewer — orbit / pan / zoom camera, trajectory timeline with 20%/5% tick marks, CPK element colours, XYZ / extended-XYZ, live settings |
| mdengine-cli | info / export / decimate / run on trajectories and decks |
| mdengine-mcp | MCP stdio server — trajectory tools plus a detached LAMMPS job runner (submit_lammps / job_status / job_log / list_jobs / cancel_job) |
Build
Requires macOS 14+ and Xcode command-line tools. LAMMPS (brew install lammps)
is needed only for run / submit_lammps.
swift build -c release # all three products
./scripts/make_app.sh # assemble + install /Applications/MDEngine.app
Bundled examples
| Example | What it shows |
|---|---|
lj_melt.xyz / lj_melt.in |
Lennard-Jones argon melt — the minimal smoke test |
fe_oxidation.xyz / fe_oxidation.in |
ReaxFF iron oxidation: a bcc Fe slab meeting O₂ gas, using ffield.reax.Fe_O_C_H from the LAMMPS distribution |
Trajectory readers are safe on in-flight dumps — a file a running simulation is still writing parses to its complete frames, so you can inspect a run mid-flight. Rows with non-finite (NaN/inf) coordinates are dropped.
Both decks are ready inputs for mdengine run and submit_lammps. Bare
force-field names resolve automatically: if $LAMMPS_POTENTIALS is unset,
MDEngine derives it from the LAMMPS install.
MCP server
mdengine-mcp is a dependency-free MCP stdio server, listed in the
MCP Registry as
com.forcefieldsilicon/mdengine (server.json in this repo). Each release ships a
signed macOS MCP Bundle
(mdengine-mcp-<version>-macos-arm64.mcpb): double-click it to install in Claude
Desktop, or unpack it (mcpb unpack) for any other client. Built from source, register
with Claude Code:
claude mcp add mdengine /path/to/.build/release/mdengine-mcp
or in Claude Desktop's claude_desktop_config.json:
{ "mcpServers": { "mdengine": { "command": "/path/to/.build/release/mdengine-mcp" } } }
| Tool | Does |
|---|---|
trajectory_info |
Frames, atom counts, per-atom fields, elements, bbox, charge range |
z_profile |
Deposition/oxidation depth analysis: substrate surface plane, probe penetration depths (min/mean/max), at-surface & in-flight counts, bound-probe charge, z histogram |
render_video |
Trajectory → MP4 (H.264) or animated GIF via the Metal renderer: camera angles, stride, cinematic orbit, baked scale-bar/frame annotations, per-element colors/sizes, style: "contrast" auto-visibility |
render_image |
One frame → PNG with the same camera/style options — lets an agent see a simulation state |
export_frame |
One frame → XYZ; charges: true → extended-XYZ with the q column |
decimate |
Keep every Nth frame (final frame always kept) |
submit_lammps |
Detached LAMMPS job: survives the server exiting and machine display-sleep (caffeinate), exit code recorded unattended |
job_status / job_log |
State + live thermo tail / raw log tail |
job_files |
Locate a finished job's outputs (run dir + bookkeeping dir) |
list_jobs / cancel_job |
Registry under ~/.mdengine/jobs/ / SIGTERM a run (state becomes cancelled) |
list_hosts |
Execution hosts from ~/.mdengine/hosts.json and which is the default |
fetch_job |
Pull a remote job's run directory (dumps, data) + logs into the local job dir under results/ |
run_lammps |
Synchronous run for short tests only |
buy_credits |
Opens the credit page to top up the hosted GPU key |
Hosted GPU tier over MCP (no install)
The same jobs are reachable from any MCP client that speaks HTTP — Claude Code, Claude.ai custom connectors, Cursor, Goose — via the hosted endpoint's Streamable HTTP server:
claude mcp add --transport http mdengine-cloud https://api.forcefieldsilicon.com/mcp
Sign in when the client asks (OAuth 2.1: a consent page where you paste your API key once; the
client keeps a token, the key stays with you). Scripted clients may instead send the key directly
as --header "Authorization: Bearer mde_YOUR_KEY". The key comes with a prepaid credit pack
(forcefieldsilicon.com/mdengine). initialize and
tools/list work without signing in; tool calls without a credential return 401 with the OAuth
Windows and Linux. The hosted tier is the supported path on both, and it is the full paid
product: every tool below works from Claude Code on Windows exactly as on a Mac. In PowerShell,
register at user scope so the server follows you into every folder, then sign in once:
claude mcp add --scope user --transport http mdengine-cloud https://api.forcefieldsilicon.com/mcp
Start claude, type /mcp, pick mdengine-cloud, choose Authenticate, and paste the key on the
browser consent page (never into the chat). Decks written on Windows (CRLF line endings) are
accepted as-is. The local viewer, renderer and CPU job runner are macOS-only today; a Windows/Linux
local build is planned and demand decides its order, so say so if you need it.
discovery pointer, which is what makes clients offer the sign-in. Tools: account, capabilities, preflight_deck, submit_job (deck inline, ≤ 8 MB),
create_job + start_job (big decks via presigned PUT), job_status, job_log,
job_results, list_jobs, delete_results, cancel_job (12 tools). Discovery card:
https://api.forcefieldsilicon.com/.well-known/mcp/server-card.json. The hosted service (endpoint, billing, GPU launcher) is operated by ForceField Silicon and its
source is not part of this repository; the client side of it (HostedClient, CLI run --gpu,
MCP host=cloud) is here under the same license as everything else.
Preflight before spend (GJOB-118). GET /v1/capabilities publishes the hosted image's LAMMPS
version, packages and every style with a gpu flag: true = KOKKOS-accelerated, false = the style
exists but runs on the pod's CPU cores at the GPU rate. Every client checks a deck against it first —
mdengine capabilities deck.in, the app's Run Accelerated, submit_lammps host=cloud, the hosted
submit_job — refusing a deck whose styles the image lacks (LAMMPS would exit at startup) and warning
when the pair style has no /kk variant (the run would not use the GPU). --force / force=true
overrides; the server only advises (preflight in the start response), it never blocks.
Troubleshooting the hosted connector:
| Symptom | Cause / fix |
|---|---|
| Client says authentication required / 401 | Use the client's sign-in (OAuth) and paste your mde_… key on the consent page, or add the header Authorization: Bearer mde_…. Keys are issued at purchase and shown once. |
| Consent page says the key was not recognised | Keys are mde_ + 32 hex characters; a revoked key no longer works. mdengine account prints the balance for a saved key. |
| "insufficient balance" | Top up at forcefieldsilicon.com/mdengine; submissions need credit for at least 15 min at the GPU rate. |
| "gpu_runners_open_soon" (503) | Runners are temporarily closed; credits are safe. |
| HTTP 429 | Too many keyless requests from one IP; add the key or slow down. |
job_results says results unavailable |
Files were deleted by delete_results, the run produced none, or the 30-day purge ran. |
Job failed with runner_error / lammps_error |
The deck itself failed; job_results (if present) or job_log holds the LAMMPS error text. |
Job failed with pod_lost / no_capacity / launch_timeout / gpu_unavailable |
Infrastructure (pod died, no GPU stock, a pod that never came up, or the host handed the pod no CUDA device); never billed, relaunched once automatically. Resubmit if it still fails. |
Jobs run in the deck's own directory (relative read_data paths work) and
launch with -sf omp -pk omp N so the OPENMP package is actually engaged;
$LAMMPS_POTENTIALS is derived from the LAMMPS install when unset.
Remote hosts (run on your own Linux / GPU box)
The job runner can execute on another machine with the same tool contract:
declare hosts in ~/.mdengine/hosts.json and pass host to submit_lammps
(or set a default). The deck's directory is rsynced up (trajectories,
checkpoints and logs excluded), LAMMPS starts under nohup with its exit code
recorded remotely, and job_status / job_log / job_files / cancel_job
work unchanged; fetch_job brings results back for trajectory_info,
z_profile and the renderers.
{
"default": "gpu1",
"hosts": {
"gpu1": {
"ssh": "me@gpu1.example.net",
"workdir": "~/mdengine-jobs",
"lmp": "/usr/local/bin/lmp",
"threads": 8,
"launch": "{lmp} -in {input} -k on g 1 -sf kk -pk kokkos newton on neigh half -log {log}"
}
}
}
ssh is anything ssh accepts (key-based, non-interactive); lmp must be an
absolute path (login PATH is not available over ssh); launch is optional —
the default is the OpenMP form, and a GPU host is simply one whose template
carries the KOKKOS flags. A remote deck must be self-contained within its own
directory. The same trust model as local runs applies, on the remote machine.
Platform & limits
macOS 14+ (Apple Silicon or Intel). Trajectories are loaded whole into memory — files over 2 GB are refused with guidance to decimate or split first.
Security note
Running a LAMMPS input executes whatever the deck says. LAMMPS decks are
programs, not data — they can invoke arbitrary shell commands (LAMMPS has a
literal shell command). Treat a deck from someone else exactly like a shell
script: read it before running it.
This applies doubly to the MCP server: an AI agent connected to
mdengine-mcp can submit decks, and a submitted deck runs with your user's
full privileges on this machine. That is the same trust model as any local
dev tool (an agent that can run make can run anything), but be deliberate
about which decks — and which agents — you hand to the job runner. Sandboxed
execution (containers, no network, resource caps) is how a future hosted tier
makes running untrusted decks safe; the local server does not sandbox.
Privacy
The local tools collect nothing; see PRIVACY.md, which also covers the hosted GPU tier.
License
Business Source License 1.1 (BUSL-1.1), © 2026 Gitinama Inc. (ForceField Silicon). See LICENSE.
In short: you may read, copy, modify and redistribute MDEngine, and you may use it in production for your own research, engineering or commercial work, on your own machines or on machines you rent. The one thing the license withholds is offering MDEngine itself, or a service whose value comes mainly from it, to third parties as a hosted, managed or embedded service. Each version converts to the Mozilla Public License 2.0 four years after its first public release. Versions 0.7.0 and earlier were released under MIT and stay MIT. Other arrangements: arvand@gitinama.tech.
Pertanyaan tentang MDEngine MCP
Bagaimana cara menambahkan MDEngine MCP ke Claude Code?
Jalankan claude mcp add --transport http mdengine https://api.forcefieldsilicon.com/mcp di terminal Anda. Tambahkan --scope user agar tersedia di semua proyek.
Bagaimana cara menambahkan MDEngine MCP ke Cursor?
Buka ~/.cursor/mcp.json dan tambahkan server di bawah mcpServers, menggunakan config Cursor yang ditunjukkan di bagian instalasi di atas.
Bisakah saya menjalankan simulasi pada GPU tanpa menginstal apa pun?
Ya, tier hosted memungkinkan Anda mengirimkan simulation decks ke endpoint GPU hosted dan menerima hasilnya kembali melalui MCP client.
Apakah aman untuk menginspeksi simulasi saat masih berjalan?
Ya, trajectory readers dapat memproses in-flight dumps dengan aman, sehingga Anda dapat menginspeksi proses yang sedang berjalan dengan membaca frame yang sudah lengkap.
Apa risiko keamanan saat menggunakan LAMMPS job runner?
LAMMPS decks adalah program yang dapat memanggil shell commands secara arbitrer; AI agent yang terhubung ke server dapat menjalankan decks dengan hak akses penuh user Anda.
Bagaimana cara autentikasi dengan hosted GPU tier?
Anda dapat menggunakan OAuth 2.1 melalui consent page tempat Anda menempelkan API key, atau mengirimkan key tersebut secara langsung sebagai Bearer token di authorization header.