Sample Model Context Protocol Demos

Created By
aws-samplesa year ago
Collection of examples of how to use Model Context Protocol with AWS.
Overview

What is Sample Model Context Protocol Demos?

Sample Model Context Protocol Demos is a collection of examples demonstrating how to use the Model Context Protocol with AWS services, particularly focusing on Amazon Bedrock.

How to use Sample Model Context Protocol Demos?

To use the demos, clone the repository from GitHub and follow the instructions provided in each module's README file to set up the environment and run the examples.

Key features of Sample Model Context Protocol Demos?

  • Provides practical examples of using Model Context Protocol with AWS.
  • Includes demos in multiple programming languages (TypeScript and Python).
  • Demonstrates both server-client interactions and local setups.

Use cases of Sample Model Context Protocol Demos?

  1. Building applications that utilize the Model Context Protocol for AI agents.
  2. Learning how to implement server-client architecture using Amazon Bedrock.
  3. Experimenting with different programming languages for AWS integrations.

FAQ from Sample Model Context Protocol Demos?

  • What programming languages are used in the demos?

The demos are provided in TypeScript and Python.

  • Is there a license for using these demos?

Yes, the library is licensed under the MIT-0 License.

  • Where can I find more information about security issues?

Please refer to the CONTRIBUTING document in the repository for security issue notifications.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
aws-samples
Star
43
Language
Python
License
MIT-0 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