Veilleur — Discord MCP server
Veilleur is a Windows-local Discord Model Context Protocol (MCP) server. An AI client prepares changes to Discord channels, roles, permissions, and messages; the user approves each plan in a local window before it runs. Veilleur keeps local snapshots and can prepare a rollback.
Veilleur uses a Discord bot token and needs the bot to be invited to an existing server. The bot's permissions and role hierarchy still apply. Deleted messages cannot be restored; recreated channels and roles receive new IDs. A rollback also requires approval.
For installation, configuration, and the limits of backups, see the English README or the French README.
Veilleur was developed with help from AI.
Metadata
Release files for veilleur-discord-mcp 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 | |
|---|---|---|---|---|
| veilleur_discord_mcp-0.1.0.tar.gz | 22.4 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| veilleur_discord_mcp-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 42.9 kB
Release files / veilleur_discord_mcp-0.1.0.tar.gz
| Download URL | veilleur_discord_mcp-0.1.0.tar.gz |
|---|---|
| Size | 22.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8b24ed56559593b2a9b6d28cf3ddd310222fee5aa104a85c50673bb15e481a9a
|
|
BLAKE2b-256 checksum How to use checksums |
d9cef238b0753f2f2fc462362e6149b13d05b8900978a7aa82fbf199b16d8c8b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Oct 28, 2026.
Transparency logRelease files / veilleur_discord_mcp-0.1.0-py3-none-any.whl
| Download URL | veilleur_discord_mcp-0.1.0-py3-none-any.whl |
|---|---|
| Size | 20.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b4f06e5a451ec33de7f87795e05426e95a571a814df5ec9687df36570097bdd4
|
|
BLAKE2b-256 checksum How to use checksums |
69daab3b6a8ae897b4881b88accacc4744889b8c2babdb88fccbc214f13898e5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Oct 28, 2026.
Transparency logSecurity for veilleur-discord-mcp 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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for veilleur_discord_mcp-0.1.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 Oct 28, 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.