search_documentation
Search AWS documentation using the official AWS Documentation Search API.
limitsearch_phraserequired
io.github.CloudCorpRecordsPublished by GitHub account CloudCorpRecordsv0.1.0Updated Nov 3, 2026
Search, read, and get recommendations for AWS documentation pages.
Searches the public AWS documentation site, converts documentation pages to markdown-style text, and suggests related pages for an AI assistant.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Follow the launch instructions in the repository.
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.
Or run the container image:
The container defaults to the MCP server (see below). Pass CLI arguments to use it as a CLI instead.
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:
MCP client configuration:
MIT — see LICENSE.
Source: README.md at commit 8e0229a
Search AWS documentation using the official AWS Documentation Search API.
limitsearch_phraserequiredFetch an AWS documentation page and convert it to markdown format.
urlrequiredmax_lengthstart_indexGet content recommendations for an AWS documentation page.
urlrequired90% 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.
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
npx @reneturcios/clouddocs search "s3 bucket naming"docker run -i ghcr.io/cloudcorprecords/clouddocs# Search the documentation indexclouddocs search "s3 bucket naming rules"clouddocs search "lambda execution role" --limit 5 --json
# Read a page as markdown-style text, optionally one window of itclouddocs read https://docs.aws.amazon.com/AmazonS3/latest/userguide/bucketnamingrules.htmlclouddocs read https://docs.aws.amazon.com/AmazonS3/latest/userguide/bucketnamingrules.html --start-index 5000 --max-length 5000
# Related pages for a documentation pageclouddocs recommend https://docs.aws.amazon.com/AmazonS3/latest/userguide/bucketnamingrules.html
clouddocs --versionnpx -y @reneturcios/clouddocs mcp{ "mcpServers": { "clouddocs": { "command": "npx", "args": ["-y", "@reneturcios/clouddocs", "mcp"] } }}npm installnpm 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