The two sources are the whole design. Remote tools answer from mastra.ai; local ones read the docs shipped inside the packages you installed, so the signature an agent quotes is the one your build will actually accept. When the type definition is not enough, getMastraExportDetails will return the implementation source alongside it.
A documentation server for the Mastra framework with two sources: the published docs at mastra.ai, and the documentation embedded in the @mastra/* packages in your own node_modules, which matches the version your code runs against.
- Documentation fetched from mastra.ai by path — guides and API reference — mastraDocs
- Migration guides navigated like a directory, with section listing and keyword search — mastraMigration
- The @mastra packages installed in a project, listed with the documentation they carry — listMastraPackages
- A package's whole API surface — classes, functions, types, constants — filterable — getMastraExports
- Complete reference for one export: TypeScript definitions, and the implementation source when you ask for it — getMastraExportDetails
- Topic guides read out of the installed package — agents, tools, workflows, memory, RAG — readMastraDocs
- Full-text search across the embedded documentation — searchMastraDocs
- An entry point that lays out which of the two sources to use for what — getMastraHelp
- An interactive course you can start, resume, jump into by lesson, advance and reset — startMastraCourse, getMastraCourseStatus, startMastraCourseLesson, nextMastraCourseStep, clearMastraCourseHistory
Published on npm as @mastra/mcp-docs-server, with a stdio entry point. The local-package tools all take projectPath, aimed at the project whose node_modules should be read; the remote tools need no project at all. Starting the course asks for an email address to register.
One command — npx -y @mastra/mcp-docs-server