---
title: "Talk to Your Database from Excel via Claude & MCP - Part 2"
slug: talk-to-your-database-from-excel-mcp-part-2
date_published: 2026-02-28T10:00:00.000Z
original_url: https://www.tigzig.com/post/talk-to-your-database-from-excel-mcp-part-2
source: fresh
processed_at: 2026-02-28T10:00:00.000Z
---

# Talk to Your Database from Excel via Claude & MCP - Part 2

![Claude Excel MCP Database Part 2](/images/blog/claudeExcelMCP_DB_part2.png)

Two new things.

1. 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.

2. 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](https://tigzig.com/security-checklist)

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](https://www.tigzig.com/post/talk-to-your-database-from-excel-postgres-duckdb-claude-mcp)