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
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago