io. github. chinlee2200-dotcom/ bridgecore
by chinlee2200-dotcom · remote · no sign-in to list tools · v0.3.2 · published by GitHub user chinlee2200-dotcom
Say what should happen; get the right app tool per step, an n8n workflow, or the call itself.
5 tools: 1 do something that can't be undone, 3 change things and 1 only read.
Scanned Oct 21, 2026
- Deletes or cancels0Claude Code: deny
- Can't be undone1Claude Code: ask: see these tools
- Changes things3Claude Code: ask: see these tools
- Only reads1Claude Code: allow: see these tools
4 checks matched something in the tool definitions. No finding is not a safety guarantee. How the checks work.
claude mcp add --transport http bridgecore https://mcp.usebridgecore.com/Findings
Matches of fixed checks, with the text they matched.
The server marks "make_n8n_workflow" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"openWorldHint":false}; The description's first verb is "generate": a word for a change.
- Warninspect_workflow
The server marks "inspect_workflow" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "inspect_workflow" says "inspect": a word for reading.
- Infodo
The description mentions "credentials".
What this check looks forMatched text
description: "...ver sends the request and never accepts credentials. A 'when …' need or several steps retur..."
The description mentions "credentials".
What this check looks forMatched text
description: "...blanks only the person can fill and the credentials to connect. Shape-checked; the person t..."
Tools
Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.
5 tools
Can't be undone 1Claude Code: ask
inspect_workflowRead 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,…1 finding
Why it is in this group
- The name "inspect_workflow" says "inspect": a word for reading.
- The description says "irreversible".
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "inspect_workflow" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "inspect_workflow" says "inspect": a word for reading.
Description, as the server wrote 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.
Annotations the server declares
- title: Inspect workflow
- readOnlyHint: true
- openWorldHint: false
Changes things 3Claude Code: ask
doOne tool for 3,604 app capabilities (n8n catalog + OpenAPI + MCP): say what should happen; get the exact call.1 finding
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Info
The description mentions "credentials".
What this check looks forMatched text
description: "...ver sends the request and never accepts credentials. A 'when …' need or several steps retur..."
Description, as the server wrote it 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).
Annotations the server declares
- title: Do it (preview)
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
make_n8n_workflowGenerate 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 …2 findings
Why it is in this group
- The description's first verb is "generate": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Info
The description mentions "credentials".
What this check looks forMatched text
description: "...blanks only the person can fill and the credentials to connect. Shape-checked; the person t..."
- Warn
The server marks "make_n8n_workflow" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"openWorldHint":false}; The description's first verb is "generate": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- title: Make n8n workflow
- readOnlyHint: true
- openWorldHint: false
plan_automationTurn 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).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: Plan automation
- readOnlyHint: true
- openWorldHint: false
Only reads 1Claude Code: allow
find_recipeFind a ready-made automation recipe for a plain-words need, e.g.No findings
Why it is in this group
- The name "find_recipe" says "find": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Find recipe
- readOnlyHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Install
Pinned to version 0.3.2. Values in angle brackets are yours to fill in.
claude mcp add --transport http bridgecore https://mcp.usebridgecore.com/Run in a terminal.
Claude Code permissions
Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__bridgecore__find_recipe"
],
"ask": [
"mcp__bridgecore__do",
"mcp__bridgecore__plan_automation",
"mcp__bridgecore__make_n8n_workflow",
"mcp__bridgecore__inspect_workflow"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as bridgecore. Review it before you use it.
