4,500+ servers built on MCP Fusion
Vinkius
Tag
#Feedback Loops

#Feedback Loops MCP Servers

Discover 7 MCP servers tagged with Feedback Loops on the Vinkius App Catalog.

15Five

15Five

6 tools

Empower performance management with 15Five. Manage check-ins, high fives, objectives, and team feedback directly from your AI agent.

Lattice

Lattice

9 tools

Retrieve HR employees, goals, feedback, and reviews directly from Lattice.

Officevibe

Officevibe

10 tools

Manage employee engagement via Officevibe. Track pulse survey scores, feedback, and NPS directly from your AI agent.

Surveypal MCP

Surveypal MCP

12 tools

Design employee experience surveys and customer feedback programs with analytics that turn responses into actionable improvements.

Systems Thinking Prover MCP

Systems Thinking Prover MCP

1 tools

AI thinks in straight lines. This engine is a 6-pivot cognitive trap that forces the LLM to map feedback loops, second-order effects, and bottlenecks before proposing any architectural change.

Gates Platform Prover MCP

Gates Platform Prover MCP

1 tools

A team built a product while competitors owned the standard. It says 'better product' instead of naming a structural moat. It sells standalone tools instead of bundling. It assumes market position is safe. That is not a platform strategy. That is a slide deck for a product no one will remember. This tool forces five Gates-level platform axes: standard ownership, developer ecosystem, bundling strategy, paranoid execution, and cross-product feedback loops.

Watt Efficiency Prover

Watt Efficiency Prover

1 tools

A team spent 6 weeks 'optimizing' their operation. No baseline. No analysis. They restructured the most visible department. Processing time got worse. The bottleneck was a manual approval step in a different department. Untouched entire time. Watt measured the Newcomen engine and found 80% of steam energy wasted reheating the cylinder. He did not 'optimize the engine'. He measured, identified, and eliminated specific waste. This tool forces that discipline: identify waste with data, instrument baselines, design feedback, isolate the bottleneck, and quantify improvement with numbers.