Dev.to AI πŸ€– Ai πŸ‘ 0 πŸ“– 1 min read

I made my portfolio answer AI assistants directly (MCP + llms.txt). Here's the setup.

When someone asks ChatGPT or Claude "who is this developer?", the answer is stitched together from whatever plain text the model can read. Most portfolios are JavaScript-heavy pages that crawlers barely parse. I made min

When someone asks ChatGPT or Claude "who is this developer?", the answer is stitched together from whatever plain text the model can read. Most portfolios are JavaScript-heavy pages that crawlers barely parse. I made mine answer directly, and it took three files.

1. An llms.txt at the root

llms.txt is a Markdown map of your site for models. Mine declares who I am (full name and the shorter form everyone uses, one canonical photo URL, role, location), then lists my CV versions, projects and contact links. The trick: it's generated from the same data source as the site, so it can't drift out of date.

2. Explicit AI crawlers in robots.txt

A wildcard Allow: / technically covers AI bots, but I name them anyway β€” GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, PerplexityBot, Google-Extended. One group per bot, explicit allow. If a model can't read you, you don't exist to it.

3. A read-only MCP server

This is the part most people skip. My portfolio exposes a public Model Context Protocol endpoint with tools like get_profile, get_experience and get_cv. Any MCP-capable agent (Claude, ChatGPT, Cursor, VS Code) can query my experience and pull the right CV for a role, in English or Spanish. Stateless Streamable HTTP, no auth, rate-limited, CORS open β€” it's public data by design.

4. One identity everywhere

Same name forms declared in JSON-LD (alternateName), the same photo file referenced from the schema and llms.txt, the same bio shape across GitHub and the site. Whatever you leave ambiguous, the model fills in with whatever it finds β€” up to showing someone else's photo.

What I'd measure

The honest metric isn't traffic. It's asking ChatGPT, Claude and Gemini for a developer with your profile, once a month, and writing down whether they mention you, what source they cite, and whether the photo is actually yours. That's the whole dashboard.

Everything above is live at franprz.vercel.app β€” check /llms.txt, /robots.txt and /for-agents.

πŸ“° Read the original article on Dev.to AI

Originally published by Dev.to AI. Aggregated on AIWithGhost for educational purposes β€” full credit and traffic to the original publisher.