Memex for Model Context Protocol
Memex is a tool for Model Context Protocol (MCP) that allows you to analyze web content and add it to your knowledge base.
The tool was inspired by the Memex project by Vannevar Bush.
Requirements
You will need API keys for the following services:
The knowledge base produced by this tool is stored as Markdown files so they can be viewed with any Markdown viewer but Obsidian is recommended.
Installation
pip install mcp-memex
Add the following to your claude_desktop_config.json and replace the placeholders with the actual paths and API keys:
{
"mcpServers": {
"memex": {
"command": "uv",
"args": [
"--directory",
"PATH_TO_LOCAL_MEMEX_REPO",
"run",
"mcp-memex",
"--index",
"PATH_TO_MEMEX_INDEX",
"--workspace",
"PATH_TO_OBSIDIAN_VAULT"
],
"env": {
"ANTHROPIC_API_KEY": "YOUR-API-KEY",
"FIRECRAWL_API_KEY": "YOUR-API-KEY",
"VOYAGE_API_KEY": "YOUR-API-KEY"
}
}
}
}
Usage
Start by asking Claude a question with a list of URLs to reference.
What is the capital of France? "https://en.wikipedia.org/wiki/France"
Once Claude has finished analyzing the content, you will see the results in your Obsidian vault. You can then ask questions about the content and Memex will use the knowledge base to answer your questions.
What is the capital of France?
Development
To run the tool locally, you can use the following command:
npx @modelcontextprotocol/inspector \
uv \
--directory PATH_TO_LOCAL_MEMEX_REPO \
run \
mcp-memex \
--index PATH_TO_MEMEX_INDEX \
--workspace PATH_TO_OBSIDIAN_VAULT
Then open the inspector and connect to the server.
http://localhost:5173?timeout=30000
Metadata
Release files for iflow-mcp_narphorium_mcp-memex 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| iflow_mcp_narphorium_mcp_memex-0.1.0.tar.gz | 10.4 kB | Without provenance | Details for iflow_mcp_narphorium_mcp_memex-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| iflow_mcp_narphorium_mcp_memex-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for iflow_mcp_narphorium_mcp_memex-0.1.0-py3-none-any.whl |
Total release size: 23.4 kB
Release files / iflow_mcp_narphorium_mcp_memex-0.1.0.tar.gz
| Download URL | iflow_mcp_narphorium_mcp_memex-0.1.0.tar.gz |
|---|---|
| Size | 10.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
71a75e020f4f742eba0db6921af20b5433dd730c8c66ec31900c71c5caa462c4
|
|
BLAKE2b-256 checksum How to use checksums |
f466c4d70e8efa18e4acc414611a00aae0f0f55d981403ec897c135eb3d4b799
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.28 {"installer":{"name":"uv","version":"0.9.28","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Debian GNU/Linux","version":"13","id":"trixie","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / iflow_mcp_narphorium_mcp_memex-0.1.0-py3-none-any.whl
| Download URL | iflow_mcp_narphorium_mcp_memex-0.1.0-py3-none-any.whl |
|---|---|
| Size | 12.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
77e2206e0cf7fe6264092436f96baeceb21559b4ac0898986bd816d49803e9c7
|
|
BLAKE2b-256 checksum How to use checksums |
1fc1a432577f7a0b4518151d109742214260813779274e827cb33949fe5a628b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.28 {"installer":{"name":"uv","version":"0.9.28","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Debian GNU/Linux","version":"13","id":"trixie","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for iflow-mcp_narphorium_mcp-memex 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.