io.github.CloudCorpRecords/clouddocs is an MCP server that search, read, and get recommendations for AWS documentation pages. Its tool list has not been published yet over stdio and sse, requires no API key, and scores 57/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients - only the file and path differ.
{
"mcpServers": {
"clouddocs": {
"args": [
"-y",
"@reneturcios/clouddocs",
"mcp"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Search, read, and get recommendations for AWS documentation pages.
Run this in your terminal to verify the server starts. Then let us know if it worked - your result helps other developers.
npx -y '@reneturcios/clouddocs' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories - click any category to see the underlying evidence.
No known CVEs.
Checked @reneturcios/clouddocs against OSV.dev.
Be the first to review
Have you used this server?
Share your experience - it helps other developers decide.
Sign in to write a review.
Others in cloud
Gives AI development tools Firebase-specific capabilities and expertise.
Cloud-powered AI platform with multi-agent swarms, sandboxes, and workflow automation
Draw cloud architecture diagrams with official AWS, Azure and GCP icons from a prompt or Terraform.
MCP Server for kubernetes management commands
MCP Security Weekly
Get CVE alerts and security updates for io.github.CloudCorpRecords/clouddocs and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
clouddocs is a reading room for AWS documentation. It searches the official AWS documentation index for a phrase, opens a documentation page and returns it as clean markdown-style text you can page through in slices, and suggests the related documentation pages a page points to. It works from the command line or as an MCP server for agents, and it needs no AWS account and no API key: everything it reads is the public documentation site.
Only AWS documentation addresses are accepted for reading and
recommendations — docs.aws.amazon.com, aws.amazon.com, and their
subdomains. Any other host is refused before a request is made.
npx @reneturcios/clouddocs search "s3 bucket naming"
Or run the container image:
docker run -i ghcr.io/cloudcorprecords/clouddocs
The container defaults to the MCP server (see below). Pass CLI arguments to use it as a CLI instead.
# Search the documentation index
clouddocs search "s3 bucket naming rules"
clouddocs search "lambda execution role" --limit 5 --json
# Read a page as markdown-style text, optionally one window of it
clouddocs read https://docs.aws.amazon.com/AmazonS3/latest/userguide/bucketnamingrules.html
clouddocs read https://docs.aws.amazon.com/AmazonS3/latest/userguide/bucketnamingrules.html --start-index 5000 --max-length 5000
# Related pages for a documentation page
clouddocs recommend https://docs.aws.amazon.com/AmazonS3/latest/userguide/bucketnamingrules.html
clouddocs --version
Exit codes: 0 on success, 1 when a search or fetch fails (the
error names the problem), 2 for usage errors.
One bin serves both faces. The mcp subcommand starts a stdio MCP
server:
npx -y @reneturcios/clouddocs mcp
MCP client configuration:
{
"mcpServers": {
"clouddocs": {
"command": "npx",
"args": ["-y", "@reneturcios/clouddocs", "mcp"]
}
}
}
| Tool | Input | What it returns |
|---|---|---|
search_documentation | search_phrase (string, required), limit (integer, optional) | Matching documentation pages: title, URL, and a short summary for each. Search runs against the official search endpoint at search.docs.aws.amazon.com. |
read_documentation | url (string, required), max_length (integer, optional), start_index (integer, optional) | The page converted to markdown-style text: headings, links, lists, and code blocks preserved, navigation and scripts removed. start_index and max_length select a window of the converted text so long pages can be read in slices. |
recommend | url (string, required) | Related AWS documentation pages for the given page: the documentation pages it links to, in order, de-duplicated. |
npm install
npm run build # tsc -> dist/
npm test # node test runner over test/*.test.ts, no network (fake fetch fixtures)
npm run dev # run the CLI from source via tsx
MIT — see LICENSE.