FEAT: MCP (Model Context Protocol) Integration
Nobody has claimed this yet.
Assessment
This issue has not been assessed yet.
Description
Is your feature request related to a problem? Please describe.
When red teaming agentic AI systems, PyRIT currently requires custom integrations for each external tool, data source, or capability. This creates friction when testing systems that use diverse toolsets and limits the ability to dynamically discover and interact with target capabilities during assessments.
TheModel Context Protocol (MCP) by Anthropic provides a standardized interface for LLM-to-tool communication that's rapidly being adopted across the AI ecosystem. Without MCP support, PyRIT cannot natively interact with MCP-enabled targets or leverage the growing ecosystem of MCP servers for red teaming workflows.
Describe the solution you'd like
Add native MCP support to PyRIT, enabling red teaming agents to dynamically discover and use external tools, data sources, and prompt templates via the MCP protocol.
Core Capabilities:
- Tools: Execute functions (converters, probes, external APIs, target system tools)
- Resources: Read data (attack datasets, MITRE ATLAS mappings, reconnaissance results)
- Prompts: Load templates (red team agent prompts, attack strategies)
Proposed Implementation:
The codebase already defines MCP types in MessagePieceType:
MCP_CALL = "mcp_call"
MCP_LIST_TOOLS = "mcp_list_tools"
MCP_APPROVAL_REQUEST = "mcp_approval_request"
These types aren't implemented yet. This proposal would complete that implementation.
Proposed Usage:
from pyrit.mcp import MCPServerConfig, MCPTransport
# Native MCP support in target
target = OpenAIResponseTarget(
mcp_servers=[
MCPServerConfig(
name="converters",
transport=MCPTransport.STDIO,
command="python",
args=["converters_server.py"]
),
MCPServerConfig(
name="recon",
transport=MCPTransport.SSE,
url="http://localhost:8080/sse"
),
]
)
# Target auto-discovers tools, model can call them during conversation
Implementation Phases:
- Core MCP client implementation using the MCP Python SDK
- Integration with OpenAIResponseTarget
- Integration examples with existing agentic security tools as MCP resources/tool
- Documentation and notebooks
Additional context
Relationship to Existing Issues:
- Supersedes #1083
- Supersedes #1118
References:
Open Questions:
- Should example MCP servers live in PyRIT core or a separate repository?
- Which transport should be prioritized first (STDIO vs SSE)?
- Any security considerations for MCP server sandboxing during red team operations?
I'm happy to start the implementation and can break this into smaller PRs. Would welcome collaboration from anyone interested in this direction.
- Dominant language
- Python
- Stars
- 4.5k
- Forks
- 896
- Avg merge
- 3d 8h
- Merged PRs (30d)
- 191
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/PyRIT
-
Difficulty 3/5 1-2 days Newbie friendliness 65/100
-
Bug: triage GUI help wanted
Difficulty 3/5 1-2 days Newbie friendliness 65/100
-
feature-request
Difficulty 3/5 1-2 days Newbie friendliness 70/100
-
bug help wanted
Difficulty 4/5 3-5 days Newbie friendliness 68/100
-
not ready yet
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
stephrobert/dsoxlab#238 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
sublimehq/package_control#1780 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
nwg-piotr/nwg-displays#145 ·