Day 30 — Custom Development + MCP
30 days. 30 builds. 10 industries. 9 services.
For the final day, an open-source starter kit. Every pattern from the previous 29 builds distilled into one clean skeleton — so you can ship your own MCP server in an afternoon.
Example Queries
Tools
| Tool | What It Does |
|---|---|
| contact_lookup | Deep view of a single contact — profile, open items, recent transactions, lifetime value, and activity log. Matches on name, email, phone, or id. |
| contact_upsert | Create or update a contact in one call (matched by email). Writes to the activity log automatically. |
| items_list | Filtered list of items with computed overdue / age flags. Filter by status, priority, category, assignee, or overdue-only. |
| item_create | Create an item under a contact. Resolves the parent by name, email, or id so the LLM doesn't need to know database ids. |
| analytics_summary | Business-wide rollup — active contacts, open / overdue items, revenue (completed vs pending), top contacts by LTV, activity volume. |
| activity_log | Query the audit log. Filter by contact, action, or trailing window. Answers "what happened and who did it?" |
The Patterns
After 29 builds across law firms, vet clinics, real estate, fitness, construction, healthcare, and six more industries, the same six tool shapes kept showing up. That's what this kit is:
A "give me everything about X" deep-view tool. Fuzzy match on whatever identifier the user has — name, email, phone, id.
Create-or-update in one call. Match on a natural key (email, slug). Always write to the audit log.
Filtered list with computed flags (overdue, at-risk, stale). Return the rows plus aggregate counts in one payload.
Child records linked to a parent. Resolve the parent by any identifier so the LLM doesn't need to know ids.
One tool that answers "what's happening in the business?" — counts, totals, top-N, trailing windows.
Query the activity log. Filter by actor, action, or window. This is the tool you didn't know you needed until you needed it.
Why This Build
After doing this thirty times, the pattern was obvious: the MCP wrapper is trivial. What takes time is deciding which six questions your team actually asks, modeling the data so those answers come out in one SQL block, and keeping computed fields (overdue, at-risk, age) out of the schema.
This kit is the skeleton of those decisions. A parent entity. Two child tables. An audit log. Six tools. Rename “contacts” to whatever your business actually tracks and you have a working MCP server your team can query from Claude Desktop by end of day.
Talk to your business. It's not that hard anymore.
Demo Data
8
Contacts
9
Items
10
Transactions
9
Activity
Eight contacts across active, paused, and archived states. Items in every status including one overdue and one urgent. Transactions covering completed, pending, and a refund. An activity log with referrals, status changes, and priority bumps. Small enough to read, varied enough that every tool returns something interesting.
Setup
git clone https://github.com/ashleynharrison/30-days-claude-code
cd 30-days-claude-code/day30-mcp-starter-kit
npm install && npm run seed && npm run buildThen rename contacts to whatever your business actually tracks, replace the seed data, and you're running.
If you want one built specifically for your business — by someone who just shipped thirty of them — let's talk.