PRODUCTAGENTS & SLACK
Your coding agent pulls a finding over MCP, proof of concept included, and patches it where you already write code. Tag @Trident in Slack and it answers from your live findings.
Works with
01HOW IT WORKS
Ask your agent to fix what Trident found. It pulls the finding, patches the code and proves the fix before it opens the PR.
listTridentFindings(severity: "HIGH")
⎿ Found 3 open findings
getTridentFinding(findingId: "fnd_8f2k1")
⎿ High · Skips the tenant check
proof of concept attached
01
Your agent lists open findings and pulls one with its proof of concept.
Update(src/routes/invoices.ts)
⎿ Updated with 1 addition and 1 removal
42 - where: { id },
42 + where: { id, workspaceId },
02
Claude Code, Cursor and Copilot make the change in your repo.
Bash(pnpm test invoices)
⎿ 14 passed, including the
cross-tenant proof
✻ Opening a draft PR…(9s)
03
The proof runs as a test, so the draft PR only opens when it passes.
02YOUR AGENT
One MCP server, the same two tools, in whichever agent your team already writes code with.
Pulls the finding over MCP, patches the file and runs the tests in your terminal.
The same Trident tools in Cursor's agent, with the change ready to review.
Agent mode in VS Code calls Trident and edits the file inline.
The Codex CLI pulls findings from Trident the same way.
trident connect
also sets up
Windsurf
Cline
Roo
Junie
Warp
Kiro
Gemini
Amp
Grok
OpenCode
Zed
Continue
Goose
Devin
Capy03SLACK
Tag @Trident in any channel and it answers in the thread from your live findings, scans and PR reviews.
Mention @Trident wherever the question comes up.
Answers come from your current findings, scans and PR reviews.
Every answer links back to the finding in Trident.
Send a finding to Linear or Jira. The ticket is titled with its severity and carries the finding id, so it traces back to Trident.
Set Linear as the project's tracker and file any finding as an issue.
![Linear issue filed by Trident: [Trident · HIGH] Invoice download skips the tenant check](/v3/products/agents/slack/win-linear.webp)
Or file to a Jira project, with the severity, category and description.
![Jira work item filed by Trident: [Trident · HIGH] Invoice download skips the tenant check](/v3/products/agents/slack/win-jira.webp)
04SET UP
Install the CLI, sign in and connect. Trident wires every coding agent on your machine to one MCP server.
01
One package for login, connect, findings and fix.
npm i -g @trident-ai/cli02
Opens your browser and signs you in to your organization.
trident login03
Finds the coding agents on this machine and shows every change before it writes one.
trident connect04
Your agent pulls the finding over MCP and gets to work.
Fix the high-severity Trident findings
$
Trident connect
───────────────
server https://mcp.tridentsecurity.io/mcp
auth OAuth. Each client signs in on its first tool call.
No key is written.
Found
id client signal
claude Claude Code binary
cursor Cursor config
vscode VS Code (Copilot agent) config
codex Codex CLI binary
Plan
claude run claude mcp add … trident
cursor write ~/.cursor/mcp.json (+4 lines)
vscode write ~/.copilot/mcp-config.json (+4 lines)
codex run codex mcp add trident --url …
Nothing is written until you confirm.
05FAQ
Still have a question?
BOOK A DEMOClaude Code, Cursor, Copilot in VS Code and Codex, plus other MCP clients. They all connect through one remote MCP server.
In any channel. Tag @Trident and it answers in the thread from your live findings, scans and PR reviews, with a link back to the finding.
No. The MCP server signs you in with OAuth on the first tool call, so no key goes into a config file. trident connect writes nothing until you confirm.
Yes. Linear and Jira are both Trident integrations, so a finding can be filed where your team already tracks work.
Your findings. It lists the open ones and pulls a finding with its proof of concept, so the fix can be proven before the PR.
Yes. Start a free trial, and your first verified findings land within a day of connecting.
Run trident connect, then ask your agent for the fix. Each finding arrives with its proof of concept.
main from dana-k/invoice-pdf
src/routes/invoices.tsResolved const invoice = await db.invoice.findUnique({ where: { id: req.params.id },High: Invoice download skips the tenant check
getInvoicePdf looks the invoice up by req.params.id alone, so any signed-in user can download another workspace's invoice. Reproduced from a clean session. Proof in Trident
const invoice = await db.invoice.findUnique({ where: { id: req.params.id }, const invoice = await db.invoice.findFirst({ where: { id: req.params.id, workspaceId: req.user.workspaceId },