MOFi

io.github.harrisonmoPublished by GitHub account harrisonmov0.1.0Updated Oct 26, 2026

Query MOF database survey metadata and connect a bounded MOFi scientific workspace.

VerifiedSTDIODesktop onlyDatabasesAI & ML

Overview

AI-generated overview

Local MCP server exposing MOFi's bounded scientific tools: MOF database survey metadata plus an optional configured scientific workspace.

What you can do
  • Browse the bundled MOF database survey metadata catalog and the server's own tool catalog
  • Inspect the catalog resource exposed by the standalone profile
  • Query survey metadata, for example by name substring
  • Connect a separately prepared MOFi workspace and advertise only the configured, available hub tools
  • Run workspace calculations through the hub's schemas, validation, scheduler, budget reservations and evidence ledgers
When to use it
Use it when an assistant needs to look up MOF survey metadata, or when you already maintain a MOFi source checkout and science environment and want its bounded scientific tools reachable over MCP. The standalone catalog profile is enough if you only need metadata inspection.
Requirements
A local Python runtime: Python 3.12 or newer, installed from PyPI as mofi-tools (for example via uvx) or from source. The scientific workspace profile additionally needs a prepared MOFi checkout, a science interpreter with the workspace's scientific dependencies, a hub config and a per-client session directory. No credentials, model login or GPU are needed for the standalone profile.
Before you install
The bundled table is unverified survey metadata, not MOF structures or reference labels. Workspace tool calls may run calculations that consume the operator's configured budget, and a client timeout does not prove a calculation stopped or refund its budget. Crystal-Builder, ARIA and external engines are not bundled, and scientific dependencies keep their own licenses. Give each client a separate session directory.

Installation

In SourceWeft

  1. Open MOFi in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

MOFi 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

bash
python -m pip install mofi-tools==0.1.0mofi-tools catalogmofi-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:

bash
python -m pip install ./packages/mofi-toolsmofi-tools catalogmofi-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:

bash
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.

Source: packages/mofi-tools/README.md at commit 4a73b88

Tools

0
SourceWeft started this package once in an isolated sandbox, without credentials, to list its tools. That failed: the package did not install.

Version history

1
  1. v0.1.0LatestOct 22, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts