Query MOF database survey metadata and connect to a bounded scientific workspace for executing scientific tools.
Also known as harrisonmo/MOFi, mofi-tools
- Stars
- 2
- Tools
- —
- Downloads, 30 days
- 187
- Latest version
- 0.1.0
- Last commit
- Oct 30, 2026
- License
- Apache-2.0
What is MOFi MCP?
MOFi queries MOF database survey metadata and connect to a bounded scientific workspace for executing scientific tools.
Summary generated from the project's README
About MOFi MCP server
MOFi provides a local Model Context Protocol server designed for researchers interacting with MOF database survey metadata and scientific workspaces. Users can install the server via PyPI or from source using Python 3.12 or newer. The standalone profile allows for catalog inspection through tools like mof_database_catalog and mofi_tool_catalog without requiring model logins, engine installations, or GPU resources. This profile uses byte-pinned CSV files to provide unverified survey metadata.
For more advanced tasks, the server connects to a specific MOFi source checkout to access a bounded scientific workspace. This setup requires pointing the server to a workspace path, a science-python executable, and a hub configuration file. When connected to a workspace, the server advertises available hub tools and utilizes existing schemas, schedulers, and evidence ledgers. Users should provide a separate session directory for each client to manage tool calls and budget reservations effectively.
What you can do with it
- 1Execute scientific toolsRun calculations within a configured scientific workspace using specific hub tools.
- 2Manage computational budgetsPerform tool calls that operate within the predefined budget reservations of the scientific hub.
Written from the project's README. Every use case is checked against a quote from it.
How to install MOFi MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall MOFi MCP in Claude Code
$ claude mcp add mofi -- uvx mofi-toolsInstall MOFi MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"mofi": {
"command": "uvx",
"args": [
"mofi-tools"
]
}
}
}Install MOFi MCP in VS Code
.vscode/mcp.json
{
"servers": {
"mofi": {
"type": "stdio",
"command": "uvx",
"args": [
"mofi-tools"
]
}
}
}Install MOFi MCP in VS Code CLI
$ code --add-mcp '{"name":"mofi","type":"stdio","command":"uvx","args":["mofi-tools"]}'Install MOFi MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"mofi": {
"command": "uvx",
"args": [
"mofi-tools"
]
}
}
}Install MOFi MCP in Codex
$ codex mcp add mofi -- uvx mofi-toolsInstall MOFi MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.mofi] command = "uvx" args = ["mofi-tools"]
Install MOFi MCP in Gemini CLI
$ gemini mcp add -s user mofi uvx -- mofi-toolsInstall MOFi MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"mofi": {
"command": "uvx",
"args": [
"mofi-tools"
]
}
}
}Automated checks
Ran Nov 14, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachableharrisonmo/mofi is public and reachablegithub.com/harrisonmo/mofi ↗Pass
- Package names this repository as its sourcemofi-tools names harrisonmo/mofi as sourcepypi.org/project/mofi-tools/ ↗Pass
- Build provenance (Sigstore attestation)Sigstore attestation for mofi-toolspypi.org/project/mofi-tools/ ↗Pass
- Open source license (OSI)Apache-2.0spdx.org/licenses/Apache-2.0.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-10-30github.com/harrisonmo/mofi ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNo popular package one edit away from mofi-toolsPass
- No critical advisory in the package or its dependencies30 resolved dependencies checked; no critical advisoryosv.dev ↗Pass
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubMOFi tools
mofi-tools provides a local Model Context Protocol server for MOFi's bounded
scientific tools. The unrelated PyPI package named mofi is not this project.
Install from PyPI
python -m pip install mofi-tools==0.1.0
mofi-tools catalog
mofi-mcp
With uv, run the stdio server using uvx --from mofi-tools==0.1.0 mofi-tools serve.
The public MCP Registry identity is io.github.harrisonmo/mofi; its package
metadata is maintained in the repository's server.json.
Install from source
Python 3.12 or newer is required:
python -m pip install ./packages/mofi-tools
mofi-tools catalog
mofi-tools query --arguments '{"name_contains":"QMOF"}'
mofi-mcp
The standalone profile provides mof_database_catalog, mofi_tool_catalog, and
the mofi://catalog resource. It bundles the byte-pinned CSV and reviewed sidecar.
The table is unverified survey metadata, not MOF structures or reference labels.
No model login, model call, engine installation or GPU is needed for this profile.
Scientific workspace
Point the installed server at a separately prepared MOFi source checkout:
mofi-mcp --workspace /path/to/MOFi \
--science-python /path/to/science-environment/bin/python \
--hub-config configs/science-hub.json --session runs/mcp-client
Only configured and available hub tools are advertised. The adapter reuses the hub's schemas, scientific validation, scheduler, budget reservations and evidence ledgers. The science interpreter needs the workspace's scientific dependencies; Crystal-Builder, ARIA and external engines are not bundled in this package. Give each client a separate session directory. Tool calls may run calculations within the operator's configured budget; catalog inspection makes no model calls.
Standard output carries MCP messages only. Diagnostics and engine output use standard error. Native jobs keep the hub's existing interruption accounting; a client timeout does not prove that a calculation stopped or refund its budget.
See MCP setup and packaging for Codex, Claude Code, Claude Desktop, building and release steps.
Original code uses Apache-2.0; see LICENSE and NOTICE. Scientific dependencies retain their own licenses. No credentials, model weights, engine binaries, development records or scientific run output are part of the distribution.
MOFi MCP questions
How do I add MOFi MCP to Claude Code?
Run claude mcp add mofi -- uvx mofi-tools in your terminal. Add --scope user to make it available in every project.
How do I add MOFi MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
Does this server require a model login or GPU?
No, the standalone profile does not require model login, model calls, engine installation, or a GPU.
What is included in the standalone profile?
The standalone profile includes the mof_database_catalog, mofi_tool_catalog, and the mofi://catalog resource, bundling byte-pinned CSV and reviewed sidecar.
Are scientific engines like Crystal-Builder bundled with this package?
No, Crystal-Builder, ARIA, and external engines are not included in this package and must be provided by the workspace.