Talk to Your Database from Excel via Claude & MCP - Part 2
Published: February 28, 2026

Two new things.
Open public server - now upgraded. No API key, no login. Hardened with rate limits, concurrency caps, SQL validation etc. 23 defense layers total. Open for anyone to try - or pressure test. Have at it.
OAuth-secured server (Auth0) - this is how I typically share tools with clients. Restricted access, JWT validation. If you want access to test, reach out. Once OAuth is at backend, setting up role-based access control is straightforward from there. The IT world has been doing this for decades - nothing new here.
Full source code is open. Single Python file. Clone it, inspect it, deploy your own.
My standard MCP advice still stands - don't connect to unknown MCP servers blind. Use servers from reputed providers, or ones you deploy yourself.
If you'd like to implement, easiest way - paste this message to your AI Coder. It's AI-agent first site. It will fetch llms.txt and pull out everything you need.
Full security checklist for Web apps: tigzig.com/security
Part 1 - Talk to Your Database from Excel via MCP (with all links) https://www.tigzig.com/post/talk-to-your-database-from-excel-postgres-duckdb-claude-mcp