AFC Commander (Free Edition)
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@AFC Commander (Free Edition)list all commands in my profile"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
# AFC Commander Free Edition
AFC Commander Free Edition is a JSON-backed command registry and pipeline runner with a Model Context Protocol (MCP) server for Cursor. It is built for teams that want a persistent alias layer for shell commands, profile-based separation between workspaces or projects, and repeatable command execution without hand-maintaining long terminal commands.
## What this project is for
AFC Commander solves a simple operational problem: teams accumulate important shell commands, but those commands are easy to lose, hard to standardize, and tedious to retype. This tool keeps those commands in a durable registry, lets you organize them by profile, and gives you a single command-line interface (CLI) for adding, listing, searching, and executing them.
The repository also includes a local MCP server named `afc-commander-core`, which exposes the same registry and execution capabilities to Cursor through standard input and standard output (stdio). That means agents can work with the command registry without needing direct shell access to your environment.
## Core capabilities
AFC Commander includes:
- Persistent command aliases stored in JSON.
- Profile isolation so different projects or environments can keep separate command sets.
- Command lookup, listing, editing, export, history, and statistics.
- Pipeline support for chaining multiple commands into a repeatable flow.
- Job tracking for longer-running or resumable executions.
- A local MCP server for agent access from Cursor.
## What it does not try to be
This is not a general-purpose task runner, and it is not a replacement for a full CI (continuous integration) system. It is a structured command registry and execution layer for shell workflows you want to keep organized, reusable, and accessible from both the terminal and MCP-aware tooling.
## Requirements
- Node.js 20.12 or newer. Node.js is the JavaScript runtime that executes the CLI and server code.
- npm, the Node.js package manager, for installation.
- Cursor, if you want to register and use the MCP server from the editor.
## Installation
From the repository root:
```bash
node setup.cjsThat setup script:
Installs the package dependencies.
Installs
afc-commander-freeglobally so theafccommand is available in your terminal.Creates a user data directory at
~/.afc-commanderunless you override it withAFC_HOME.Registers the
afc-commander-coreMCP server in~/.cursor/mcp.json.
After setup, reload MCP in Cursor so the server is detected.
Verify the install
afc version
afc help
afc profile listRelated MCP server: Studio MCP
Typical workflow
Start by creating or switching to a profile. A profile is an isolated command namespace for a specific project, environment, or workflow.
afc profile create myproject "My project"
afc profile switch myprojectAdd a command with a readable alias:
afc add hello "echo hello" -d "Say hello"Run it:
afc -y helloThe -y flag confirms execution when the command would otherwise prompt.
Working with profiles
Profiles let you reuse the same alias in different contexts without collisions. For example, deploy can mean staging in one profile and production in another. That is useful when you want local command behavior to match the project you are currently working on.
Working with pipelines
Pipelines chain existing commands into an ordered execution flow. That is useful for repeatable routines such as build, test, deploy, cleanup, or environment preparation.
Common pipeline commands include:
afc pipeline create
afc pipeline list
afc pipeline show my-deploy
afc pipeline execute my-deployMCP tools
The local afc-commander-core server exposes these tools to MCP clients such as Cursor:
afc-list-commandsafc-search-commandsafc-execute-commandafc-add-commandafc-remove-commandafc-list-profilesafc-create-profileafc-switch-profileafc-list-pipelinesafc-create-pipelineafc-execute-pipeline
Data locations
By default, AFC Commander stores user data in:
~/.afc-commander
Other important locations:
~/.cursor/mcp.jsonfor MCP registration~/.afc-commander/install.jsonfor install metadata
You can move the user data directory by setting AFC_HOME before running setup.
Useful commands
Refresh MCP paths after moving the package or reinstalling:
node setup.cjs --mcp-onlyUninstall the package and MCP registration:
node uninstall.cjsRemove the user data directory as well:
node uninstall.cjs --purge-dataProject layout
afc-commander/— CLI package and command implementationserver.js— MCP stdio entrypointsetup.cjs— installation scriptuninstall.cjs— uninstall scriptdocs/— usage, architecture, and help content
Development notes
The repository includes docs for the command parser, registry structure, help topics, and usage patterns. Those docs are useful if you want to understand how aliases are parsed, how profiles isolate commands, and how pipelines are stored.
License
See license.md for the project license.
This server cannot be installed
Maintenance
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Trace186/AFC-Commander-CLI-Registry-With-MCP'
If you have feedback or need assistance with the MCP directory API, please join our Discord server