As someone with ADHD, I built this because context-switching between documentation, form builders, and actual work destroys my flow. Now I can stay in one conversation and just describe what I need.

The interesting technical challenges:

1. API Complexity Abstraction Tally's API requires deeply nested objects for simple fields. An email field needs ~10 nested objects with UUIDs. I built a translation layer so users can just say "add an email field" in natural language, and the server handles the complex structure behind the scenes.

2. Safe Bulk Operations For destructive operations, I implemented a preview-then-confirm pattern. The server generates a confirmation token during preview that must be passed back for execution. This prevents accidental mass deletions while keeping the conversation flow natural.

3. Smart Rate Limiting The server monitors API responses and adjusts its behavior dynamically. When hitting rate limits, it automatically reduces batch sizes and adds delays between requests. Added randomization to prevent multiple instances from hitting the API simultaneously.

4. Type Safety Throughout Full TypeScript with runtime validation for both MCP messages and Tally API responses. This caught several undocumented API quirks during development.

Performance notes: - Batch creation of 100 forms: ~12 seconds with batched operations - Individual creation of 100 forms: ~5 minutes due to rate limits - Human creation of 100 forms: probably a full week of mind-numbing clicking - Submission analysis across 10K responses: ~3 seconds

The code is ISC licensed: https://github.com/learnwithcc/tally-mcp

This particularly helps when you need to create multiple similar forms but your brain rebels at repetitive tasks. Curious if others are building MCP servers and what workflows you're optimizing for.

Also interested in thoughts on MCP vs traditional CLI tools. The conversational interface is slower for simple operations but much better for complex, multi-step tasks where you might forget the exact syntax.

Comments URL: https://news.ycombinator.com/item?id=44381728

Points: 3

# Comments: 0

I have ADHD and am, and always have been, a reader and writer. Once I get locked in on something, I have trouble refocusing my attention elsewhere.

I work with individuals with ADHD who regularly point out that I have provided too much text for them to process.

We each have our own unique challenges in this, and recognizing that helps strengthen the community as a whole IMO.

How many of these commenters have founded a business that has faced the level of scrutiny they're applying here? Have they taken the time to speak with someone who has worked with a Shimmer coach about their experience? I ask these questions because I've actually done so, unlike many here.

Since my diagnosis last year, I've been with Shimmer, and my coach has been nothing short of amazing. While I can only speak for my experience, I urge others to think twice before criticizing a service that many active users, including myself, rely on and appreciate.

I've even written a blog post about my positive experience with Shimmer, which I'd happily share. Discovering Shimmer was a pivotal moment for me when I was tackling a significant challenge, and it helped me gain the momentum I needed to start my own business.

Was Shimmer the only factor? Certainly not! But would I have made such transformative changes in my life without it and my coach's guidance? That's unlikely.

I was at a loss for where to begin, and choosing Shimmer was the right decision for me. So, I urge everyone to be thoughtful and considerate before leaving critical comments. Give those who use the service a chance to share their perspectives. I've witnessed Shimmer's evolution over the past year and the hard work they've put in to make their service valuable.

Let's honour that effort by engaging in a respectful and balanced discussion.

Edit: forgot to include this -> https://satellitemtl.com/blog/adhd-coaching/