
Cloudsession
io.github.CloudCorpRecordsPublished by GitHub account CloudCorpRecordsv0.1.0Updated Nov 3, 2026
Local AWS session and execution-plan state as MCP tools.
Overview
Cloudsession's local MCP server; no sign-in required; STDIO.
No AI overview yet: these facts come from the registry entry and the server itself.
Installation
In SourceWeft
- Open Cloudsession in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
cloudsession
Local AWS session and plan state as MCP tools. cloudsession is a clean-room rebuild of the session/plan meta core of the AWS core MCP server, under a new name: real local state logic, fresh code, no copied branding. No tool in this subset calls an AWS API — a session is a local context carrying a profile name and a region, and a plan is an ordered list of steps advanced explicitly by the caller.
Tools (core subset, 9)
start_session, get_session_info, end_session, set_region,
set_profile, list_regions, create_plan, advance_plan_step,
get_plan.
Sessions start with profile default and region us-east-1 unless
overridden, get deterministic IDs (session-1, plan-1, ...), and
validate regions against a curated static region list (29 regions).
Ending a session blocks further mutation while keeping it readable.
Plans track each step as pending/completed; advancing the final step
completes the plan, and advancing a completed plan is an error. State
is in-memory for the life of the server process — nothing persists
across restarts.
Not in this subset: AWS API proxy/call tools, credential and SSO login flows, documentation search helpers, prompt templates, and any tool that calls live AWS service APIs.
Setup
No credentials or environment variables are required.
CLI
Each tool name is a subcommand taking one JSON object argument. Note that each CLI invocation starts with a fresh store, so multi-step session/plan flows belong in the MCP server, which keeps one store for its lifetime.
MCP client config
Docker
Development
License
MIT
Source: README.md at commit 13462ca
Tools
0Version history
1- v0.1.0LatestNov 3, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts