In which case, that sounds like it would be, in general, fairly problematic. Means that there’s an upper limit of the number of tools
I’m not sure I’m following the core question or issue.
There’s a limit to the number of tools due to context windows.
Is there a way to separate for claude the MCP serveres such that only a subset of those authoried on mcp.pipedream.com are associated and accessed for a given MCP configuration to reduce the tool call
For example, I removed a bunch of MCP servers because pipedream was returning errors/warning as it increased.
I’m still not quite sure what you’re asking — remember that each of those apps will contain many tools, so that’s actually a lot to expose to Claude.
Is there a way to address this so that all those tools aren’t exposed to Claude?
The ideal case is that I can have separate MCP servers that are treated as distinct instances as it was before when the URLs were different.
When you connect to Pipedream MCP on the above screen, you can enable / disable whichever apps you want to expose tools for. Yea, everything now goes through a single static endpoint, as opposed to app-specific URLs. You could actually hack it this way:
https://mcp.pipedream.net/v2?app=trello
https://mcp.pipedream.net/v2?app=google_calendar
etc