Nikola Tesla Inventor Prover MCP Connector for Claude

The domain is irrelevant. The thinking method is universal. You must: (1) MENTALLY SIMULATE — build the complete system in your mind, running at maximum demand. Every process, every failure mode, every recovery path — visualized before building. Tesla ran the AC motor in his mind for months, wearing down imaginary bearings. If you need to "build it and see," you have not thought deeply enough, (2) PROVE MATHEMATICALLY — derive WHY the system works. Not "it should work" — calculate the bounds, the constraints, the relationships between components. Tesla derived the rotating field equations. Edison tried 6,000 filaments, (3) ELIMINATE FRICTION — map every flow path and remove every unnecessary step, wait, handoff, and bottleneck. Tesla removed the commutator. Do not improve friction — eliminate its source, (4) FIND RESONANCE — identify the structural amplifier that multiplies output without proportional resource increase. One teacher training five peer tutors who each help five students reaches 25 students — not hiring 25 tutors. Resonance, not brute force, (5) HARMONIZE — all components must share one rhythm, one lifecycle, one coordination mechanism. Tesla's polyphase system was one field — not isolated parts wired together. If rejected, your design is empirical, frictional, or brute-force. Re-engineer it.Send ALL parameters in ONE call — the analyses above plus YOUR OWN verdict: every PIVOT boolean, verdict and clarification. The engine cross-checks the pivots against the verdict and rejects incomplete or self-contradictory calls. Structured reflection tool that forces the LLM to think like Nikola Tesla — the inventor who built the AC motor entirely in his mind before touching metal, who derived the rotating magnetic field equations before winding a single coil, and who refused trial-and-error as "a lack of theoretical foundation." Applicable to ANY domain: designing a bakery, engineering a power grid, architecting software, planning a supply chain, or inventing a physical product. The domain does not matter — the THINKING METHOD is universal. Catches Empirical Guessing (building first, theorizing later — Edison tested 6,000 materials for the lightbulb filament through brute trial-and-error. Tesla called this "a little theory and calculation would have saved him 90% of the labor." A baker who opens a second location "because business is good" without calculating whether the unit economics survive higher rent, split management attention, and supply chain complexity is guessing empirically. A city planner who adds lanes to reduce traffic without modeling induced demand is guessing empirically. The question is never "does it work?" — the question is "can you PROVE why it will work before you build it?"), Causality Blind (describing WHAT happens without proving WHY — "the restaurant is popular because the food is good" is observation, not causality. WHY is it popular? Location within 200m of a metro exit (foot traffic), menu optimized for 12-minute average preparation (lunch crowd turnover), and a 4.7 Google rating creating a self-reinforcing discovery loop. Tesla did not say "the motor spins" — he proved that orthogonal alternating currents create a rotating magnetic field whose angular velocity equals the supply frequency divided by the number of pole pairs. The mechanism IS the understanding), Friction Tolerance (accepting inefficiency as inherent — Tesla eliminated the mechanical commutator from electric motors because brushes create friction, sparking, wear, and energy loss. He did not improve the commutator — he removed it entirely. A hospital emergency room with a 4-hour average wait has friction: triage → registration → waiting → examination → testing → waiting → results → treatment. Friction elimination: registration during triage (parallel, not sequential). Point-of-care testing (eliminate lab round-trip). Bedside results delivery (eliminate second wait). The question is never "how do we make waiting more comfortable?" — it is "why is there waiting at all?"), Brute Force Scaling (adding resources linearly instead of finding resonance — Tesla powered entire cities from one Niagara Falls generator through polyphase AC: one source → long-distance transmission → local transformation. Edison needed a power plant every square mile because DC cannot travel far. A school that hires one tutor per struggling student is Edison — linear scaling. A school that creates a peer tutoring program where one trained student helps five others is Tesla — structural amplification. A factory that doubles workers to double output is brute force. A factory that redesigns the assembly sequence so each station feeds the next without idle time is resonance — output doubles with zero additional resources), and System Fragmentation (isolated components instead of unified harmony — Tesla's polyphase system was ONE electromagnetic field: generator, transmission line, transformer, and motor all synchronized to 60 Hz. Every component resonated at the same frequency. A company where marketing runs campaigns that sales has never seen, where product builds features that support cannot explain, and where finance tracks metrics that operations does not recognize — that is not a company, it is a collection of departments. A farm where irrigation, fertilization, harvesting, and storage operate on independent schedules instead of synchronized to the crop lifecycle — that is fragmentation. The question is: do all parts share ONE rhythm, or does each part have its own?). Call once per major design, invention, or system decision — in any domain