
Mif Tools
io.github.varun29ankuSPublished by GitHub account varun29ankuSv0.2.1Updated Oct 24, 2026
Convert, validate, and inspect AI agent memories across formats
Overview
A local MCP server that lets an assistant export, import, validate and inspect AI agent memories in the vendor-neutral MIF format.
- What you can do
- Export memories into the MIF JSON envelope and import them back, auto-detecting mem0, CrewAI, LangChain, generic JSON and Markdown formats. Validate memory documents, including deep checks of UUIDs, references, timestamps and embedding dimensions. Inspect memory files and list the supported formats. Preserve optional data such as memory types, tags, entities, embeddings, knowledge graphs and vendor extensions on round-trip.
- When to use it
- Useful when moving agent memories between systems or providers, or when you want an assistant to check and inspect memory export files before migrating them.
- Requirements
- Runs as a local process over stdio; install the Python package with the MCP extra and start it with the mif mcp command. No accounts, API keys or environment variables are declared.
Installation
In SourceWeft
- Open Mif Tools in the dashboard and add it to a workspace.
- 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
Memory Interchange Format (MIF)
[PyPI] [npm] [License] [Tests] [Docs]
Your AI agent has 6 months of memories in System A. You want to try System B. Without MIF, you lose everything. With MIF:
Done. Your memories are portable.
What is MIF?
A vendor-neutral JSON envelope for AI agent memories. Like vCard for contacts or iCalendar for events — a minimal schema so memories move between providers without data loss.
3 required fields. That's it.
Everything else — memory types, tags, entities, embeddings, knowledge graph, vendor extensions — is optional. Add what you have, ignore what you don't.
Install
Convert Between Formats
Python API
Add MIF to Your MCP Server (10 lines)
Supported Formats
Full Spec
MIF supports optional fields for rich memory data:
- Memory types —
observation,decision,learning,error,context,conversation, and custom types - Entity references — named entities with type and confidence
- Embeddings — model name, dimensions, vector (reuse or regenerate)
- Knowledge graph — entities and relationships with confidence scores
- Vendor extensions — system-specific metadata preserved on round-trip
- Privacy — PII detection and redaction markers
Full specification: spec/mif-v2.md | JSON Schema: schema/mif-v2.schema.json
MCP Server
Expose MIF tools to any MCP-compatible AI client:
Tools: export_memories, import_memories, validate_memories, inspect_memories, list_formats
Adapters & Implementations
Design Principles
- Minimal — 3 required fields. Everything else is optional.
- Extensible — Unknown fields and vendor extensions MUST be preserved on round-trip.
- Vendor-neutral — The schema doesn't favor any implementation.
- Forward-compatible — Importers MUST ignore unknown fields.
Contributing
We welcome adapter implementations for any memory system. See CONTRIBUTING.md.
Related
- Documentation — Full docs site
- MCP SEP #2342 — Original proposal to the Model Context Protocol
- tower-mcp #531 — Tracking issue in tower-mcp
- shodh-memory — Reference implementation (Rust)
- mif-tools on PyPI — Python package
- @varunshodh/mif-tools on npm — npm package
License
Apache 2.0
Source: README.md at commit 2162e8e
Tools
0Version history
1- v0.2.1LatestSep 16, 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