What should a Capacitor MCP server do?

[eric-horodyski]

We're looking at building a Capacitor MCP server — a way for agents to get real information about your project instead of guessing from whatever it saw in training.

In order to build the right thing, we need to hear where AI actually falls short on Capacitor projects today. We have our own ideas, but you're the ones hitting it daily.

A few things we're looking to understand:

1. Where has AI been confidently wrong?
2. What do you still check by hand every time?
3. What would you not want an AI touching without asking first?

Specific examples help us the most; something like "it told me Camera.takePhoto() takes a quality string instead of a number" gives us more to work with than a feature request would.

If you'd rather just vote than write something up, there's a poll attached with some of our suspicions.

This will stay pinned and open. I'll come back with what we heard and what we're planning to build.

[eric-horodyski]

Something else: Strict version bound docs — serving specific versioned documentation according to the version of Capacitor being used in a project. (sourced from Discord)