Skip to content

Get Featured in the Docs

Built something useful for Strands Agents? Getting featured in our docs helps other developers discover your work and gives your package visibility across the community.

We feature reusable packages that extend Strands Agents capabilities:

  • Model Providers — integrations with LLM services (OpenAI-compatible endpoints, custom APIs, etc.)
  • Tools — packaged tools that solve common problems (API integrations, utilities, etc.)
  • Session Managers — custom session/memory implementations
  • Plugins — extend or modify agent behavior during lifecycle events
  • Integrations — protocol implementations, framework bridges, etc.

We’re not looking for example agents or one-off projects — the focus is on packages published to PyPI that others can pip install or npm install and use in their own agents. See Community Packages for guidance on creating and publishing your package.

  1. Create a PR to strands-agents/docs
  2. Add your doc file in the appropriate community/ subdirectory
  3. Include the required frontmatter so your page appears in the community catalog
  4. Update src/config/navigation.yml to include your new page in the nav

Place your documentation in the right spot:

TypeDirectoryExample
Model Providerscommunity/model-providers/cohere.mdx
Toolscommunity/tools/strands-deepgram.mdx
Session Managerscommunity/session-managers/agentcore-memory.mdx
Pluginscommunity/plugins/my-plugin.mdx
Integrationscommunity/integrations/ag-ui.mdx

Your Strands docs page should be a concise overview — not a copy of your GitHub README. Keep it focused on getting users started quickly. Save the deep dives, advanced configurations, and detailed API docs for your project’s own documentation.

Follow this structure (see existing docs for reference):

# Package Name
Brief intro explaining what your package does and why it's useful.
## Installation
pip install your-package
## Usage
Working code example showing basic usage with Strands Agent.
## Configuration
Environment variables, client options, or model parameters.
## Troubleshooting (optional)
Common issues and how to fix them.
## References
Links to your repo, PyPI, official docs, etc.

Every community page needs frontmatter with catalog fields so it appears in the community catalog. Without community: true, integrationType, description, and languages, your page won’t show up in the catalog tables.

Here’s the full frontmatter for a Tool (adapt integrationType for your package type — tool, model-provider, session-manager, plugin, or integration):

---
title: your-package-name
community: true
integrationType: tool
description: Short description of what the tool does
languages: Python
sidebar:
label: "display-name"
project:
pypi: https://pypi.org/project/your-package/
github: https://github.com/your-org/your-repo
maintainer: your-github-username
service:
name: Service Name
link: https://service-website.com/
---
FieldRequiredNotes
communityMust be true
integrationTypetool, model-provider, session-manager, plugin, or integration
descriptionShown in the catalog table
languagesPython, TypeScript, or omit for both
projectRecommendedPyPI/npm link, GitHub repo, maintainer
serviceOptionalExternal service metadata

Add your page to src/config/navigation.yml under the Community section:

- label: Community
items:
- label: Model Providers
items:
- label: Your Provider
link: community/model-providers/your-provider
- label: Tools
items:
- label: your-tool
link: community/tools/your-tool

Look at existing community pages for reference:

Open an issue at strands-agents/docs — we’re happy to help!