Does this work in the Qwen Code chat?

Yes. Run /mcp in the chat to open the MCP dialog and see your server's tools, prompts and resources. If Qwen Code was already running, restart it in the same project.

If I connect Incident Postmortem Prover to Gemini, can I use the same connection in Claude or ChatGPT later?

Yes, and that's the point: the connection is yours, not Gemini's. You paste the same link in any AI you use, and there's nothing new to set up or pay again. Connect a new AI and Incident Postmortem Prover is already there.

Do I need to hand my Incident Postmortem Prover password to Gemini?

Never. You sign in once at Vinkius, and we keep your logins encrypted and away from your AI. Gemini only ever sees the link, and you can remove it whenever you want.

What can I actually ask Gemini to do with Incident Postmortem Prover?

Whatever the Connector covers: check data, run actions and bring answers back. The Connector page lists every capability your AI gains, with real examples you can copy.

Gemini doesn't show the Connector. What do I check?

Run qwen mcp list or open the /mcp dialog, confirm the url was pasted exactly as copied, and confirm the Connector is active in your Vinkius account. If Qwen Code was already running, restart it in the same project.

Can I remove the access later?

Run qwen mcp remove and it's out of your sessions. Your Vinkius account keeps the connection and its history either way, ready for the next AI.

How to give Qwen Code access to Incident Postmortem Prover

Set up in seconds, once. From then on, Qwen Code gets things done for you: run one command, and Incident Postmortem Prover is live in your terminal.

Ask AI about this guide

Incident Postmortem Prover Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_KJycaUpjREM4styaMUmvRCfmlrKrfVMXPwF6uM9b/mcp

Connecting Incident Postmortem Prover to Qwen Code

About a minute, in your terminal

1Run: qwen mcp add --transport http Incident Postmortem Prover <your link>. The link above is the URL.
2Prefer a config file? Add it to ~/.qwen/settings.json (user) or .qwen/settings.json (project) with the httpUrl field. The link above is the URL.
3Enter /mcp in the chat to confirm the server appears. Incident Postmortem Prover is now part of Qwen Code.

Configuration · claude_desktop_config.jsonCopy

{
  "mcpServers": {
    "incident-postmortem-prover-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_KJycaUpjREM4styaMUmvRCfmlrKrfVMXPwF6uM9b/mcp"
    }
  }
}

Qwen Code + Incident Postmortem Prover

One chat. Your Incident Postmortem Prover, live inside Qwen Code.

Real prompts, answered with live data. This is the kind of session you will have in Qwen Code once the link is in.

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

These prompts ship with the Incident Postmortem Prover Connector. Once yours is connected, they work in your sessions.

The full capability set, the prompts and the observed latency live on the Incident Postmortem Prover Connector page.

Mission Control

See everything your Qwen Code agents do in Incident Postmortem Prover.

When Qwen Code runs a tool in Incident Postmortem Prover, it happens in your editor: you see the result, but not the request itself, what data it carried, or whether a rule was broken.

Now every move lands on your screen.

Every execution is recorded, enforced, and shown to you: what ran, what it returned, what was blocked, and why.

AI Briefing

Upgrade to unlock

Know exactly what needs your attention before you even look at the charts. One briefing. The full picture. The next move.

Requests

Total in this period

Avg Latency

API 88ms · Overhead 54ms

Vinkius Reliability

Agent 280 · Upstream 47 · Vinkius 15

Tokens

AI tokens processed

DLP Protected

Sensitive data redacted

Cost Saved

FinOps truncations applied

AI Agents Activities

last 30 days

30d agotoday

Request Volume & Latency

requests latency

Every request your Qwen Code agents make through Incident Postmortem Prover is logged, enforced and auditable. See how AI Governance turns agent activity into accountability, and what it means for your Incident Postmortem Prover workflows.

What sets us apart

It's not just the Connector that stays safe. Everything your agents do through it is.

Connecting Incident Postmortem Prover to your AI is step one. But an open line between your agents and Incident Postmortem Prover is only half the story: without protection, every action they take runs unguarded.

That's why protection doesn't stop at the door.

