<feed xmlns="http://www.w3.org/2005/Atom"> <id>https://gauravnavgire.github.io/</id><title>Gaurav Navgire</title><subtitle>Personal site and blog of Gaurav Navgire.</subtitle> <updated>2026-10-21T15:53:43+05:30</updated> <author> <name>Gaurav Navgire</name> <uri>https://gauravnavgire.github.io/</uri> </author><link rel="self" type="application/atom+xml" href="https://gauravnavgire.github.io/feed.xml"/><link rel="alternate" type="text/html" hreflang="en" href="https://gauravnavgire.github.io/"/> <generator uri="https://jekyllrb.com/" version="4.4.1">Jekyll</generator> <rights> © 2026 Gaurav Navgire </rights> <icon>/assets/img/favicons/favicon.ico</icon> <logo>/assets/img/favicons/favicon-96x96.png</logo> <entry><title>Timelines That Don't Invent Dates</title><link href="https://gauravnavgire.github.io/posts/timelines-that-dont-invent-dates/" rel="alternate" type="text/html" title="Timelines That Don&amp;apos;t Invent Dates" /><published>2026-10-21T12:00:00+05:30</published> <updated>2026-10-21T12:00:00+05:30</updated> <id>https://gauravnavgire.github.io/posts/timelines-that-dont-invent-dates/</id> <content type="text/html" src="https://gauravnavgire.github.io/posts/timelines-that-dont-invent-dates/" /> <author> <name>Gaurav Navgire</name> </author> <category term="AI" /> <category term="Projects" /> <summary>Ask a chatbot to put a document’s events in order and you’ll get a neat, confident timeline. Look closer and three things usually go wrong: Fake precision. A date known only as “July 1969” becomes 16 July 1969. Silent choices. Three sources give three times for the same meeting; the timeline shows one of them and doesn’t mention the other two. Calendar blindness. Shakespeare and Cervant...</summary> </entry> <entry><title>Updating Your MCP Server for the 2026-07-28 Spec</title><link href="https://gauravnavgire.github.io/posts/mcp-server-on-the-2026-07-28-spec/" rel="alternate" type="text/html" title="Updating Your MCP Server for the 2026-07-28 Spec" /><published>2026-07-29T16:00:00+05:30</published> <updated>2026-07-29T16:00:00+05:30</updated> <id>https://gauravnavgire.github.io/posts/mcp-server-on-the-2026-07-28-spec/</id> <content type="text/html" src="https://gauravnavgire.github.io/posts/mcp-server-on-the-2026-07-28-spec/" /> <author> <name>Gaurav Navgire</name> </author> <category term="AI" /> <category term="Tutorials" /> <summary>Barely a day after MCP’s first anniversary, the protocol shipped its most significant revision yet: the 2026-07-28 specification. It’s a bigger jump than a routine version bump, so before we touch code, here’s what actually changed. What’s new in 2026-07-28 Stateless protocol core. MCP moves from a stateful, bidirectional session to a request/response model. Every request now carries its o...</summary> </entry> <entry><title>Your First MCP Server in Python</title><link href="https://gauravnavgire.github.io/posts/your-first-mcp-server-in-python/" rel="alternate" type="text/html" title="Your First MCP Server in Python" /><published>2026-07-29T10:30:00+05:30</published> <updated>2026-07-29T10:30:00+05:30</updated> <id>https://gauravnavgire.github.io/posts/your-first-mcp-server-in-python/</id> <content type="text/html" src="https://gauravnavgire.github.io/posts/your-first-mcp-server-in-python/" /> <author> <name>Gaurav Navgire</name> </author> <category term="AI" /> <category term="Tutorials" /> <summary>A year ago, the Model Context Protocol (MCP) started as “a little open-source experiment” from Anthropic. Twelve months later it has become the de facto way to connect large language models to real data and tools — over 2,000 servers exist, with adoption spanning GitHub, Stripe, Notion, Microsoft, Google, AWS, and more. To celebrate the anniversary, let’s build the smallest useful thing you ca...</summary> </entry> </feed>
