io.github.chinlee2200-dotcom/bridgecore · v0.3.2 · agents-and-memory
io.github.chinlee2200-dotcom/bridgecore is healthy: it completed an MCP handshake in 4771 ms and exposes 5 tools.
Say what should happen; get the right app tool per step, an n8n workflow, or the call itself.
Endpoint: https://mcp.usebridgecore.com/ (streamable-http)
Repository · Website · JSON · Add to my inventory
| Users (last 30 days) | 0 |
| Handshake | Healthy |
| Auth needed | None |
| Tool count | 5 |
| Latency | 4771 ms |
| Last checked (UTC) | 2026-10-16T07:05:43.166Z |
| Checked (UTC) | Status | Latency | Error |
|---|---|---|---|
| 2026-10-16T07:05:43.166Z | Healthy | 4771 | |
| 2026-10-15T03:15:36.292Z | Healthy | 3489 |
do | One tool for 3,597 app capabilities (n8n catalog + OpenAPI + MCP): say what should happen; get the exact call. Plain words in ('send an sms to +1 213 555 0100 saying hello', 'add a row to google sheets'); the matching capability is found, its required inputs are checked (values you said out loud — e |
find_recipe | Find a ready-made automation recipe for a plain-words need, e.g. 'when a typeform is submitted add a row to google sheets and send a slack message'. Returns the best matching recipes (apps chained with →, what it does, the n8n workflow JSON, the blanks to fill and accounts to connect) plus matching |
plan_automation | Turn a plain-words need into steps (one trigger + actions) and pick the concrete tool for each step from 3,000+ app capabilities (n8n nodes, OpenAPI, MCP). Reports a gap when the named app cannot do a step instead of substituting another app. |
make_n8n_workflow | Generate an importable n8n workflow JSON from a plain-words need, with every node wired in order, values said out loud already filled (emails, #channels, trigger events), plus the list of blanks only the person can fill and the credentials to connect. Shape-checked; the person tests it in n8n before |
inspect_workflow | Read an existing n8n workflow JSON (a template from n8n.io, an export, anything) and say what it would do before it runs: every node's label (read-only / reversible / irreversible, computed from the node's own resource + operation), which irreversible steps (send, post, delete, pay) would run with n |