Skip to content
Raghvendra Pratap Singh.

About

I’m Raghvendra Pratap Singh. I build web applications, Windows desktop software and tools that connect AI assistants to everyday workflows. Alongside software, I study medicine.

My work spans the interface and the systems behind it: React and Next.js applications, TypeScript APIs, desktop workflows with Electron, and MCP servers. Projects include a local file converter, a booking application, and tools for working with notes and diagrams.

I created and maintain Obsidian MCP Pro. It’s an open-source project: I coordinate changes with contributors, review pull requests, discuss implementation tradeoffs and test changes before merging. I also implement features and work through the details of safe access to a user’s notes. I care about clear interfaces, useful error messages and software that recovers when something goes wrong.

I’m interested in software engineering opportunities and client projects across web, desktop and developer tools. Explore my work for the implementation decisions, contributions and current state of each project.

Working together

Have a website or a repetitive software task in mind? These are starting points for a conversation about a clearly defined piece of work. The examples below show related work and its current limits.

Websites and client tools

A website that explains your work, an enquiry form, or a place for clients to sign in. A possible starting point is a set of pages or one account journey, with the content and connections agreed in advance.

Describe who the site is for, what they should be able to do, and what you already have.

Discuss a website or client tool

Related work: Riverstone & Willow

A coaching website and client portal with booking, account and payment workflows.

What this shows and where it stops. This case study describes implementation work. Live booking, payments and notifications are not demonstrated here. No client records, private source code or real transaction details are exposed.

Explore Riverstone & Willow

The case study includes engineering decisions, contributions and evidence.

Tools for repeated Windows work

A focused tool for a task you repeat on your computer, such as processing a batch of files. The starting scope could cover one workflow, with visible progress and a way to handle failures.

Describe the repeated task and the file types involved. Keep any examples free of personal or confidential information.

Discuss a Windows workflow

Related work: File Converter

Batch file conversion on your computer, with clear progress and a way to recover when a file fails.

What this shows and where it stops. The browser converter is a separate PNG/JPEG demonstration, not the desktop application shown in the captures. Those captures show a local development build. Conversion fidelity depends on the format and engine; this is not a claim that every format is lossless or that an installer has been verified.

Explore File Converter

The case study includes engineering decisions, contributions and evidence.

Connecting notes and tools

Help an AI assistant find or work with information in a tool you already use. A possible first step is one search or editing action, with access permissions and the data it can use agreed before development.

Name the tools you use and one action you want to make easier. There is no need to send private notes or account credentials.

Discuss a connection between tools

Related work: Obsidian MCP Pro

Connect an AI assistant to an Obsidian vault through structured tools for notes, search, links and attachments.

What this shows and where it stops. The recorded runs use the actual local server. The interactive sample vault is a separate, limited browser simulation with fictional notes, not a live MCP connection. No real vault or account credentials are collected. AI-provider privacy depends on the client and provider a user chooses.

Explore Obsidian MCP Pro

The case study includes engineering decisions, contributions and evidence.

A proposed way to work

  1. Understand the need

    Describe the problem, who will use the software and what you have already tried.

  2. Agree the scope

    Define the work, its limits and how to check it, along with any access or services it needs.

  3. Review progress

    Look at working examples together and discuss changes before expanding the scope.

  4. Hand over

    Walk through the result and the agreed setup instructions, known limits and ongoing responsibilities.

Let’s talk.

Have a project in mind or a role to discuss? A few lines are enough to get started.

Time zone

Central European time: CET (UTC+1) in winter and CEST (UTC+2) in summer.

The contact form is temporarily unavailable. Please email me directly for projects, opportunities or product enquiries.

Email Raghvendra

Opens your email app. Please leave out credentials and confidential information.