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
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