Azure Terminal Copilot

Created By
madebygpsa year ago
A Python-based Azure CLI assistant that provides natural language processing capabilities for Azure commands, leveraging Azure MCP Server.
Overview

What is Azure Terminal Copilot?

Azure Terminal Copilot is a Python-based Azure CLI assistant that utilizes natural language processing to facilitate Azure command execution, leveraging the Azure MCP Server.

How to use Azure Terminal Copilot?

To use Azure Terminal Copilot, clone the repository, set up a virtual environment, install the necessary packages, and run the main Python script after configuring the environment variables.

Key features of Azure Terminal Copilot?

  • Natural language processing for Azure CLI commands
  • Integration with Azure MCP Server
  • Easy setup and installation process

Use cases of Azure Terminal Copilot?

  1. Executing Azure commands using natural language queries.
  2. Managing Azure resources more efficiently.
  3. Enhancing productivity for Azure developers and administrators.

FAQ from Azure Terminal Copilot?

  • What are the prerequisites for using Azure Terminal Copilot?

You need Python 3.11+, Azure CLI, Ollama, and Azure MCP server installed and configured.

  • Is Azure Terminal Copilot free to use?

Yes! It is open-source and available under the MIT License.

  • How do I troubleshoot issues with Azure Terminal Copilot?

Ensure that your Azure CLI is logged in, as Azure MCP uses that for authentication.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
madebygps
Star
2
Language
Python
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Crevio

2 days ago