Thank you! Yes we do provide auth and support other remote MCP servers via our API : https://docs.klavis.ai/api-reference/strata/create. It indeed support custom headers. Feel free to give us a try or come talk to us!

The eval benchmark also compared Notion and we are 13% higher than them as well!

That's the critical question. The key is that Strata never exposes all tools to the agent at once. Our progressive guidance acts as a dynamic allowlist, so that the agent only "sees" the specific tools relevant to its immediate task. This fundamentally reduces the blast radius at each step. We do provide a comprehensive audit trails for every action, giving a CISO a centralized control plane to manage and monitor agent capabilities, rather than an exponential risk. If you are interested, come talk to us!

How is a “dynamic allowlist” useful if it can still access anything based on what the user prompts? Is there a way to impose a static allowlist too?

Yes there is a way to impose a static allowlist. As a very simple example, you can disable certain servers completely via the UI or the API.

Isn’t that a blocklist?

Yes we do! Just signup to our website https://www.klavis.ai/home/mcp-servers and you will see all the apps and the auth options.

I think having the gallery viewable without an account would be valuable.

Oh yes for sure. Checkout https://www.klavis.ai/mcp-servers. You do not need to sign up. But you cannot see the auth flow for obvious reasons.

The lack of enterprise Microsoft services is really discouraging.

We are aware of this and working on it now. We are actually code complete on Microsoft Teams and Outlook. We will definitely launch it within the next week or so.

Yes it is the former. The value comes from its progressive guidance during a task, not just in the initial setup.

As for latency, we optimized for that. For examples, Strata automatically uses a direct, flat approach for simple cases. And we use less tokens compared to official MCP servers as well, as shown in the benchmark.

Isn't Microsoft going to eat your lunch with their "virtual tools" offering for high tool counts?

We tested our approaches with several thousand tools and it is working pretty well. Also we provide API access as well, so any developer can use this, not just on Microsoft or VS Code.

Haha yeah we did optimize it a lot before the launch!

Actually for us, our first prototype was pretty good! We are also surprised about that because it took us a day or so to build the the prototype (only for one integrations though). Then it took us another week to build another prototype for multiple integrations.

Glad it could be helpful to you! Curious what AI agents you are building and exactly what tools caused the failure.

In any case, feel free to give us a try!

As you can see from our examples, the main approach is not tool search. Instead, Strata guides your AI agent step by step, going from server to categories to actions to action details so that the model does not get overloaded. We actually have 1000+ tools for some of the integrations (e.g. GitHub) and this approach works better than traditional methods.

Think of it as a search engine vs. a file explorer. But we do provide documentation search as well. So you get the best out of the two worlds.

haha I like the word vibefrastructure!

Yes thank you for sharing your thoughts. The MCP interfaces definitely sound promising. However I think it does not stop people from building other MCP servers . And different people may have different opinions regarding how to design this interface for a search MCP server.

TBH I think all of these problems are still very new (remember MCP is only 6 months old) and I think we need to wait and see how things evolve.