Bridgecore

io.github.chinlee2200-dotcomPublished by GitHub account chinlee2200-dotcomv0.3.2Updated Oct 24, 2026

Say what should happen; get the right app tool per step, an n8n workflow, or the call itself.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowDeveloper Tools

Overview

AI-generated overview

Bridgecore turns plain-language automation requests into concrete app calls, step plans, or importable n8n workflows, and inspects existing workflows before you

What you can do
Find and run app capabilities: match a plain-words request to one of thousands of app capabilities and return the exact call with required inputs checked, or find ready-made automation recipes with their n8n workflow JSON, blanks and accounts to connect. Plan automations: turn a need into one trigger plus actions, choosing a concrete tool per step and reporting a gap when an app cannot do a step. Generate workflows: produce an importable n8n workflow JSON with nodes wired in order, stated values filled in, and the remaining blanks and credentials listed. Inspect workflows: read an existing n8n workflow JSON and describe what each node would do, labeling steps read-only, reversible or
When to use it
Use it when you want to automate a task across apps without hand-building the workflow: describing a need in plain words, getting a step-by-step plan or a ready n8n workflow, or checking what an existing n8n workflow would actually do before running it.
Requirements
A remote MCP endpoint; no local package, environment variables or headers are declared. No authentication is declared. The generated workflows are meant to be imported and tested in n8n, and the accounts for the apps involved must be connected there.
Before you install
Generated workflows and calls can send, post, delete or pay once run in n8n; inspect_workflow flags irreversible steps, so review before executing. Credentials for the connected apps are listed for you to supply in n8n, not handled by this server. Requests are sent to a third-party remote service.

Installation

In SourceWeft

  1. Open Bridgecore in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.chinlee2200-dotcom%2Fbridgecore/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "bridgecore": {
      "type": "http",
      "url": "https://mcp.usebridgecore.com/"
    }
  }
}

README

This repository has no README.

Tools

5

do

Do it (find the capability, preview the exact call)

One tool for 3,604 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 — emails, #channels, +phones — are filled for you), and the exact HTTP/MCP request that would be sent is returned, with `missing` naming any input still needed. Preview only: this server never sends the request and never accepts credentials. A 'when …' need or several steps returns one preview per step; n8n-only steps come back as an importable n8n workflow. Running the request for real is offered separately by the Bridgecore Apify Actor (apify.com/bridgecore/bridgecore-automation-planner).

Parametersneedrequiredinputsdry_run

find_recipe

Find a ready-made automation 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 public n8n templates (title + official link). Covers connecting apps, automating a workflow, syncing tools, and getting notified when something happens.

Parametersneedrequiredlimit

plan_automation

Plan an automation (tool per step)

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.

Parametersneedrequiredalternatives

make_n8n_workflow

Make an importable 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 turning it on. Say 'and ask me first' (or approval='always') and a one-tap approval gate — a Slack/Telegram/Gmail message with Approve / Decline buttons — goes in front of the step, so nothing is sent, posted, deleted or paid until the person taps Approve.

Parametersnameneedrequiredapproval

inspect_workflow

Check an existing n8n workflow before running it

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 nobody asked, which steps already have an approval in front of them, and which nodes have no account connected. With add_gates=true it returns a copy of the workflow with a one-tap Approve / Decline step (Slack, Telegram, Gmail…) wired in front of every such step. Nothing is run; the original is not modified.

Parametersask_viaworkflowrequiredadd_gates

Version history

3
  1. v0.3.2LatestOct 16, 2026
  2. v0.3.0Oct 15, 2026
  3. v0.1.0Oct 14, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.