vicsia-system-mcp
MCP server pour piloter le système (macOS + Windows) depuis Claude ou tout autre client MCP — via Vicsia.
Expose des outils pour :
- Lancer une application (
open_app) avec fuzzy match du nom - Ouvrir un chemin / fichier (
open_path) avec garde-fous sécurité - Lister les documents récents (
documents_recents) — ouverts ou modifiés ces 30 derniers jours, groupés par dossier (Recent.lnksur Windows, Spotlight sur macOS) - Chercher un nom (
find_files) dans les ~20 dossiers actifs seulement — jamais tout le disque ; « pas trouvé » signifie « pas dans les dossiers actifs », et le dit - Récupérer des infos système (
system_info: batterie, wifi, micro) - Ouvrir des panneaux de réglages (
open_settings,list_settings_panels)
Installation
uvx vicsia-system-mcp
Ou avec pip :
pip install vicsia-system-mcp
python -m vicsia_system_mcp
Configuration MCP client
{
"mcpServers": {
"vicsia-system": {
"command": "uvx",
"args": ["vicsia-system-mcp"]
}
}
}
Sécurité
- Aucun outil n'exécute du code arbitraire — seulement des commandes shell système via les API natives (
opensur macOS,startsur Windows). open_pathrefuse les chemins contenant des segments sensibles (.ssh,.aws,.kube, credentials…) même si formulés explicitement.list_filesest scopé : pas de~complet, uniquement les dossiers de contenu utilisateur (Documents, Desktop, Downloads, Pictures, Music, Movies/Videos).
Licence
MIT
1 maintainer
Metadata
1 maintainer
Release files for vicsia-system-mcp 1.3.17
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 | |
|---|---|---|---|---|
| vicsia_system_mcp-1.3.17.tar.gz | 36.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| vicsia_system_mcp-1.3.17-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 79.7 kB
Release files / vicsia_system_mcp-1.3.17.tar.gz
| Download URL | vicsia_system_mcp-1.3.17.tar.gz |
|---|---|
| Size | 36.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cd0bc6de4d4409c2c0dc25ef5686200abbc3b8d21b9b0cb05447b7bda8da256e
|
|
BLAKE2b-256 checksum How to use checksums |
0786c05b1bdfc0c2894ac8f77a141650a1fe0120324a8e3acb2b6b0fd8959203
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.13.3 {"installer":{"name":"uv","version":"0.13.3","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / vicsia_system_mcp-1.3.17-py3-none-any.whl
| Download URL | vicsia_system_mcp-1.3.17-py3-none-any.whl |
|---|---|
| Size | 43.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b3f0cfefd8eaa0223a073e7f635b2c2b45b36280bd8ba430c9108247d3765098
|
|
BLAKE2b-256 checksum How to use checksums |
e39792e76020bcccac4aa8cccad5b5b17e00395dcdaa37389f8528637b304898
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.13.3 {"installer":{"name":"uv","version":"0.13.3","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for vicsia-system-mcp 1.3.17
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.
