by ttommyth
Interactive Terminal enhances AI interactions with user input, notifications, and cross-platform support for complex tas
Enables AI assistants to ask users questions via pop-up prompts and send notifications, allowing for clarification and confirmation during complex tasks.
Interactive Terminal is a community-built MCP server published by ttommyth that provides AI assistants with tools and capabilities via the Model Context Protocol. Interactive Terminal enhances AI interactions with user input, notifications, and cross-platform support for complex tas It is categorized under productivity, developer tools. This server exposes 5 tools that AI clients can invoke during conversations and coding sessions.
You can install Interactive Terminal in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
MIT
Interactive Terminal is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Share your MCP server with the developer community
Interactive Terminal is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
According to our notes, Interactive Terminal benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
Useful MCP listing: Interactive Terminal is the kind of server we cite when onboarding engineers to host + tool permissions.
We evaluated Interactive Terminal against two servers with overlapping tools; this profile had the clearer scope statement.
I recommend Interactive Terminal for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
We evaluated Interactive Terminal against two servers with overlapping tools; this profile had the clearer scope statement.
I recommend Interactive Terminal for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
Interactive Terminal is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
Useful MCP listing: Interactive Terminal is the kind of server we cite when onboarding engineers to host + tool permissions.
Interactive Terminal has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
showing 1-10 of 30
A MCP Server implemented in Node.js/TypeScript, facilitating interactive communication between LLMs and users. Note: This server is designed to run locally alongside the MCP client (e.g., Claude Desktop, VS Code), as it needs direct access to the user's operating system to display notifications and command-line prompts.
(Note: This project is in its early stages.)
Want a quick overview? Check out the introductory blog post: Stop Your AI Assistant From Guessing — Introducing interactive-mcp
<div align="center"> <a href="https://glama.ai/mcp/servers/@ttommyth/interactive-mcp"> <img width="380" height="200" src="https://glama.ai/mcp/servers/@ttommyth/interactive-mcp/badge" alt="interactive-mcp MCP server" /> </a> </div>This server exposes the following tools via the Model Context Protocol (MCP):
request_user_input: Asks the user a question and returns their answer. Can display predefined options.message_complete_notification: Sends a simple OS notification.start_intensive_chat: Initiates a persistent command-line chat session.ask_intensive_chat: Asks a question within an active intensive chat session.stop_intensive_chat: Closes an active intensive chat session.Here are demonstrations of the interactive features:
| Normal Question | Completion Notification |
|---|---|
 |  |
| Intensive Chat Start | Intensive Chat End |
|---|---|
 |  |
This server is ideal for scenarios where an LLM needs to interact directly with the user on their local machine, such as:
This section explains how to configure MCP clients to use the interactive-mcp server.
By default, user prompts will time out after 30 seconds. You can customize server options like timeout or disabled tools by adding command-line flags directly to the args array when configuring your client.
Please make sure you have the npx command available.
Add the following minimal configuration to your claude_desktop_config.json (Claude Desktop) or mcp.json (Cursor):
{
"mcpServers": {
"interactive": {
"command": "npx",
"args": ["-y", "interactive-mcp"]
}
}
}
With specific version
{
"mcpServers": {
"interactive": {
"command": "npx",
"args": ["-y", "[email protected]"]
}
}
}
Example with Custom Timeout (30s):
{
"mcpServers": {
"interactive": {
"command": "npx",
"args": ["-y", "interactive-mcp", "-t", "30"]
}
}
}
Add the following minimal configuration to your User Settings (JSON) file or .vscode/mcp.json:
{
"mcp": {
"servers": {
"interactive-mcp": {
"command": "npx",
"args": ["-y", "interactive-mcp"]
}
}
}
}
For a smoother experience on macOS using the default Terminal.app, consider this profile setting:
This section is primarily for developers looking to modify or contribute to the server. If you just want to use the server with an MCP client, see the "Client Configuration" section above.
package.json for version compatibility.npm install -g pnpm after installing Node.js.Clone the repository:
git clone https://github.com/ttommyth/interactive-mcp.git
cd interactive-mcp
Install dependencies:
pnpm install
pnpm start
The interactive-mcp server accepts the following command-line options. These should typically be configured in your MCP client's JSON settings by adding them directly to the args array (see "Client Configuration" examples).
| Option | Alias | Description |
|---|---|---|
--timeout | -t | Sets the default timeout (in seconds) for user input prompts. Defaults to 30 seconds. |
--disable-tools | -d | Disables specific tools or groups (comma-separated list). Prevents the server from advertising or registering them. Options: request_user_input, message_complete_notification, intensive_chat. |
Example: Setting multiple options in the client config args array:
// Example combining options in client config's "args":
"args": [
"-y", "interactive-mcp",
"-t", "30", // Set timeout to 30 seconds
"--disable-tools", "message_complete_notification,intensive_chat" // Disable notifications and intensive chat
]
pnpm buildpnpm lintpnpm formatWhen interacting with this MCP server (e.g., as an LLM client), please adhere to the following principles to ensure clarity and reduce unexpected changes:
request_user_input, start_intensive_chat, etc.) frequently to engage with the user.You can provide these instructions to an LLM client like this:
# Interaction
- Please use the interactive MCP tools
- Please provide options to interactive MCP if possible
# Reduce Unexpected Changes
- Do not make assumption.
- Ask more questions before executing, until you think the requirement is clear enough.
Contributions are welcome! Please follow standard development practices. (Further details can be added later).
MIT (See LICENSE file for details - if applicable, or specify license directly).
Prerequisites
Time Estimate
15-60 minutes depending on server complexity
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
Compatibility
✓ Use when
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid when
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.