How to Use the Bugcrowd MCP in Cline

Q: Can Cline fetch my current Bugcrowd submissions?

Yes, Cline uses listsubmissions to retrieve all your past and active reports. It can then run getsubmission to pull down specific triage comments or status updates.

Q: How does Cline know which Bugcrowd targets are in scope?

Cline executes listtargets to fetch the active asset list. It then cross-references these targets against your local files to ensure you only test authorized endpoints.

Q: Can I retrieve organization details?

The getorganizationinfo tool fetches your core Bugcrowd company profile. Cline uses this to verify your account permissions before runing other security tools.

Let Cline audit Bugcrowd targets and draft vulnerability submissions directly inside VS Code.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Bugcrowd MCP to Cline

Create your Vinkius account to connect Bugcrowd to Cline and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Bugcrowd with Cline

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Map active Bugcrowd targets in Cline

The `list_targets` tool exposes all scoped assets directly to your Cline agent. Cline reads this list, compares the targets to your active workspace files, and determines which directories are subject to testing. This means Cline can write targeted test suites only for assets that are explicitly in scope. It prevents you from wasting time auditing files that are excluded from the Bugcrowd program.

Draft vulnerability reports using Bugcrowd MCP Server

The `create_submission` tool allows Cline to push vulnerability findings straight to your Bugcrowd account. This MCP Server lets your agent compile the logs and create the submission entry when it finds a bug. You get a fully formatted draft with reproduction steps in seconds. Cline handles the API payload generation so you do not have to leave VS Code to file a report.

Audit active program engagements

The `list_engagements` tool pulls active pen tests and bounties directly into Cline. Cline parses these engagements to understand the timeline, reward structure, and testing rules for your active assessments. By invoking `get_engagement`, your agent extracts specific rules of engagement. This ensures that every test script Cline writes respects the program boundaries.

Setup guide

Set up Bugcrowd MCP in Cline

Prerequisites

VS Code with Cline extension installed
Active Vinkius subscription with a valid endpoint token

1

Open Cline MCP settings

Click the Cline icon in the VS Code sidebar to open the Cline panel. Then click the MCP Servers icon (server stack) at the top-right corner of the panel.
2

Add a remote server

Click "Remote Servers" at the top, then click "Add Remote MCP". In the Name field, type bugcrowd-mcp. In the URL field, paste your Vinkius endpoint: https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp. Get your token from cloud.vinkius.com.
3

Enable the server

After saving, the server appears in the Cline MCP panel. Toggle the switch to enable it. The status indicator turns green when the connection is live.
4

Start using tools

Return to the Cline chat and ask: "Check my latest Bugcrowd refund status." Cline will discover the available tools and request your approval before invoking each one — giving you full control over every action.

Cline MCP Settings

{
  "mcpServers": {
    "bugcrowd-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Bugcrowd. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Bugcrowd now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Bugcrowd MCP in Cline

Open the Cline sidebar, click the MCP icon, and add the server URL. Cline will instantly load all ten Bugcrowd security tools.

Yes, Cline uses `list_submissions` to retrieve all your past and active reports. It can then run `get_submission` to pull down specific triage comments or status updates.

Cline executes `list_targets` to fetch the active asset list. It then cross-references these targets against your local files to ensure you only test authorized endpoints.

The `get_organization_info` tool fetches your core Bugcrowd company profile. Cline uses this to verify your account permissions before runing other security tools.

Yes, the Vinkius MCP sandbox isolates all API traffic, meaning your submission payloads and engagement details remain encrypted in transit. Cline processes this data locally within your VS Code session without third-party exposure.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript