ladon-nous
MCP server exposing Ladon crawl data to AI agents.
ladon-nous (νοῦς — the Greek principle of divine intellect) is the mind interface
of the Ladon crawler framework. It serves
crawled data from a DuckDB database over the
Model Context Protocol (MCP), making it
available to Claude Desktop, Cursor, and other MCP-compatible AI clients.
What it does
Point ladon-nous at a DuckDB file produced by a Ladon adapter (e.g.
ladon-mimir), and your AI client
can instantly:
- Search articles by keyword across title, summary, and full text
- List crawl runs and check their status
- Read full article content as a resource
Tools
| Tool | Description |
|---|---|
article_search(query, limit=10) |
Keyword search across crawled articles |
run_list(limit=20) |
Recent crawl runs with status and article counts |
crawl_status(run_id) |
Status detail for a specific run |
Resources
| Resource | Description |
|---|---|
ladon://articles/{page_id} |
Full Markdown content of a single article |
Installation
pip install ladon-nous
Or for development:
git clone https://github.com/MoonyFringers/ladon-nous
cd ladon-nous
python -m venv .venv && source .venv/bin/activate
pip install -e ".[dev]"
Usage
ladon-nous serve --db /path/to/mimir.db
The server speaks MCP over stdio by default (compatible with Claude Desktop).
Add --transport sse for HTTP/SSE deployment.
Claude Desktop setup
Add to ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"ladon-nous": {
"command": "/path/to/.venv/bin/ladon-nous",
"args": ["serve", "--db", "/path/to/mimir.db"]
}
}
}
Restart Claude Desktop. The article_search, run_list, and crawl_status
tools will appear automatically.
Compatibility
ladon-nous v0.1.0 is designed for databases produced by
ladon-mimir (Wikipedia adapter).
Support for other Ladon adapters will be added in v0.2.0 via the
LadonMCPAdapter plugin protocol.
License
Apache-2.0. See LICENSE.
Metadata
Release files for ladon-nous 0.2.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 |
|---|---|---|---|---|
| ladon_nous-0.2.0.tar.gz | 10.2 kB | Without provenance | Details for ladon_nous-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ladon_nous-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for ladon_nous-0.2.0-py3-none-any.whl |
Total release size: 19.5 kB
Release files / ladon_nous-0.2.0.tar.gz
| Download URL | ladon_nous-0.2.0.tar.gz |
|---|---|
| Size | 10.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3a96aaceb294855d0494dd857e5c801168a09ed29c49c16ef7e06d3dace2af89
|
|
BLAKE2b-256 checksum How to use checksums |
6c5ca26cf4424cef00372a2110abe4ad78613225f2f984c6538ebb7580cbc055
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.12
|
Release files / ladon_nous-0.2.0-py3-none-any.whl
| Download URL | ladon_nous-0.2.0-py3-none-any.whl |
|---|---|
| Size | 9.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7b9549b48ddbf7d08798e42ce62d679ecd0d7448b33c51a407997b221f95d837
|
|
BLAKE2b-256 checksum How to use checksums |
7cfff5ce2870b318f00a4685c5f4dbf478afc8fdf175f56748492fc723cb5b9e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.12
|
Security for ladon-nous 0.2.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.