[docs] Community-maintained Tauri Documentation MCP #16019
fxckcode
started this conversation in
Show and tell
Replies: 2 comments
Update: package and registry publication completedThe initial implementation and release pipeline are now published:
The package provides a read-only, stdio MCP server for resolving and querying an immutable Tauri 2 documentation snapshot. It complements runtime/debugging MCP projects and does not execute commands, write files, fetch arbitrary URLs, or control a running Tauri app. |
0 replies
That would be https://github.com/tauri-apps/awesome-tauri |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Community-maintained Tauri Documentation MCP
I built and published a community-maintained MCP server focused on retrieving official Tauri 2 documentation for AI coding agents:
https://github.com/fxckcode/tauri-docs-mcp
Initial release:
https://github.com/fxckcode/tauri-docs-mcp/releases/tag/v0.1.0
The first functional slice provides a read-only stdio MCP server with one bounded tool,
search_tauri_docs. It searches a checked-in Tauri 2 documentation corpus and returns deterministic results with canonical source URLs, context, and version-sensitive metadata. It includes strict input validation, structured errors, TypeScript linting, typechecking, unit tests, and a real stdio integration smoke test.This intentionally complements rather than replaces the existing runtime/debugging MCP projects. It does not execute commands, fetch user-controlled URLs, write files, control a running Tauri app, or claim to be an official Tauri project.
The project was developed through a staged Builder -> independent Verifier -> functional QA workflow. The current scope is deliberately conservative: the corpus is checked in, while live crawling, embeddings, automatic version ingestion, project detection, and runtime debugging remain future work.
Would the Tauri maintainers consider listing this in a community resources or ecosystem section, if one exists or is planned? I would also welcome feedback on documentation terminology, source coverage, versioning expectations, or integration points that would make this more useful and accurate for Tauri users.
All reactions