It’s been a productive period for building and shipping open-source software. Through 2024 and into 2025, I’ve focused on creating tools that solve specific developer problems—from better API documentation to bridging the gap between AI and codebases.

Here is a summary of the key projects I’ve released and maintained.

A quick theme across all of them

Even though these projects span different ecosystems (Go, Rust, Tauri, SvelteKit, Vite), they share a few consistent goals:

• Reduce context switching: keep docs, tooling, and workflows close to where you write code.
• Ground AI output in sources: when an assistant can reference live docs, you get fewer “confidently wrong” suggestions.
• Ship small, useful utilities: tools that solve one problem well tend to get adopted.

🤖 Bridging AI and Documentation with MCP

The Model Context Protocol (MCP) has revolutionized how we interact with AI in our editors. To support this ecosystem, I launched several MCP servers designed to give your AI assistants expert knowledge:

• shadcn-svelte-mcp: Bringing the power of shadcn-svelte docs directly to your editor. Featured on the MCP Market!
• tauri-docs: A server exposing Tauri documentation, ensuring your cross-platform apps are built with the correct APIs.
• rust-docs: Specialized access to Rust documentation from docs.rs to help prevent AI hallucinations in Rust code.
• go-docs: Providing real-time, expert Go programming assistance sourced from pkg.go.dev.

If you’ve ever asked an assistant for an API signature and gotten something that looked right (but didn’t compile), you already understand the value here: these servers give the model a way to retrieve the real documentation on demand.

🛠️ Svelte & Vite Ecosystem Tools

As a big fan of Svelte and Vite, I built tools to verify and improve the development workflow:

• sveltekit-api-gen: Automatically generate OpenAPI 3.0 specs from your SvelteKit endpoints using JSDoc annotations. Keep your docs in sync with your code effortlessly.
• vite-plugin-lingo: A visual editor for .po translation files, integrated directly into Vite. It simplifies internationalization and works great with libraries like wuchale.

These are the kinds of tools I wish I had on every project: the ones that quietly keep your docs and developer experience from drifting over time.

📱 User-Facing Applications

• Svelte-MiniApps: A collection of single-purpose tools built with Svelte 5. Updated for 2025, this project serves as both a set of useful utilities and a reference for modern Svelte development.

It’s also intentionally simple in how it ships: one repo and one lightweight site that contains the whole collection.

I like having a “playground repo” like this because it doubles as:

• a place to ship small tools that are actually useful, and
• a living reference for how I structure Svelte 5 code.

How to try these quickly

If you want to evaluate any of these in under 10 minutes:

1. Open the GitHub repo and skim the README for the quickstart / install section.
2. If it’s an MCP server, connect via an SSE endpoint (best for editors) or HTTP (good for scripts).
3. Ask one focused question (e.g. “show me the config option for X”), then one applied question (“now generate the code for my use case”).

What’s Next?

I’m continuing to maintain these projects and explore new ideas in the Svelte and AI space. Check out the repositories, give them a star if you find them useful, and feel free to contribute!

Happy Coding!

If you enjoyed this roundup, consider starring the repos and sharing the post.

If you’re building something similar, I’d love to hear what you want automated next—docs, scaffolding, migrations, or anything else that steals time from actually shipping.

title: “2024-2025 Project Showcase: Empowering Developers with Tools & Utilities”

description: “A look back at the projects built over the last year, featuring MCP servers, SvelteKit tools, and helpful utilities.”
tags: [“showcase”, “opensource”, “svelte”, “mcp”]
series: “Tooling Experiments: MCP, Svelte & Beyond”

2024-2025 Project Showcase: Empowering Developers with Tools & Utilities

It’s been a productive period for building and shipping open-source software. Through 2024 and into 2025, I’ve focused on creating tools that solve specific developer problems—from better API documentation to bridging the gap between AI and codebases.

Here is a summary of the key projects I’ve released and maintained.

A quick theme across all of them

Even though these projects span different ecosystems (Go, Rust, Tauri, SvelteKit, Vite), they share a few consistent goals:

• Reduce context switching: keep docs, tooling, and workflows close to where you write code.
• Ground AI output in sources: when an assistant can reference live docs, you get fewer “confidently wrong” suggestions.
• Ship small, useful utilities: tools that solve one problem well tend to get adopted.

🤖 Bridging AI and Documentation with MCP

The Model Context Protocol (MCP) has revolutionized how we interact with AI in our editors. To support this ecosystem, I launched several MCP servers designed to give your AI assistants expert knowledge:

• shadcn-svelte-mcp: Bringing the power of shadcn-svelte docs directly to your editor. Featured on the MCP Market!
• tauri-docs: A server exposing Tauri documentation, ensuring your cross-platform apps are built with the correct APIs.
• rust-docs: Specialized access to Rust documentation from docs.rs to help prevent AI hallucinations in Rust code.
• go-docs: Providing real-time, expert Go programming assistance sourced from pkg.go.dev.

If you’ve ever asked an assistant for an API signature and gotten something that looked right (but didn’t compile), you already understand the value here: these servers give the model a way to retrieve the real documentation on demand.

🛠️ Svelte & Vite Ecosystem Tools

As a big fan of Svelte and Vite, I built tools to verify and improve the development workflow:

• sveltekit-api-gen: Automatically generate OpenAPI 3.0 specs from your SvelteKit endpoints using JSDoc annotations. Keep your docs in sync with your code effortlessly.
• vite-plugin-lingo: A visual editor for .po translation files, integrated directly into Vite. It simplifies internationalization and works great with libraries like wuchale.

These are the kinds of tools I wish I had on every project: the ones that quietly keep your docs and developer experience from drifting over time.

📱 User-Facing Applications

• Svelte-MiniApps: A collection of single-purpose tools built with Svelte 5. Updated for 2025, this project serves as both a set of useful utilities and a reference for modern Svelte development.

It’s also intentionally simple in how it ships: one repo and one lightweight site that contains the whole collection.

I like having a “playground repo” like this because it doubles as:

• a place to ship small tools that are actually useful, and
• a living reference for how I structure Svelte 5 code.

How to try these quickly

If you want to evaluate any of these in under 10 minutes:

1. Open the GitHub repo and skim the README for the quickstart / install section.
2. If it’s an MCP server, connect via an SSE endpoint (best for editors) or HTTP (good for scripts).
3. Ask one focused question (e.g. “show me the config option for X”), then one applied question (“now generate the code for my use case”).

What’s Next?

I’m continuing to maintain these projects and explore new ideas in the Svelte and AI space. Check out the repositories, give them a star if you find them useful, and feel free to contribute!

Happy Coding!

If you enjoyed this roundup, consider starring the repos and sharing the post.

If you’re building something similar, I’d love to hear what you want automated next—docs, scaffolding, migrations, or anything else that steals time from actually shipping.