Amazon Q Developer CLI

Created By
BrianSuarezSantiagoa year ago
AWS MCP Server Configurations for different operating systems
Overview

What is Amazon Q Developer CLI?

Amazon Q Developer CLI is a command-line interface tool designed for configuring AWS MCP (Managed Cloud Platform) servers across different operating systems.

How to use Amazon Q Developer CLI?

To use the Amazon Q Developer CLI, follow these steps: 1. Install the CLI from the official documentation. 2. Configure the CLI by creating a global or workspace-specific configuration file. 3. Use the CLI commands to manage your AWS MCP servers.

Key features of Amazon Q Developer CLI?

  • Easy installation and configuration for AWS MCP servers.
  • Support for multiple operating systems.
  • Command-line tools for managing AWS resources efficiently.

Use cases of Amazon Q Developer CLI?

  1. Configuring AWS MCP servers for different environments.
  2. Managing AWS resources through command-line operations.
  3. Automating server configurations and deployments.

FAQ from Amazon Q Developer CLI?

  • Is Amazon Q Developer CLI free to use?

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

  • What operating systems are supported?

The CLI supports various operating systems, but specific configurations may vary.

  • How do I report issues or contribute?

You can report issues or contribute to the project on its GitHub repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
BrianSuarezSantiago
Star
0
Language
-
License
MIT license
Tags

Recommend Servers

View All
Voyei

2 hours ago
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