MDEngine MCP server
2026년 10월 29일 커밋AI 클라이언트가 분자 역학 궤적을 검사하고, 시뮬레이션 비디오를 렌더링하며, LAMMPS 시뮬레이션을 분리된 백그라운드 작업으로 실행할 수 있게 합니다.
다른 이름 forcefieldsilicon/mdengine
- 스타
- 0
- Tools
- —
- 다운로드, 30일
- —
- 최신 버전
- 0.7.1
- 마지막 커밋
- 2026년 10월 29일
- 라이선스
- —
MDEngine MCP란?
MDEngine은(는) MCP server입니다. AI 클라이언트가 분자 역학 궤적을 검사하고, 시뮬레이션 비디오를 렌더링하며, LAMMPS 시뮬레이션을 분리된 백그라운드 작업으로 실행할 수 있게 합니다.
프로젝트 README에서 생성된 요약
MDEngine MCP server 정보
MDEngine은 분자 역학을 위한 특화된 워크벤치를 제공하여 AI 에이전트가 궤적을 검사하고 시뮬레이션을 관리할 수 있도록 합니다. 개발자는 로컬 macOS stdio 서버를 사용하여 머신이 절전 모드에 들어가도 계속 실행되는 분리된 백그라운드 작업으로 LAMMPS 시뮬레이션을 실행할 수 있습니다. 이 시스템에는 원자 수, bounding box, 전하 범위 분석 도구뿐만 아니라 산화 또는 증착 프로세스를 위한 특화된 깊이 분석 도구가 포함되어 있습니다.
Windows 또는 Linux 사용자나 로컬 하드웨어가 없는 사용자를 위해 HTTP transport를 통한 hosted GPU tier를 사용할 수 있습니다. 이를 통해 Claude Code 또는 Cursor와 같은 클라이언트가 로컬 설치 없이 원격 엔드포인트로 시뮬레이션 데크를 보내고 결과를 받을 수 있습니다. 사용자는 상태 확인, 로그 보기 또는 실행 취소 도구를 사용하여 이러한 원격 작업을 관리할 수 있습니다. hosted tier에 액세스하려면 크레딧 팩과 연결된 API 키가 필요하며, 이는 OAuth 2.1 동의 프로세스를 통해 관리할 수 있습니다.
활용 사례
- 1시뮬레이션 깊이 분석AI 에이전트가 산화 과정 중 프로브의 침투 깊이를 계산할 수 있습니다.
- 2시뮬레이션 시각화 생성개발자가 분자 궤적의 MP4 비디오 또는 애니메이션 GIF를 요청할 수 있습니다.
- 3원격 GPU 시뮬레이션 실행에이전트가 클라우드 기반 GPU에 LAMMPS 데크를 제출하여 고부하 연산을 수행할 수 있습니다.
- 4실행 중인 데이터 검사연구자가 시뮬레이션이 파일을 계속 작성하고 있는 동안 궤적 파일을 조사할 수 있습니다.
프로젝트의 README를 바탕으로 작성되었습니다. 모든 활용 사례는 해당 내용의 인용문과 대조하여 확인합니다.
MDEngine MCP 설치 방법
형식 확인: 2026년 11월 10일Cursor에 추가Goose에 추가Claude Code에 MDEngine MCP 설치
$ claude mcp add --transport http mdengine https://api.forcefieldsilicon.com/mcpCursor에 MDEngine MCP 설치
~/.cursor/mcp.json
{
"mcpServers": {
"mdengine": {
"url": "https://api.forcefieldsilicon.com/mcp"
}
}
}VS Code에 MDEngine MCP 설치
.vscode/mcp.json
{
"servers": {
"mdengine": {
"type": "http",
"url": "https://api.forcefieldsilicon.com/mcp"
}
}
}VS Code CLI에 MDEngine MCP 설치
$ code --add-mcp '{"name":"mdengine","type":"http","url":"https://api.forcefieldsilicon.com/mcp"}'Codex에 MDEngine MCP 설치
$ codex mcp add mdengine --url https://api.forcefieldsilicon.com/mcpCodex config.toml에 MDEngine MCP 설치
~/.codex/config.toml
[mcp_servers.mdengine] url = "https://api.forcefieldsilicon.com/mcp"
Gemini CLI에 MDEngine MCP 설치
$ gemini mcp add -s user --transport http mdengine https://api.forcefieldsilicon.com/mcpGemini settings.json에 MDEngine MCP 설치
~/.gemini/settings.json
{
"mcpServers": {
"mdengine": {
"url": "https://api.forcefieldsilicon.com/mcp",
"type": "http"
}
}
}자동 검사
2026년 11월 14일에 실행됨전체 보고서 →아직 인증되지 않았습니다. 서버는 80점 이상의 점수, 심각한 결함 없음, 그리고 검사에 충분한 데이터를 갖추어야 합니다. 검사 방식 · 점수를 높이기 위해 수정할 항목
- 소스 저장소 연결 및 접근 가능forcefieldsilicon/mdengine is public and reachablegithub.com/forcefieldsilicon/mdengine ↗통과
- 패키지가 이 저장소를 소스로 명시검사되지 않음
- 빌드 출처(Sigstore 증명)검사되지 않음
- 오픈 소스 라이선스 (OSI)No license결함 발견
- 최근 1년 내 커밋 또는 릴리스Last commit or release 2026-10-29github.com/forcefieldsilicon/mdengine ↗통과
- OpenSSF Scorecard검사되지 않음
- 패키지 이름이 인기 패키지와 유사하지 않음검사되지 않음
- 패키지 및 해당 종속성에 중요한 보안 권고 없음검사되지 않음
- 모델에 대한 숨겨진 지침 없음0 tool descriptions and the README read; no override phrases, credential paths or hidden characters통과
- 파괴적인 도구에 라벨 표시됨검사되지 않음
- 원격 엔드포인트가 MCP 핸드셰이크에 응답initialize answered with protocol 2025-06-18 in 471 ms통과
README
GitHub에서 보기MDEngine
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.
MDEngine MCP 질문
MDEngine MCP를 Claude Code에 추가하려면 어떻게 하나요?
터미널에서 claude mcp add --transport http mdengine https://api.forcefieldsilicon.com/mcp를 실행합니다. 모든 프로젝트에서 사용할 수 있게 하려면 --scope user를 추가합니다.
MDEngine MCP를 Cursor에 추가하려면 어떻게 하나요?
~/.cursor/mcp.json를 열고 mcpServers 아래에 서버를 추가합니다. 위 설치 섹션에 표시된 Cursor 구성을 사용합니다.
별도의 설치 없이 GPU에서 시뮬레이션을 실행할 수 있나요?
네, hosted tier를 사용하면 시뮬레이션 데크를 hosted GPU 엔드포인트로 전송하고 MCP 클라이언트를 통해 결과를 받을 수 있습니다.
시뮬레이션이 실행 중인 상태에서 검사해도 안전한가요?
네, 궤적 리더가 실행 중인 dump 파일을 안전하게 파싱할 수 있으므로, 완료된 프레임을 읽어 실행 중간에 상태를 검사할 수 있습니다.
LAMMPS 작업 실행기를 사용할 때의 보안 위험은 무엇인가요?
LAMMPS 데크는 임의의 shell 명령을 호출할 수 있는 프로그램입니다. 서버에 연결된 AI 에이전트는 사용자의 전체 권한을 가진 상태로 데크를 실행할 수 있습니다.
hosted GPU tier 인증은 어떻게 하나요?
API 키를 붙여넣는 동의 페이지를 통해 OAuth 2.1을 사용하거나, authorization 헤더에 Bearer token으로 키를 직접 전달할 수 있습니다.