This MCP server provides documentation about Strands Agents to your GenAI tools, so you can use your favorite AI coding assistant to vibe-code
If you already use Strands Agents, the strands agents mcp server is the piece that lets your assistant work with it directly. This MCP server provides documentation about Strands Agents to your GenAI tools, so you can use your favorite AI coding assistant to vibe-code Strands Agents.
The source code is now under strands-mcp/. All new development, issues, and pull requests should go there.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Section — Based Browsing**: Browse document structure via table of contents, then fetch only the section you need - more token-efficient than retrieving fullsearch_docs — Find relevant documentation with intelligent rankingfetch_doc — Browse a page's structure and preamble, then read individual sections@modelcontextprotocol/inspector on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Configuration is passed through the environment: FASTMCP_LOG_LEVEL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
The usage methods below require uv to be installed on your system. You can install it by following the official installation instructions.
Plenty of knowledge and memory servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Strands Agents's toolset — Section, search_docs, fetch_doc — is a fair guide to whether it matches your workflow. It is maintained by strands-agents; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Section | Based Browsing**: Browse document structure via table of contents, then fetch only the section you need - more token-efficient than retrieving full pages |
| search_docs | Find relevant documentation with intelligent ranking |
| fetch_doc | Browse a page's structure and preamble, then read individual sections |
{
"mcpServers": {
"strands-agents": {
"command": "uvx",
"args": ["strands-agents-mcp-server"],
"env": {
"FASTMCP_LOG_LEVEL": "INFO"
},
"disabled": false,
"autoApprove": ["search_docs", "fetch_doc"]
}
}
}Configuration as documented by the project. Restart the client after saving.
The usage methods below require uv to be installed on your system. You can install it by following the official installation instructions.
| Variable | Description | Required |
|---|---|---|
| FASTMCP_LOG_LEVEL | Configuration value read at startup. | Optional |
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.