Lassare is an MCP server that lets you remotely answer questions and approve actions that your AI coding agents ask for. Each supported agent (Claude Code, Copilot in VS Code, Cursor, and Gemini CLI) has its own MCP configuration folder, enabling a dedicated integration that forwards questions to Slack and returns answers or approvals back to the agent. The system provides two core tools: ask and approve. When the agent needs input, it issues an ask; you receive a Slack DM and respond from your phone. For risky actions, the approve tool provides Approve/Deny options in Slack. Hooks are included to intercept dangerous commands and route them to Slack, helping you stay in control while away from your desk. To use it, sign up, obtain an API key, choose your agent, and follow the setup instructions in the corresponding agent folder README. You can switch between inline and Slack modes with slash commands like /lassare-slack and /lassare-inline. Each agent folder contains its own prompts, hooks, and MCP-specific configuration to tailor behavior and permissions to that agent.

Prerequisites:

• Node.js installed on your machine (recommended for npx-based setup)
• Access to Slack workspace and bot token
• An Lassare portal API key (for provisioning and management)

Install steps:

1. Clone the repository: git clone https://github.com/lassare-hq/agent-configs.git cd agent-configs

2. Install global or local dependencies if needed (example using npm): npm install

3. Configure environment variables for each agent:

   • In the mcp.json or your environment, set SLACK_BOT_TOKEN=your-slack-bot-token CLAUDE_API_KEY=your-claude-api-key CO-PILOT_API_KEY=your-copilot-api-key CURSOR_API_KEY=your-cursor-api-key GEMINI_API_KEY=your-gemini-api-key PORTAL_API_KEY=optional-portals-api-key

4. Start the MCP servers for the agents you enabled. For example:

   Claude Code

   npx -y lassare-claude-code

   Copilot in VS Code

   npx -y lassare-copilot

   Cursor

   npx -y lassare-cursor

   Gemini CLI

   npx -y lassare-gemini

5. Ensure your MCP.json (or equivalent config) points to these servers and that your agent configurations reference Lassare as the MCP server. When you’re ready, connect your Slack workspace and verify that you can send/receive asks and approvals.

Tips and common issues:

• If a command like rm -rf or git push --force triggers the danger hooks, verify that your prompts and permissions are up-to-date to avoid unnecessary interruptions.
• The hooks and dangerous command list are customizable per agent; adjust permission-approve.sh to fit your security posture.
• If questions or approvals expire after 15 minutes, check your Slack notification delivery and ensure the MCP webhook URL is reachable from your environment.
• Use the two modes (Inline and Slack) to balance speed and safety depending on whether you are at your desk or away.
• Ensure the agent’s API keys and SLACK_BOT_TOKEN are not leaked in logs or version control.
• For troubleshooting, consult the agent folder READMEs (claude-code, copilot, cursor, gemini) for agent-specific prompts, hooks, and setup details.