[smattiso]

This is a great idea. I have a question:

Typically speaking an LLM is the code driving the control flow and the MCP servers are kind of dumb API endpoints (find_flights, search_hotels, etc) say for a travel MCP.

With your product, how is the LLM made aware of the underlying data store in a more useful way than “func search(query)”?

It seems to be that if you could expose some precomputed API structure into the MCP for a given data store then the LLM could reason more effectively about the data rather than throwing search queries into the void and hoping for the best?

[behindsight]

From what I have gathered their main differentiator is taking the approach of assigning each discrete data point its own "entity" definition that is independent but can be extended for each data provider.

So since its all represented by entities, you could treat them like any other vectorised data in your vector data store and use vector search.

It's a nice technique, but probably tricky if they ever venture into encapsulating endpoints in realtime for rapidly changing b2c applications (ratelimits/cronjob latency)