MCP Servers
MCP is how a model reaches a system it does not otherwise know about. I build these for systems I actually use, which means I have hit the parts that are genuinely awkward rather than the parts that demo well. Someone deeper in this than me may find it basic — the point is that it is real and running, so you can judge it on that instead of on a number I gave myself.
How I use it
A résumé a model can only paraphrase
Built a server exposing work history as structured, queryable tools rather than a PDF, so specific questions get specific answers instead of a summary of a document.
An assistant that can read but not act
A tracker with a full read-and-write MCP surface over sessions, bankroll and opponents — defined tools with real side effects, not a chat window bolted onto a database.
Tool surfaces a model cannot navigate
Granularity is the design decision that matters. Too many narrow tools and the model cannot choose between them; too few and every call needs a paragraph of arguments. This is API design where the caller re-reads the docs every single time.
What I use
- Model Context Protocol
- TypeScript
- Claude API
Related skills
Want the detail behind any of this?
I can walk through any of it in as much depth as you want.