More and more people meet a developer through an agent rather than a browser tab. Someone asks Claude, ChatGPT or Perplexity who you are and what you have built, and the agent reads your site on their behalf. So I rebuilt this site to be read by agents as carefully as by people, and to give them the same answer the page gives.
1One source, five surfaces
Everything the site says lives in a few typed content files: a profile, the list of work, the paper and these notes. The HTML pages, the markdown versions, llms.txt, the structured data and the MCP tools are all generated from them, so an agent never reads a different story from the one on the page.
2MCP: ask the site directly
There is a read-only MCP server at /mcp, over Streamable HTTP. Add it to Claude Code with one command:
claude mcp add --transport http divyansh https://divyanshshukla.com/mcpIt has six tools: about, list_work, get_work, get_paper, search and contact. Each returns markdown, every input is validated, and every tool is marked read-only, so a client can call them without stopping to ask.
3WebMCP: the same tools inside the browser
Agents that run inside the browser can use the same tools on the page itself, registered through WebMCP, with nothing to install.
4Markdown and llms.txt
Append .md to any URL, or send Accept: text/markdown, and you get the page as clean markdown with a canonical link back to the HTML version. /llms.txt lists every page with a one-line description, and /llms-full.txt is the whole site in one file, which is often all an agent needs.
curl -H "Accept: text/markdown" https://divyanshshukla.com/5Structured data for search and answer engines
Every page carries schema.org JSON-LD that points to a single Person node, so search engines and answer engines resolve one entity for my name. Products are marked as software applications, the paper as a scholarly article with Google Scholar tags, and these notes as blog posts. robots.txt welcomes AI crawlers: being cited correctly is the point.
6The page shows its own grounding
Figure 1 on the home page is an agent that runs in your browser. Ask it something and it plans once, outlines the evidence on the page as it finds it, and answers, with no model call and no tokens spent. It is the idea from my paper, made small enough to run on a portfolio.
7Try it
- Connect the MCP server and ask your agent what I have shipped.
- Open llms.txt, or any page with
.mdon the end. - Switch on Agent view in the toolbar to outline every element an agent can act on.