Forem: Abhinav Singh

DevStash: AI-Powered Developer Knowledge Management with Algolia MCP

Abhinav Singh — Sun, 27 Jul 2025 10:58:56 +0000

This is a submission for the Algolia MCP Server Challenge

What I Built

I built DevStash, a comprehensive developer knowledge management ecosystem that transforms how developers save, organize, and retrieve code snippets, commands, queries, and notes, etc. Unlike traditional snippet managers, DevStash leverages AI to intelligently analyze and enrich content before storing it in Algolia, creating a truly smart search experience.

Core Features:

VS Code Extension: Seamless snippet saving with command Devstash: Save or Ctrl+Alt+S and searching with command Devstash: Search or Ctrl+Alt+D directly in your editor
AI-Powered Analysis: Automatic content categorization, language detection, smart tagging, and title generation
Intelligent Search: Algolia-powered search with rich metadata and context-aware results
Self-Hostable: Complete deployment blueprints for Render.com
Extensible Architecture: Built with n8n workflows and MCP server for easy customization

The system consists of:

VS Code Extension (frontend interface)
n8n Workflow (AI-powered backend processing)
Algolia (storage and search engine)
Algolia MCP Server (AI assistant integration)
OpenRouter AI Models (content analysis)

Demo

GitHub Repository:

bugcacher / devstash

A comprehensive developer knowledge management system that allows you to save, organize, and search code snippets, commands, queries, notes, etc

DevStash

A comprehensive developer knowledge management system that allows you to save, organize, and search code snippets, commands, queries, notes, etc.

System Architecture

The DevStash ecosystem consists of:

VS Code Extension: Frontend interface for saving, deleting, and searching snippets
n8n Workflow: AI-powered backend processing and data orchestration
Algolia: Combined storage and search engine
Algolia MCP Server: Model Context Protocol server for seamless AI assistant integration with your Algolia indexes
AI Models: Intelligent content analysis and metadata extraction via OpenRouter

Prerequisites

Before setting up DevStash, ensure you have:

n8n instance (self-hosted or cloud)
Algolia account
OpenRouter API account (for AI processing)
VS Code

Installation Guide

Step 1: Set up Algolia

Create an Algolia account
Create a new application
Create an index (e.g., stashes)
Get your credentials:
- Application ID
- Search-Only API Key
- Admin API Key (for n8n workflow)

Step 2: Set up OpenRouter or any other

…

View on GitHub

Demo Link:

How I Utilized the Algolia MCP Server

The Algolia MCP Server is the backbone of DevStash's AI integration, enabling seamless communication between AI models and Algolia search infrastructure.

Data Storage & Indexing: The n8n workflow uses the Algolia MCP Server to create and maintain a searchable index of all saved content - from code snippets and commands to configuration files and notes. Each entry combines user-provided content with AI-enhanced metadata, creating rich, searchable documents.
Auto Index Management The MCP server enables AI models to Create indexes automatically when they don't exist, ensuring seamless setup.

Why MCP Server Over Direct API?

AI-Native: Designed specifically for AI model interactions
Simplified Integration: No need to handle Algolia API complexities in n8n
Standardized Protocol: MCP provides consistent interface across different AI models

Key Takeaways

Challenges Faced

Challenge 1: Getting Algolia MCP Server Deployed and Working - Initially struggled with getting the Algolia MCP server to properly authenticate and connect. Due to a bug in the MCP server, if no tools are explicitly provided in the configuration, the Algolia credentials are not read from environment variables, causing all calls to the MCP server to fail.

Solution: After reading through the MCP server code, I discovered the issue and fixed it by specifically mentioning the required tools in the configuration. This ensures proper credential loading and successful Algolia operations.

Challenge 2: Self-Hosting Complexity - Wanted to make the system accessible to developers without complex setup requirements.

Solution: Developed comprehensive Render.com blueprints and n8n templates for easy deployments.

What I Learned

MCP Server Integration: Discovered how the Algolia MCP Server simplifies AI-to-search workflows, eliminating API complexity while maintaining powerful indexing capabilities
Visual Workflow Development: Learned that n8n's visual approach makes AI-powered data processing surprisingly accessible compared to traditional backend coding
Privacy-First Architecture: Understood the value of self-hosting for developer tools - complete data control without sacrificing search performance
AI-Enhanced Search: Realized how AI-generated metadata transforms search from keyword matching to intent understanding, making forgotten content discoverable
VS Code Extension Capabilities: Explored how webviews can create rich, interactive experiences within the familiar editor environment

Impact

DevStash transforms scattered developer knowledge into a centralized, searchable repository that grows more valuable over time. It's particularly useful for developers working with complex systems, configurations, or codebases who need quick access to previously used patterns and solutions.

