MCP servers · cloudcorprecords

cloudsession: local AWS session and plan state as MCP tools

An MCP server that keeps local AWS session context and ordered execution plans in memory, without calling any AWS API.

This text was machine-translated from the publisher's own information and has not been checked by a human editor. The publisher's original text is the reference.

This resource was imported automatically from the sources listed below and has not been reviewed by the AI Gate team yet. The description is the publisher's own, as published. Check the repository before installing.

What it does

cloudsession provides nine MCP tools for local AWS session and plan state: start_session, get_session_info, end_session, set_region, set_profile, list_regions, create_plan, advance_plan_step and get_plan. It is a clean-room rebuild of the session and plan core of the AWS core MCP server. No tool calls an AWS API. A session holds a profile name and a region, defaulting to profile default and region us-east-1, with deterministic IDs such as session-1. Regions are validated against a static list of 29 regions.

It suits workflows that need to track which profile and region are in use, or to step through an ordered plan where the caller advances each step explicitly. Ending a session blocks further changes while keeping it readable. Plans mark each step as pending or completed; advancing the final step completes the plan, and advancing a completed plan returns an error.

No credentials or environment variables are required. Session and plan state is held in memory for the life of the server process. Each CLI invocation starts with a fresh store, so multi-step flows are meant to run through the MCP server. Credential and SSO login flows, AWS API proxy tools, documentation search and prompt templates are not included.

Limitations and requirements

State is held in memory and nothing persists across server restarts. Each CLI invocation starts with a fresh store, so multi-step flows must use the MCP server. No tool calls live AWS service APIs, and credential and SSO login flows are not included.

Safety

Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.

  • Runs code or changes an assistant's behaviour

Sources

  • Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
    io.github.CloudCorpRecords/cloudsession

    Local AWS session and execution-plan state as MCP tools.

    v0.1.0
    As shown on registry.modelcontextprotocol.io when we last read it
MCP servers
modelcontextprotocol

MCP reference servers

Seven small example servers maintained by the Model Context Protocol project: files, Git, web fetching, memory, time, step-by-step thinking and a test server.

92K GitHub starsSoftware development
Updated 18 Nov 2026
MCP servers
firecrawl

Firecrawl MCP Server (web search and scraping)

Firecrawl's MCP server that lets an AI assistant search the web, turn pages and PDFs into clean Markdown, crawl sites and interact with dynamic pages.

7.8K GitHub starsWeb, search & browserProductivity & automation
Updated 17 Nov 2026
MCP servers
hashicorp

Terraform MCP Server (HashiCorp)

HashiCorp's MCP server that gives an assistant current Terraform Registry information on providers, modules and policies, and can manage HCP Terraform workspaces.

1.6K GitHub starsCloud & DevOpsSoftware development
Updated 17 Nov 2026
MCP servers
docker

Docker Hub MCP Server

Docker's MCP server that helps an AI assistant find and compare container images on Docker Hub and, with your token, manage your own repositories and tags.

171 GitHub starsCloud & DevOpsSoftware development
Updated 13 Nov 2026