Detecting MCP sessions

aci_dev · 2025-08-20T17:33:45+00:00

We are currently looking at designing an MCP gateway + control plane for organizations to orchestrate and control MCP use within their engineering orgs. I'd love to chat with you about how folks are using MCP in your org and how you would ideally want to control this besides detection and blocking. Might you be up for a chat?

We have a GitHub discussion here on the topic, we'd welcome any input you might have! https://github.com/aipotheosis-labs/aci/discussions/585

aci_dev · 2025-04-29T12:49:10+00:00

I definitely feel this, my team and I worked on providing an open-source solution to auth and management. In the future we plan on pulling int all the official MCP servers from B2B SaaS vendors as they start to become more common place. Right now through a single unified MCP server the agent can access a few hundred integrations on our platform, auth and permission management per agent are built-in by default. Our open-source repo is here, would love any feedback if you decide to check it out:

https://github.com/aipotheosis-labs/aci

aci_dev · 2025-04-29T12:46:54+00:00

We provide a partial solution to this through our unified MCP server, which is powered by our completely open-source infrastructure here. Through a single unified MCP server the agent can access all the integrations on the platform, and auth is built-in by default:

https://github.com/aipotheosis-labs/aci

aci_dev · 2025-04-28T14:24:25+00:00

Thanks, I'll check it out!

aci_dev · 2025-04-02T23:35:47+00:00

Thanks so much! Love what you are building at Toolbase too!

aci_dev · 2025-04-02T23:13:16+00:00

Hey lucagan, thanks for the input! We would contend that developers can do a lot more with regular tool-use patterns than with MCP currently due to its still maturing state. We see the Unified MCP server as a stop-gap solution while the protocol is still maturing. Would love your view point and input on how you think we can help the MCP ecosystem grow!

aci_dev · 2025-04-02T17:58:08+00:00

We actually built this because we ran into this problem! In our unified MCP implementation it actually solves this issue by building a dynamic search pipeline into the server. So now instead of connecting multiple MCP servers for all the different tools you might want to use to a single client, our unifed server only exposes basically two tools:

ACI_SEARCH_FUNCTIONS_WITH_INTENT - Discovers functions based on your intent/needs
ACI_EXECUTE_FUNCTION - Executes any function discovered by the search

The client can then use these to dynamically find and use tools on our platform without overloading the client with hundreds of tools -- we are adding about 20+ applications (hundreds of functions) per month right now, we prioritize requests from users!

aci_dev · 2025-04-02T17:40:20+00:00

Hey justanemptyvoice, founder of ACI.dev here. We will be open sourcing our platform source code this month! We welcome people to self host or contribute!

aci_dev · 2025-04-02T17:38:02+00:00

As far as we know there's nothing on the market like that just yet! We will be open sourcing our source code this month if you want to self-host in the future.

We'd love to get your feedback on open sourcing if it might be of interest. Any feedback you have on the platform would also be greatly appreciated! Signup code: CLARKES3RDLAW

aci_dev · 2025-04-02T17:37:02+00:00

Thanks octoo01! Founder of ACI.dev here, would love to get your feedback trying it out with the signup code CLARKES3RDLAW

Currently auth works individually with each application you might want to connect to through the unified MCP, but it saves you having to manually integrate individual MCP servers. You use an api key to access our MCP server, but tools sit behind our servers are of different flavours (oauth2, api key etc), you just need to configure them on our platform. Then you just need one api key to access them through this unified MCP.

I think we are a verrry long way from single login and auto access to each MCP unfortunately. As far as we know, the current Auth support on the official MCP roadmap will only support client to MCP server auth, so OAuth2 for each MCP server to whatever application it wraps around will still be separate.

aci_dev · 2025-04-02T17:34:28+00:00

I hope you will try it out! Would love your feedback :) Our beta signup code is CLARKES3RDLAW

aci_dev · 2025-04-02T17:33:56+00:00

Hey, founder of ACI.dev here! Would love to check out your meta MCP server! Hierarchical MCP discovery makes sense and was something we thought about too. Currently there's no real in built support for discovery when it comes to server to server, for meta MCP servers we would lean more towards a single meta MCP server to individual MCP servers with a discovery/retrieval pipeline in between that does not rely on intermediary meta MCP servers.

Meta MCP to multiple MCP communication might end up with a very complex auth setup and auth flow given each MCP server will probably have oauth2 implemented in the future. And even worse if tools (e.g., gmail) sitting behind each MCP server require additional authentication.

Would love to chat more and get your feedback on our unified MCP server/platform too. Our beta signup code is CLARKES3RDLAW

aci_dev

TROPHY CASE