Atomistic Toolkit MCP Server

Created By
XirtamEsrevnia year ago
An MCP-compatible server providing atomistic simulation capabilities through ASE, pymatgen, etc.
Overview

What is Atomistic Toolkit MCP Server?

The Atomistic Toolkit MCP Server is an MCP-compatible server that provides atomistic simulation capabilities using tools like ASE and pymatgen, along with machine learning interatomic potentials (MLIPs).

How to use Atomistic Toolkit MCP Server?

To use the server, you can set it up by following the instructions in the GitHub repository. Users can perform atomistic simulations by utilizing the provided tools for structure creation, manipulation, and optimization.

Key features of Atomistic Toolkit MCP Server?

  • Compatibility with MCP for atomistic simulations
  • Integration with ASE for structure manipulation and optimization
  • Support for machine learning interatomic potentials (MLIPs)
  • File I/O operations for reading and writing structures

Use cases of Atomistic Toolkit MCP Server?

  1. Conducting atomistic simulations for material science research.
  2. Optimizing molecular geometries for various compounds.
  3. Utilizing machine learning for predicting interatomic interactions.

FAQ from Atomistic Toolkit MCP Server?

  • Is the Atomistic Toolkit MCP Server fully functional?

No, the project is under active development, and not all features are fully operational yet.

  • What programming language is used for the server?

The server is developed in Python.

  • Is there a license for the project?

Yes, the project is licensed under the MIT license.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
XirtamEsrevni
Star
0
Language
Python
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago