mcp-trustedadvisor-server

Created By
tomtapiaa year ago
Use Trusted Advisor as a model context protocol.
Overview

what is mcp-trustedadvisor-server?

The mcp-trustedadvisor-server is a server application that utilizes Trusted Advisor as a model context protocol to enhance server management and decision-making processes.

how to use mcp-trustedadvisor-server?

To use the mcp-trustedadvisor-server, clone the repository from GitHub, install the necessary dependencies, and run the server using the provided commands in the documentation.

key features of mcp-trustedadvisor-server?

  • Integration with Trusted Advisor for improved context management.
  • Built with TypeScript for better type safety and maintainability.
  • Open-source under the MIT license, allowing for community contributions.

use cases of mcp-trustedadvisor-server?

  1. Enhancing server management by providing context-aware recommendations.
  2. Assisting developers in making informed decisions based on Trusted Advisor insights.
  3. Streamlining server operations through automated context protocols.

FAQ from mcp-trustedadvisor-server?

  • What is Trusted Advisor?

Trusted Advisor is a service that provides real-time guidance to help you provision your resources following AWS best practices.

  • Is mcp-trustedadvisor-server free to use?

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

  • What programming language is used?

The server is developed in TypeScript.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
tomtapia
Star
0
Language
TypeScript
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