Every action your agents take through the Connector runs inside our infrastructure: signed activity logs, automatic key rotation, spending limits that pause instead of surprise, and a sandbox that isolates every execution.

Tamper Proof Activity Log

Every request your agents make in Incident Postmortem Prover is recorded and signed, so any change to the history becomes detectable.

Automatic Key Rotation

We rotate security keys every 24 hours. Your Incident Postmortem Prover connection stays protected without any manual work.

Spending Protection

We enforce the spending limit you choose and pause actions that exceed it until approval is received. Your Incident Postmortem Prover actions never surprise you.

Isolated Sandbox

Every execution through Incident Postmortem Prover runs isolated, with 34+ security rules covering memory, CPU, network access, file handling and execution.

Security Event Streaming

Security events flow to Splunk, Datadog or your own webhook, so Incident Postmortem Prover activity lands in the tools you already rely on.

Instant Resume

Idle connections resume in 3 to 5 ms while preserving their state, keeping your Qwen Code sessions responsive.

Malicious File Protection

We detect compressed files designed to exhaust system resources and block them before they ever reach Incident Postmortem Prover.

Credential Validation

We test your Incident Postmortem Prover credentials before saving them. Invalid credentials are rejected instead of being stored.

Separate Usage Limits

Usage stays isolated per account, so activity in one connection never consumes another account's allowance.

One Connector, one link, and the whole operation is protected. Not just the connection: everything your agents do through it.

These guarantees are not add-ons: they are the infrastructure every Incident Postmortem Prover connection runs on. Read how our infrastructure protects everything your Qwen Code agents do, end to end.

Inside Vinkius

Get Incident Postmortem Prover ready for your AI. It's easy.

You choose Incident Postmortem Prover from the Vinkius Catalog and get one connection link. That's it.

You choose Incident Postmortem Prover
You find Incident Postmortem Prover in the Catalog and install the Connector with one click.
Incident Postmortem Prover
Active
Enable Connector
Activating…
You add the link in Qwen Code
Vinkius gives you one connection link. In Qwen Code, you run one qwen mcp add command with the link as the HTTP URL, and the connection is ready.
Token generated successfully
MCP Connection URL
https://edge.vinkius.com/vk_preview_KJycaUpjREM4styaMUmvRCfmlrKrfVMXPwF6uM9b/mcp
Connection Token
vk_live_••••••••
Go to Dashboard

Set it up once. Use Incident Postmortem Prover with the AI you already use.

FAQ

Qwen Code access questions.

01
Does this work in the Qwen Code chat?
Yes. Run /mcp in the chat to open the MCP dialog and see your server's tools, prompts and resources. If Qwen Code was already running, restart it in the same project.
02
If I connect Incident Postmortem Prover to Gemini, can I use the same connection in Claude or ChatGPT later?
Yes, and that's the point: the connection is yours, not Gemini's. You paste the same link in any AI you use, and there's nothing new to set up or pay again. Connect a new AI and Incident Postmortem Prover is already there.
03
Do I need to hand my Incident Postmortem Prover password to Gemini?
Never. You sign in once at Vinkius, and we keep your logins encrypted and away from your AI. Gemini only ever sees the link, and you can remove it whenever you want.
04
What can I actually ask Gemini to do with Incident Postmortem Prover?
Whatever the Connector covers: check data, run actions and bring answers back. The Connector page lists every capability your AI gains, with real examples you can copy.
05
Gemini doesn't show the Connector. What do I check?
Run qwen mcp list or open the /mcp dialog, confirm the url was pasted exactly as copied, and confirm the Connector is active in your Vinkius account. If Qwen Code was already running, restart it in the same project.
06
Can I remove the access later?
Run qwen mcp remove and it's out of your sessions. Your Vinkius account keeps the connection and its history either way, ready for the next AI.
More questions about Incident Postmortem Prover? The Connector page answers them. See everything the Incident Postmortem Prover Connector can do

About the Connector

What Incident Postmortem Prover adds to your AI.

Once you connect it, your AI can take real actions in Incident Postmortem Prover when you ask. The Connector page lists every capability in detail, alongside the latency we measure in production and prompts worth trying first.

See everything the Incident Postmortem Prover Connector can do