N.I.L.O.
N.I.L.O. - Notion Interfaces, Locally Operated - provides a local Notion runtime with shared Core/Runtime modules and thin CLI/MCP adapters.
Web docs: bluewhitep.github.io/notion-nilo
Status
- Core owns shared business logic; Runtime owns shared process and execution lifecycle behavior.
- CLI is the git-like human and Function Calling entrypoint, with explicit short aliases and stable
--jsonerrors. - MCP tools are the structured Agent/LLM entrypoint and reuse Core/Runtime capabilities.
- Background MCP server lifecycle commands are available through
nilo server .... - Local MCP clients use stdio; URL-based local or remote clients use Streamable HTTP. Legacy SSE is not supported.
Remote deployment guidance, authentication, TLS, and reverse-proxy configuration are deferred; current HTTP examples bind to localhost only.
The project is in alpha. Public APIs, CLI commands, and MCP tool contracts may still change before a stable release.
Installation
PyPI release
Install the current release from PyPI:
uv tool install notion-nilo
nilo --help
If you do not use uv, install with pip instead:
pip install notion-nilo
nilo --help
GitHub source
Use this method to install directly from the public source repository:
git clone https://github.com/bluewhitep/notion-nilo.git
cd notion-nilo
uv tool install .
nilo --help
Migration From notion-mcp
The previously published notion-mcp PyPI project remains separate and will not be renamed by PyPI. New releases use:
- PyPI package:
notion-nilo - Python import package:
nilo - CLI command:
nilo - GitHub repository:
bluewhitep/notion-nilo
Existing .notion_mcp/ project context directories and NOTION_MCP_* environment variables are intentionally kept for compatibility in this rename.
Documentation
Web documentation is deployed with GitHub Pages:
Repository documentation is organized by language. The English tree is the source for content decisions:
Common English entrypoints:
Roadmap
- Stabilize the Core/Runtime, CLI, and MCP contracts toward the first stable release.
- Expand remote deployment security guidance before recommending network exposure.
- Keep GitHub source installation available for users who want the latest repository state before a PyPI release.
Development
uv run pytest -q -p no:cacheprovider
uv run ruff check .
uv run mypy src
Live Notion tests require explicit opt-in and real Notion credentials. Do not commit tokens or local configuration files.
Security
Report non-sensitive bugs through GitHub issues. For sensitive security reports, follow SECURITY.md.
Contributing
Pull requests are welcome. See CONTRIBUTING.md before opening a PR.
License
Licensed under the Apache License 2.0.
Metadata
Release files for notion-nilo 0.4.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 |
|---|---|---|---|---|
| notion_nilo-0.4.0.tar.gz | 218.3 kB | With provenance | Details for notion_nilo-0.4.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| notion_nilo-0.4.0-py3-none-any.whl | Python 3 | none | any | Details for notion_nilo-0.4.0-py3-none-any.whl |
Total release size: 331.1 kB
Release files / notion_nilo-0.4.0.tar.gz
| Download URL | notion_nilo-0.4.0.tar.gz |
|---|---|
| Size | 218.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3d100ef5eb2da14d0a2c37f098232ff4a4ae74c426de4d77a64c7aded42a2726
|
|
BLAKE2b-256 checksum How to use checksums |
afdd7bfa3e098157b28c6222cfbce2d3ce4338edd179a7585cc5f6532af0938c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 12, 2026.
Transparency logRelease files / notion_nilo-0.4.0-py3-none-any.whl
| Download URL | notion_nilo-0.4.0-py3-none-any.whl |
|---|---|
| Size | 112.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
bc1df4398400f1680f9e2e9de241cea4940a1b77f8b4897bf65fe0ce7491bb62
|
|
BLAKE2b-256 checksum How to use checksums |
3194e796e3d55f00239a8021e3a75f5fe7c1d8d93495f2d4339ce089a246a535
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 12, 2026.
Transparency logSecurity for notion-nilo 0.4.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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for notion_nilo-0.4.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 12, 2026.
Transparency logA 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.