Aicommander
Outbound-only remote shell, detached long-running jobs and temporary file transfer for AI agents, without exposing SSH, ports or a VPN.
Install
The installation steps are in the documentation below. Documentation
Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
Contents
AI Commander
AI Commander gives AI agents secure remote access to computers you control. It can inspect machine availability, run shell commands, manage detached background jobs, capture opted-in desktop screenshots, and transfer files without exposing SSH or opening inbound ports.
This public repository contains:
- the open-source AI Commander plugin for Cursor;
- signed application release artifacts and their checksums through GitHub Releases.
It does not contain the proprietary source code of the AI Commander desktop application, machine agent, or hosted relay service.
Cursor plugin
The plugin connects Cursor to the hosted Streamable HTTP MCP endpoint:
https://aicommander.dev/mcp
Cursor starts the OAuth flow when account access is needed. After signing in, the plugin can work with machines linked to that AI Commander account. Tool calls that execute commands, stop jobs, or write files can change or delete data on the selected machine; review the target and requested action before approving them in Cursor.
Installing the plugin is free. The hosted AI Commander service provides a Free plan and optional paid Pro features; current plan limits and purchase terms are described on the public privacy-and-terms page linked below.
Test locally
- Clone this repository into
~/.cursor/plugins/local/aicommander. - In Cursor, run Developer: Reload Window.
- Open Settings → Plugins → Installed and confirm that AI Commander is present.
- Ask: “List my AI Commander machines and show which are online.”
- Complete OAuth when Cursor opens the AI Commander sign-in page.
The plugin consists of the manifest at
.cursor-plugin/plugin.json, the MCP configuration at mcp.json, and the
marketplace logo at assets/logo.png. Its version is independent of desktop,
agent, and hosted-service release numbers.
Downloads
- Latest installers: https://aicommander.dev/ or GitHub Releases
- Machine-readable release metadata: https://aicommander.dev/dist/latest
- Immutable versioned artifacts:
https://aicommander.dev/dist/v/<version>/
Verifying downloads
Every release ships a SHA256SUMS manifest covering all artifacts.
- macOS: DMG, PKG, and ZIP artifacts are Apple Developer ID signed and
notarized. Verify checksums with
shasum -a 256 -c SHA256SUMS. - Windows: the NSIS installer is Authenticode-signed. Verify its checksum
with
certutil -hashfile AICommander-Setup.exe SHA256. - Linux agent: detached Ed25519 signatures and
.sha256files are published alongside the binary. The documented install flow verifies them before running anything with elevated privileges.
Documentation and support
- Documentation: https://aicommander.dev/docs/
- Setup guide: https://aicommander.dev/howto/
- Privacy policy and terms: https://aicommander.dev/privacy/
- Support: <support@coderai.dev>
- Issues and questions: use this repository's issue tracker.
License scope
The files in this repository — the Cursor plugin, MCP configuration,
Glama/stdio evaluation files (Dockerfile, package.json, glama.json),
and this documentation — are available under the MIT License. AI Commander
trademarks, release binaries, desktop and agent applications, and the hosted
service are not relicensed by that grant and remain subject to their applicable
product terms.
Frequently asked questions
What is Aicommander?
Outbound-only remote shell, detached long-running jobs and temporary file transfer for AI agents, without exposing SSH, ports or a VPN.
How do I install Aicommander?
Follow the installation steps in its documentation, shown on this page and in its repository.
Is Aicommander open source?
Yes. Its code is on GitHub under the MIT license.
Who maintains Aicommander?
It is published by AICommander-dev. AI.tn lists it but does not maintain or endorse it.
From the community awesome-mcp-servers lists and the project's GitHub repository. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.