The fastest way to get up to speed on me: add this server to your agent, in Claude, Cursor or any MCP client. Your agent gets direct access to my skills, my experience and every case study on this site, close to 100,000 words of it. Then just ask it specific questions. What has he shipped? What did the revenue engine produce? Has he run lifecycle for a consumer brand? It searches, reads, and answers with the live URL as its source.
https://hi-daniel.com/api/mcp
One call, abridged
› search_portfolio({ query: "attribution the CFO trusts" })
## 1. Marketing Ops: 200+ Workflows in Production https://hi-daniel.com/work/marketing-ops.html Finance stopped keeping a second spreadsheet once every number in the weekly report could be traced back to the record that produced it…
Four tools. Ask for the profile first, search when you want evidence, read a page in full when it matters.
get_profile
Who I am in one call: current positioning, the nine AI systems I designed and shipped, expertise areas, and the case studies behind each one. Assembled from the site itself, so it cannot drift from what the pages say.
search_portfolio
Ranked passages across the whole site, each with the URL it came from. Ask it about attribution, paid efficiency, lifecycle, agent architecture, or a specific number, and it returns the paragraphs that answer.
get_page
One page in full, section by section. Use it when an excerpt looks relevant and the whole argument matters more than the snippet.
list_pages
The index: every page with its title, description and word count, grouped into work, AI systems, expertise, principles, hiring lenses and the blog.
Streamable HTTP, so most clients need the URL and nothing else. There is no key to request and no account to make.
One command, then ask it anything about my work.
claude mcp add --transport http hi-daniel https://hi-daniel.com/api/mcp
Add it as a custom connector in settings and paste the endpoint. In Claude that is Settings, then Connectors, then Add custom connector.
https://hi-daniel.com/api/mcp
Add one entry to the client’s MCP config.
{
"mcpServers": {
"hi-daniel": { "url": "https://hi-daniel.com/api/mcp" }
}
}
The endpoint answers plain JSON-RPC, so curl is enough to see the tool list.
curl -s https://hi-daniel.com/api/mcp \
-H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
One serverless function, no dependencies, read-only. The corpus comes from the sitemap, so the server can only answer from pages this site actually publishes.
Each page splits at its section headings, the unit worth returning: big enough to carry an argument, small enough that the answer is not buried. Ranking is BM25 with page titles weighted in, tuned against twelve questions a hiring team would actually ask. The server holds no data beyond these public pages, and it writes nothing anywhere. If you would rather read the site yourself, every answer carries the URL. Or just send me a message.