Get the FREE Ultimate OpenClaw Setup Guide →

docs

Documentation for the Strands Agents SDK. A model-driven approach to building AI agents in just a few lines of code.

Installation
Run this command in your terminal to add the MCP server to Claude Code.
Run in terminal:
Command
claude mcp add --transport stdio strands-agents-docs npx -y strands-agents/docs

How to use

This MCP server serves the Strands Agents documentation site. It is a static site built with Astro and delivered via a Node-based toolchain. The repository’s docs are authored in Markdown and rendered into a navigable site through the build process. The server exposes development and build commands that let you preview changes locally and generate a production-ready static site for deployment.

To use the server you’ll rely on the standard Node.js tooling: npm install to pull dependencies, npm run build to generate the static site, and npm run dev to spin up a local development server for previewing the site at http://localhost:4321/. The docs editor workflow relies on common Markdown edits in the docs/ directory, with build-time integration managed by MkDocs/Astro tooling configured in mkdocs.yml and the project’s Astro setup.

How to install

Prerequisites

  • Node.js 20+ (npm comes bundled with Node.js)
  • Git (optional, for cloning the repository)

Installation steps

  1. Clone the repository (or download the ZIP): git clone https://github.com/strands-agents/docs.git cd docs

  2. Install dependencies: npm install

  3. Build the static site for production: npm run build

  4. Run a local development server to preview the site: npm run dev

    The site will be available at http://localhost:4321/

Notes

  • The documentation site is powered by Astro with the Starlight theme and uses Markdown content located in docs/.
  • For content edits, you can modify Markdown files directly; the build process will render them into the static site during the build step.

Additional notes

Tips and common issues:

  • Ensure Node.js version matches the prerequisites (Node.js 20+).
  • If npm install stalls, try clearing the npm cache or using a clean environment.
  • The dev server defaults to port 4321; if you need a different port, modify the start script or environment variables as appropriate for your deployment.
  • When wiring into MCP tooling, the server exposes a single entry point for the docs site, with assets generated under the build/output directory.
  • If building with a CI/CD pipeline, run npm ci for clean installs and cache management to speed up builds.

Related MCP Servers

Sponsor this space

Reach thousands of developers