Discovery
Back to browse
GitHubTool

Superglue - integrations from natural language

YC W25 project that builds production-grade tool integrations from a prompt. Aimed at long-tail SaaS connectors that legacy iPaaS doesn't cover.

View source ↗
#integrations#ai-agents#api-gateway#typescript#yc

This entry doesn't have a long-form writeup yet. Follow the source link above for the full context.

Recent discussion

From the wider web

Related entries

GitHubToolFeatured

trace-mcp - framework-aware codebase MCP for coding agents

MCP server with 138 tools and cross-language framework awareness (58 integrations across 81 languages). Indexes Laravel/Inertia/Vue, Rails/Hotwire, Django/HTMX edges so agents skip re-deriving call graphs. Decision memory links architectural choices to the code they're about. Local-first ONNX embeddings, optional LSP enrichment.

Why I saved this - Distinct from Qartez - Qartez is structural (PageRank, blast radius), trace-mcp is framework-semantic. The cross-language edges (Laravel controller -> Vue page via Inertia) are the differentiated bit.
#mcp#claude-code#code-intelligence#typescript#static-analysis
GitHubToolFeatured

wanman - worktree-isolated multi-agent runtime for Claude Code and Codex

Multi-agent runtime that spawns each Claude Code or Codex agent in its own git worktree and home directory. JSON-RPC subprocess control, task pooling, artifact storage. Solves the share-a-directory failure mode that breaks most multi-agent harnesses.

Why I saved this - The 'one-man train' framing is load-bearing: humans observe rather than approve every step. Worktree-per-agent isolation is the upgrade most multi-agent harnesses skip.
#claude-code#codex#multi-agent#orchestration#typescript
GitHubToolFeatured

Claudraband - persistent, resumable Claude Code sessions over HTTP and ACP

Wraps the real Claude Code TUI with a session lifecycle layer. Resumable non-interactive workflows, HTTP daemon for remote/headless control, ACP server for editor integrations (Zed, Toad). Drives your existing Claude Code install rather than reimplementing it - keeps skills, hooks, MCPs, and approvals intact.

Why I saved this - Different from the Claude SDK - Claudraband drives the real CLI from outside, so user-installed skills/hooks/MCPs all still work. The ACP support is the easy path to editor integrations.
#claude-code#remote-control#developer-tools#typescript#cli