MCP server for working with AWS Blog and News articles

Created By
mirecekd10 months ago
This MCP server provides tools for retrieving and filtering AWS blog articles and news from all AWS categories. The server is built using the FastMCP framework and supports SSE transport on port 8807.
Overview

What is AWS Blogs MCP?

AWS Blogs MCP is a server designed to retrieve and filter AWS blog articles and news from various AWS categories, built using the FastMCP framework.

How to use AWS Blogs MCP?

To use the server, you can run it via Docker or locally, and then access its API endpoints to retrieve articles based on different parameters such as date, category, or search queries.

Key features of AWS Blogs MCP?

  • Supports SSE transport on port 8807
  • Filters articles by type (News/Blog) and category
  • Date filtering options (specific date range or days back)
  • Text search functionality
  • Caching mechanism for improved performance
  • Structured API responses

Use cases of AWS Blogs MCP?

  1. Fetching the latest AWS articles for developers.
  2. Integrating with automation tools like N8N for processing AWS news.
  3. Filtering articles by specific categories for targeted information.

FAQ from AWS Blogs MCP?

  • Can I run AWS Blogs MCP locally?

Yes! You can run it locally by installing dependencies and executing the server script.

  • What types of articles can I retrieve?

You can retrieve both News and Blog articles from AWS.

  • Is there a limit on the number of articles I can fetch?

Yes, each API endpoint has a default limit on the number of articles returned, which can be adjusted.

Project Info
Created At
10 months ago
Updated At
10 months ago
Author Name
mirecekd
Star
-
Language
-
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
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.

35 minutes ago