Use Pulumi ESC as Your OpenFeature Provider for Secrets and Configs

Abhinav Singh — Sun, 06 Apr 2025 16:02:50 +0000

This is a submission for the Pulumi Deploy and Document Challenge: Shhh, It's a Secret!

What I Built

I built an OpenFeature Provider for Pulumi ESC, written in Go. This provider lets developers securely fetch configuration and secret values from Pulumi ESC in a type-safe, extensible, and standards-compliant way using the OpenFeature SDK. It can replace environment variables, remote config systems, and flag providers in modern applications — all while simplifying cloud secrets access from AWS, GCP, or Azure using OIDC.

Live Demo Link

Demo Link
Demo Application Source Code

Project Repo

bugcacher / open-feature-pulumi-esc-provider

Pulumi ESC Provider For Open Feature

OpenFeature Pulumi ESC Provider

An OpenFeature provider written in Go for securely accessing secrets and configuration values from Pulumi ESC. This provider allows your application to retrieve values like API keys, DB URLs, feature flags, and more — in a typed, structured, and cloud-agnostic way.

Using Pulumi ESC as the source of truth and OpenFeature as the standard interface, this tool simplifies environment configuration and makes it effortless to manage secrets across multiple cloud providers.

Features

Strongly-typed config access (string, bool, int, float)
Built-in support for default fallback values
Fetch secrets/configs from AWS, GCP, Azure or any other cloud vendor (via Pulumi ESC)
Minimal setup using Pulumi ESC with OIDC authentication
Fully compatible with the OpenFeature SDK in Go

Installation

go get github.com/bugcacher/open-feature-pulumi-esc-provider

Pulumi ESC Setup

You must configure a Pulumi ESC environment with the secrets and configuration values you want to expose. Here's…

View on GitHub

My Journey

When I came across the Pulumi ESC challenge, I realized there was a missing piece in the ecosystem: there was no OpenFeature provider for Pulumi ESC.

OpenFeature was originally built to manage feature flags, but its provider model and typed API make it a perfect fit for general configuration and secrets management too. That’s when it clicked — why not treat Pulumi ESC like a configuration backend for OpenFeature?

By building this provider, I extended OpenFeature into a broader use case:

Securely fetch configuration values and secrets
From multiple sources — including cloud secret managers (like AWS Secrets Manager and Parameter Store), static configs, or encrypted values in ESC
With typed access and support for fallbacks, defaults, and environments

One thing that made this approach especially powerful is Pulumi ESC's support for multiple cloud integrations. You can define AWS Secrets, GCP Secret Manager, Azure Key Vault — all in the same ESC environment. This means, by using just one OpenFeature provider, you get the benefits of multiple cloud-native OpenFeature providers — without writing any extra integration logic or using multiple SDKs.

This pattern works seamlessly across environments:

✅ Local development
✅ Cloud deployments
✅ Serverless apps
✅ Kubernetes or VM-based setups

For developers already using OpenFeature, this provider becomes a drop-in solution that replaces .env files and makes secret/config access unified, secure, and version-controlled — with zero cloud SDKs and full type safety.

Using Pulumi ESC

When building this provider, Pulumi ESC turned out to be an ideal backend for securely managing configs and secrets across environments.

I used Pulumi ESC's YAML-based configuration to define dynamic providers like aws-secrets and aws-parameter-store, alongside static configs and encrypted secrets. The declarative nature made it easy to describe how each value should be fetched — and from where — whether it was AWS, Pulumi-native, or elsewhere.

What made it even smoother was Pulumi AI (Copilot) — which I used extensively to learn and implement parts of the Pulumi ESC Go SDK. Some of the key prompts I used were:

"How to read an individual property from a Pulumi ESC environment using Go?"
"How to configure OIDC-based login to AWS in Pulumi ESC?"
"How to pull secrets dynamically from AWS Secrets Manager in Pulumi ESC?"

Each of these helped me shape the provider to dynamically resolve and return values without hardcoding any logic — everything flows through Pulumi ESC and its cloud-specific integrations.

The result?

🔒 Secrets never touch code
📦 Configs are version-controlled and environment-specific
🔁 And switching cloud backends or secret sources requires no change in application logic — just the ESC config

This strong separation of concern, powered by Pulumi ESC + OpenFeature, turns configuration and secret management into a first-class citizen of your delivery pipeline.

Thanks for reading! If you're using — or planning to use — Pulumi ESC for environment variable or secret management, do check out my OpenFeature Pulumi ESC Provider on GitHub. Contributions, feedback, and ⭐️s are welcome!