Last 12 weeks · 0 commits
2 of 6 standards met
An MCP server for docs is just a bad idea An LLMS.txt is all you need If you want to make something interactive for whatever reason then make a cli that can be called directly from a repo and provide a skill that explains how to use it. For eg, This is far less hassle and in most cases far more efficient than using mcp servers. It also gives the user a layer of control if they wish to tweak the skill for whatever reasons
Since the introduction of plugins in Claude Code, several MCP servers began being distributed as part of/exposed through Claude Code plugins for more convenient access to said MCP servers. Creating and distributing a Claude Code plugin marketplace would be a great quality-of-life enhancement for the Astro Docs MCP server, making it easier for Claude Code users to connect to it, similar to the convenient deep links already available for Cursor and Visual Studio Code. In addition to the above, I find that creating a plugin for Astro would be especially valuable as Claude Code plugins can also bundle LSP servers alongside MCP servers. As an example, the Svelte plugin does exactly this. It would make a lot of sense for Astro to do the same, combining the Astro Docs MCP server (in this repo) with the Astro language server () into one plugin. This would give Claude Code users: Access to the latest Astro docs via MCP Code intelligence for files via LSP The end result is that Claude Code users would be able to set up everything with two commands: This replaces the current manual setup of running , while providing more functionality. Additionally, plugin installations are tracked in the project’s under . This means a team can commit that file to their repo so that every contributor who opens the project in Claude Code automatically has the Astro Docs MCP server available; no per-user setup required. Files to add If this looks like a good idea, I can open a pull request.
Repository: withastro/docs-mcp. Description: Astro Docs MCP Server Stars: 63, Forks: 13. Primary language: HTML. Languages: HTML (61.6%), TypeScript (38.4%). Open PRs: 4, open issues: 4. Last activity: 8mo ago. Community health: 62%. Top contributors: ascorbic, trueberryless, ematipico, kenedyolisi.