askme-cli
Allows the MCP server to open a new Alacritty terminal window to display user confirmation prompts.
Allows the MCP server to open a new Hyper terminal window to display user confirmation prompts.
Allows the MCP server to open a new iTerm2 terminal window to display user confirmation prompts.
Allows the MCP server to open a new Warp terminal window to display user confirmation prompts.
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., "@askme-cliask user for confirmation before deploying"
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.
We'd love your help! If you try askme-cli on Windows or have compatibility fixes, PRs are very welcome👏.
ASKME-CLI
🤖 💬 ⚡ 🚀 ✨
An MCP (Model Context Protocol) server that provides user confirmation interface for AI assistants
Why
AI assistants often need user confirmation or next steps, but there's no simple way to get user input during MCP conversations.
This project provides a personal confirmation endpoint via terminal interface.
Related MCP server: MCP Terminal
How to start
You will need to configure your MCP client to use ASKME-CLI.
Deploy the configuration using the instructions below.
Quick Setup with npx
# View help and configuration examples
npx askme-cli help
# Run directly (when called by MCP client)
npx askme-cliConfigure MCP Client
Add to your MCP client configuration file:
Cursor (.cursor/mcp_servers.json)
{
"mcpServers": {
"askme-cli": {
"command": "npx",
"args": ["askme-cli"],
"env": {
"ASKME_CLI_TERMINAL": "warp"
}
}
}
}Other MCP Clients
{
"mcpServers": {
"askme-cli": {
"command": "npx",
"args": ["askme-cli"],
"env": {
"ASKME_CLI_TERMINAL": "iterm2"
}
}
}
}Local Development
# Clone and install
git clone <your-repo-url>
cd askme-cli
npm install
# Build and run
npm run build
npm run startHow to use
Once configured, the AI assistant can use the ask_me tool to collect user confirmation:
AI assistant calls
ask_metool with summary of completed workASKME-CLI opens a new terminal window with confirmation interface
User enters next plan or confirmation and submits
AI assistant receives user input to continue
Terminal Support
Configure via ASKME_CLI_TERMINAL environment variable:
Terminal | Value | Description |
Warp |
| Default, modern terminal app |
iTerm2 |
| Popular macOS terminal |
Terminal |
| macOS system terminal |
Kitty |
| Cross-platform terminal |
Alacritty |
| GPU-accelerated terminal |
Hyper |
| Web-based terminal |
API Reference
ask_me Tool
Collects user's next plan or confirmation.
Parameters:
what_we_did(string): Summary of work completed by AI
Returns:
User's input for next plan or confirmation
Supports text and image input
Usage Examples
AI Assistant Integration
To use ASKME-CLI effectively in your AI assistant, add these rules to your system prompt:
- Must call the askme-cli.ask_me tool before ending any user prompt every time.
- All prompts starting with /tk, don't modify code or files, and call the askme-cli.ask_me tool before ending.
- When you have questions, always call the askme-cli.ask_me tool before ending.
- If you have ideas for new features or changes, explain them clearly, analyze their feasibility, and ask if I want to proceed.Example Tool Call
{
"tool": "ask_me",
"parameters": {
"what_we_did": "I've completed setting up the database schema and created the user authentication endpoints. The API is now ready for testing."
}
}Tech Stack
TypeScript - Type-safe development
React + Ink - Terminal UI framework
MCP SDK - Model Context Protocol support
Node.js - Runtime environment
License
MIT
Available Tools
1 toolask_meC
Ask the user for their next plan or obtain the user's confirmation
| Name | Required | Description | Default |
|---|---|---|---|
| what_we_did | Yes | Format your response as follows: 1. Start with '**TL;DR**: [brief summary]' on the first line 2. Follow with bullet points for what we did. 3. Use bullet points starting with '•' for each action |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full burden. It mentions 'ask the user' implying interaction, but does not disclose behavioral traits like blocking, side effects, or permissions. Minimal behavioral disclosure.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single short sentence that conveys the core functionality efficiently. However, it could be slightly clearer by separating the two actions.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool has one parameter and no output schema, the description is too minimal. It lacks context about when this tool is appropriate and what the user interaction entails, leaving the agent underinformed.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with detailed formatting instructions for the single parameter. The tool description does not add extra meaning beyond what the schema provides, so baseline 3.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool asks the user for their next plan or obtains confirmation. It uses a specific verb-resource pair and distinguishes the tool's purpose, though the 'or' could imply two behaviors.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives, nor are there exclusions or context. The description simply states what it does without any usage context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
1 tool update
v1.0.0- First observed
ask_me
TDQS
Only one tool exists, so there is no possibility of confusion or overlap.
With a single tool, naming consistency is not applicable, and 'ask_me' is a clear verb phrase.
A single tool is borderline for the server's purpose; while it might be sufficient for a singular action, it feels thin.
The tool covers asking the user for plans or confirmation, but there are no additional tools for other interactions, making the surface minimal.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
MCP server for AI dialogue using various LLM models via AceDataCloud
An MCP server that integrates with Discord to provide AI-powered features.
MCP server for Wan AI video generation
MCP server for Gainium — manage trading bots, deals, and balances via AI assistants
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceAn MCP server that allows AI assistants like Claude to execute terminal commands on the user's computer and return the output, functioning like a terminal through AI.89-
- AlicenseCqualityCmaintenanceA server that enables AI assistants to execute terminal commands and retrieve outputs via the Model Context Protocol (MCP).327MIT
- AlicenseAqualityDmaintenanceAn MCP server implementing AI-user confirmation protocols, providing tools for LLMs to seek user confirmation when uncertain through yes/no questions, action confirmations, intent clarification, understanding verification, and satisfaction ratings.822MIT
- FlicenseNot gradedqualityDmaintenanceAn MCP server that gives AI assistants the ability to create, manage, and control terminal sessions through a safe, isolated tmux environment.1-
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- 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/rhyspenn/askme-cli'
If you have feedback or need assistance with the MCP directory API, please join our Discord server