Alex_Plug_In

Alex Plug-In includes an MCP cognitive tools server embedded with the Agent Plugin ecosystem. This MCP server enables autonomous tool use, memory management, and cross-session reasoning for Alex within the VS Code extension environment. Once the server is running, you can leverage Alex’s capabilities to perform multi-step tasks, manage long-running workflows, and coordinate between different skills and agents. The server exposes MCP endpoints exposed via the plugin integration, allowing commands to be issued for memory updates, tool invocations, and intent-driven workflows. Typical interactions involve initializing Alex, starting conversational sessions, and then invoking slash commands or 29+ tools that Alex can orchestrate through the MCP server.

Prerequisites:

• Node.js (recommended LTS version) installed on your development machine
• npm or yarn package manager
• VS Code installed (for the Agent Plugin workflow)

1. Install Node.js if you don’t have it:

   • macOS/Linux: https://nodejs.org/
   • Windows: https://nodejs.org/

2. Clone or download the Alex Plug-In repository from GitHub and navigate to the project root.

3. Install dependencies (run in project root):

   • npm install or
   • yarn install

4. Build or prepare the MCP server component as defined by the project’s build/scripts. If a build script exists, run:

   • npm run build

5. Start the MCP server (example):

   • node path/to/server.js

6. In VS Code, install the Alex Cognitive Architecture extension from the Marketplace and follow the Quick Start instructions to initialize Alex and connect to the MCP server.

Note: If the project ships with a packaged server within the Agent Plugin, the plugin may automate the server startup. In that case, ensure the plugin has permissions to launch the Node process and access required directories for memory and configuration.

Tips and notes:

• Environment variables:
  • ALEX_MCP_LOG_LEVEL controls verbosity (debug, info, warn, error).
  • ALEX_MCP_MEMORY_DIR should point to a writable directory for episodic memory storage.
  • ALEX_MCP_CONFIG_PATH can be used to point to a JSON config file with server settings.
• If you encounter startup issues, check the log level and ensure Node.js has access to the configured memory directory and config path.
• Ensure that the Agent Plugin and MCP server share compatible tool definitions and memory schemas to avoid schema mismatches.
• Restart the MCP server after changing configuration or memory paths to load new settings.
• When deploying across environments, consider using environment-specific config files and hardening security on access to memory and config directories.