Update Policy for Cache of API Results
I'm busy building an MCP for my (for now just mine) Postman collections, and using the Postman API for things like fetching a list of collections, or a particular collection. This API isn't much good for analysis of any kind, even simple searches, so I'm going to cache the results in a local db that I can hopefully execute json queries on.
What strategy can I use to determine when I must update the cache db? It's going to be rare that someone would use Claude just to find one collection or request, so using it not being in the cache as a trigger isn't the most sound policy.
Maybe an update on every startup of the MCP, or on every n queries to it, or what?
0 Replies