Skip to main content Announcing Tool Policies: AI agent permissions down to the field Read the announcement
Live 43 Actions

Black Duck MCP Server
for AI Agents

Connect your AI agent to StackOne's Black Duck MCP server and give it 43 MCP tools out of the box. Auth, tool execution, and security all managed.

Black Duck logo
Black Duck MCP Server
Built by StackOne StackOne
DrataGPLocalyzeFlipMindtoolsScreenloop

Coverage

43 Agent Actions

Agents can read, write, delete and run operations in Black Duck. Extend your agent's capabilities with custom actions.

Authentication

Agent Tool Authentication

Per-user OAuth in one call. Your Black Duck MCP server gets session-scoped tokens with zero credentials stored on your infra.

Agent Auth →

Security

Agent Protection

Every Black Duck tool response scanned for prompt injection in milliseconds, with 88.7% accuracy, all running on CPU.

Prompt Injection Defense →

Performance

Max Agent Context. Min Cost.

Free up to 96% of your agent's context window to enhance reasoning and reduce cost, on every Black Duck call.

Tools Discovery →

What is the Black Duck MCP Server?

A Black Duck MCP server lets AI agents read and write Black Duck data through the Model Context Protocol, Anthropic's open standard for connecting LLMs to external tools. StackOne's Black Duck MCP server ships with 43 pre-built actions, fully extensible via the Connector Builder, plus managed authentication, prompt injection defense, observability, and agent execution runtime. Connect it from MCP clients like Claude Desktop, Claude Code, Cursor, Goose, and VS Code, or from agent frameworks like OpenAI Agents SDK, LangChain, and Vercel AI SDK.

All Black Duck MCP Tools

Every StackOne action for Black Duck, ready for your agent. Read, write, delete and run operations, scoped to exactly what you need.

Code Locations

  • List Code Locations

    List every scan code location recorded on the instance.

  • Get Code Location

    Get a single scan code location by id.

  • Update Code Location

    Rename a code location or change its mapped project version.

  • Delete Code Location

    Delete a scan code location from the instance.

Components

  • List Components

    Search the global component knowledge base.

  • Get Component

    Get a single component from the knowledge base by id.

  • Update Component

    Update the description of a catalog component.

Licenses

  • List Licenses

    Search the global license knowledge base.

  • Get License

    Get a single license from the knowledge base by id.

Notifications

  • List Notifications

    List system notifications within a date range.

  • Delete Notification

    Delete a single notification.

Policy Rules

  • Create Policy Rule

    Create a new compliance policy rule.

  • List Policy Rules

    List every policy rule configured on the instance.

  • Get Policy Rule

    Get a single policy rule by id.

  • Update Policy Rule

    Update an existing compliance policy rule.

  • Delete Policy Rule

    Delete a compliance policy rule from the instance.

Projects

  • Create Project

    Create a new project record to attach versions and scans to.

  • List Projects

    List all projects in the Black Duck instance.

  • Get Project

    Get a single project by id.

  • Update Project

    Update a project's name or description.

  • Delete Project

    Permanently remove a project and its version history.

Users

  • Create User

    Create a new user account on the instance.

  • List Users

    List every user account on the Black Duck instance.

  • Get User

    Get a single user account by id.

  • Update User

    Update a user's name or active status.

  • Delete User

    Delete a user account from the instance.

Project Versions

  • Create Project Version

    Create a new version under an existing project.

  • List Project Versions

    List every version recorded under a project.

  • Get Project Version

    Get a single project version by id.

  • Update Project Version

    Update a project version's name, phase or distribution.

  • Delete Project Version

    Delete a single version from a project.

Other (12)

  • Add Component To Version

    Manually add a component to a project version's BOM.

  • List Code Location Scan Summaries

    List the scan summaries recorded under a code location.

  • List Version Components

    List the bill-of-materials components on a project version.

  • List Roles

    List every role defined on the instance.

  • Get Current User

    Get the user account the API token belongs to.

  • List Component Vulnerabilities

    List vulnerabilities known for a specific component.

  • Get Vulnerability

    Get a single vulnerability record from the knowledge base.

  • Remove Component From Version

    Remove a component from a project version's BOM.

  • Mark Notification Read

    Mark a single notification as read.

  • Assign Role To User

    Assign an existing role to a user account.

  • Unassign Role From User

    Revoke a previously assigned role from a user account.

  • Reset User Password

    Trigger a password reset for a user account.

