Once we get more data connectors a la MCPs into this, it's going to be pretty powerful.
@jiquanngiam
-
Tool Call Outputs as Container Files: Data Processing Possibilities
By
–
Can tool call outputs directly become files in the container? I’d really want that – open up a ton of data processing possibilities.
-
MCP Protocol Adoption and Product Terminology Evolution
By
–
Ah, as it turns out, we're calling them connectors too in our product. My gut feel is that as the protocol gets adopted and matures, we will gradually stop referring to it. For example, we don't say "http sites", we just call them "websites". MCP is kinda of technical term for
-
Custom MCP Connectors Enterprise Management Solution
By
–
Glad to see custom connector support! We're building Enterprise grade management for MCPs that plugs really nicely into this. – check out MintMCP
-
MCP Setup Guide on MintMCP Platform
By
–
Which MCP were you trying? Let’s get you setup on http://
mintmcp.com! -
Custom MCP Connectors Enable Advanced AI Agent Integration
By
–
Huge! and custom MCP connectors too, that's so awesome.
-
AI Tool Access Control and Performance Risk Management
By
–
Most of the time I wouldn't be forking the repo, and I'm personally not comfortable with letting the AI delete my workflow run logs yet. Having these tools made available to the AI all the time creates unnecessary risk – and poorer performance.
-
Claude Code Tool Configuration Requires Manual JSON Editing
By
–
Unfortunately, the solution in Claude Code now is to manually edit the json settings file, and specify the tools I want into a list there; quite a painful experience to have to copy-paste across the 91 tools GitHub has made available.