Alright, it’s obviously needed 
1 Like
Have you tried:
What’s great about ^ is that if you find your process you’re trying to create isn’t consistent enough when using MCP - convert it to a script and reference that via .mdc instead.
I feel a lot of us are trying to capture process via plain text - until MCP tool calls can be @'ed in the same way that files / scripts can, we’re probably going to keep suffering as we try to build process via plain text.
1 Like
Interesting approach. one very odd thing is that they are running it remotely where I wouldnt want that. additionally if there are connection issues to the composio server then the whole tool usage suffers. i wonder if it works at all using a remote server due to reconnection need.
Composio is definitely a way better user experience to get plugged in with MCPs. Main issues right now are:
- Not enough developer centric MCPs available
- Composio controls your keys / privacy issue.
- No control over MCPs. For example, SQL MCP has like 100 functions that overwhelms Cursor context window.
Great news for all 3- on Tuesday I booked a call with them to determine for our org when they would be bringing the MCP service under a paid tier and I got a scoop on quite a bit of future work that would answer some of these Qs.
First Ill answer your 3rd bullet - it’s why I booked the call. This is something they are looking into and mentioned in the next month or so once they have MCP tied to the account system they’ll have a control plane for selecting which tool calls are available when you generate your link for cursor. I then pitched that this technically would allow us to generate like 3 different setups for 3 different custom agents for the same GitHub integration or what have you.
Next I’ll answer your second bullet - I will try not to be dismissive here, mostly going to post my experience when adopting it in my org. I brought this to my security guy he reviewed the Security - Composio page - it ticked the boxes for him in terms of what he would expect for this kind of service and I did some light exploration of their auth plane which is definitely being reused here: AgentAuth: Seamless Authentication for AI Agents with 250+ Apps - Composio and I felt ok with the world.
Now for the fun first answer - this may be a bit further out, but Composio supports you uploading your own openAPI spec and then a yaml for security configuration requirements and lets you host a custom integration on their site. I asked in that meeting if something like this would be coming for MCP. It seemed like it would, though it may be further out like 2-3 months mostly because of all the other big things landing above.
If you want to dig in on how they’d support your first question you don’t have to look very far in their implementation - they use supergateway which does a std io wrapper to sse which theoretically you can do with ANY MCP server hosted on their service.
(FYI they’ve now abstracted this public package behind composio-core - probably don’t want too many people understanding what goes into this)
1 Like
Yes we need mcp marketplace others has this feature and it made my coding 100x better pls add iit i tried adding mcp manually but my system didnt accept it some how i spend 1 hour on itt ! but if u have the market place u just click add bam its done ! i even send u screenshots on how to do it