Set Up Your Black Duck MCP Server in Minutes

One endpoint. Any framework. Your agent is talking to Black Duck in under 10 lines of code.

Agent Frameworks

Claude Desktop
{
  "mcpServers": {
    "stackone": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@latest",
        "https://api.stackone.com/mcp?x-account-id=<account_id>",
        "--header",
        "Authorization: Basic <YOUR_BASE64_TOKEN>"
      ]
    }
  }
}

Check More developer MCP Servers

Wiz

696+ actions

IONOS

501+ actions

Workiva

266+ actions

KnowBe4

259+ actions

HighLevel

251+ actions

WorkOS

234+ actions

SAP Concur

232+ actions

Black Duck MCP Server FAQ

Does StackOne have a Black Duck MCP server?
Yes. StackOne offers a hosted Black Duck MCP server with 43 pre-built actions, and every action is tested and QA'd by StackOne. Connect it to Claude, Cursor, and any other MCP client, or to any agent framework through the AI Action SDK. It ships with managed agent authentication, prompt injection defense, and tool discovery with server-side execution that preserve your agent's context window and keep reasoning performance.
Black Duck MCP server vs direct API integration: what's the difference?
A Black Duck MCP server and direct API integration serve different use cases. Direct API integration is for software-to-software work, where backend code calls Black Duck. A Black Duck MCP server is for AI agents that discover and call Black Duck at runtime, such as MCP clients like Claude and Cursor, plus framework agents built with OpenAI, LangChain, or Vercel AI. StackOne provides both.
How does Black Duck authentication work for AI agents?
Black Duck authentication for AI agents works through a StackOne Connect Session. Create one via the dashboard or the SDK to get an auth link and ready-to-paste config for Claude Desktop, Cursor, and other MCP clients. Your user authenticates their own Black Duck account; StackOne handles token exchange, storage, and refresh. Credentials never reach the LLM, and each user is isolated via origin_owner_id.
Are Black Duck MCP tools vulnerable to prompt injection?
Yes. Black Duck MCP tools can be vulnerable to indirect prompt injection. Any tool that reads user-written content, such as documents, messages, tickets, records, or free-text fields, is a potential vector. StackOne Defender scans every tool response before it enters the agent's context. It runs regex patterns in ~1ms, then a MiniLM classifier in ~4ms. Accuracy is 88.7%, and it runs entirely on CPU.
What is the context bloat of a Black Duck agent and how do I avoid it?
Context bloat happens when Black Duck tool schemas and API responses eat your Black Duck agent's memory, preventing it from reasoning effectively. A single Black Duck query can return a massive JSON response, and connecting multiple tools compounds the problem. Tools Discovery reduces it by loading only the tools relevant to each query.
Can I limit which actions my Black Duck agent can access?
Yes. You can limit which actions your Black Duck agent can access directly from the StackOne dashboard. Toggle actions on or off, or restrict them to specific accounts, with no code changes to your agent. Session tokens can be scoped to exact actions so if one leaks, exposure stays contained.
Can I create custom agent actions for my Black Duck MCP server?
Yes. You can create custom agent actions for your Black Duck MCP server using Connector Builder. It's an integration agent your coding assistant (Claude Code, Cursor, or Copilot) can invoke to research Black Duck's API, generate production-ready connector YAML, test against the live API, and validate before you ship.
When should I NOT use a Black Duck MCP server?
Skip a Black Duck MCP server if your integration is purely software-to-software, because direct Black Duck API integration is simpler when no AI agent is involved. For deterministic, compliance-critical operations (financial transactions, regulatory reporting), direct API gives you predictable behavior without agent-driven decision-making. MCP shines when AI agents need to dynamically discover and call Black Duck actions at runtime.
What AI frameworks and AI clients does the StackOne Black Duck MCP server support?
The StackOne Black Duck MCP server supports both. MCP clients (paste-and-go apps): Claude Desktop, Claude Code, Cursor, VS Code, Goose. Agent frameworks (code SDKs you build with): OpenAI Agents SDK, Anthropic, Vercel AI, Google ADK, CrewAI, Pydantic AI, LangChain, LangGraph, Azure AI Foundry.

Put your AI agents to work

All the tools you need to build and scale AI agent integrations, with best-in-class connectivity, execution, and security.