Available Plugins

Available Plugins

MCP Context Forge provides a comprehensive collection of production-ready plugins for security, performance, content transformation, and compliance. This page catalogs all available native and external plugins.

Plugin Categories

• Security & Safety
• Reliability & Performance
• Observability & Monitoring
• Content Transformation & Formatting
• Content Filtering & Validation
• Compliance & Governance
• Network & Integration
• Policy Enforcement

Security & Safety

Plugins for protecting against security threats, detecting sensitive data, and moderating content.

Reliability & Performance

Plugins for improving system reliability, performance, and resource management.

Observability & Monitoring

Plugins for telemetry, tracing, and monitoring tool invocations.

Content Transformation & Formatting

Plugins for transforming, formatting, and normalizing content.

Content Filtering & Validation

Plugins for filtering, validating, and controlling content.

Compliance & Governance

Plugins for ensuring compliance with licenses, regulations, and governance policies.

Network & Integration

Plugins for network operations and external system integration.

Policy Enforcement

Plugins for enforcing custom policies and business rules.

Plugin Types

Native Plugins

Native plugins run in-process within the gateway for maximum performance:

• Location: plugins/ directory
• Language: Python
• Performance: Lowest latency
• Configuration: Fully-qualified class path in plugins/config.yaml
• Use Cases: PII filtering, input validation, content transformation, business rules

Example configuration:

plugins:

  - name: "PIIFilterPlugin"
    kind: "plugins.pii_filter.pii_filter.PIIFilterPlugin"
    hooks: ["tool_pre_invoke", "tool_post_invoke"]
    mode: "enforce"
    priority: 50

External Plugins

External plugins run as separate servers for independent scaling and isolation:

• Location: plugins/external/ directory
• Transports: MCP (STDIO or Streamable HTTP) or gRPC (high-performance)
• Performance: MCP ~600 calls/sec, gRPC ~4,700 calls/sec, Unix socket ~9,000 calls/sec
• Configuration: kind: "external" with mcp: or grpc: connection details
• Use Cases: Advanced AI safety, complex ML inference, policy engines

Example configuration (MCP):

plugins:
  - name: "OPAPluginFilter"
    kind: "external"
    priority: 10
    mcp:
      proto: STREAMABLEHTTP
      url: http://localhost:8000/mcp

Example configuration (gRPC - high performance):

plugins:
  - name: "HighPerformanceFilter"
    kind: "external"
    priority: 10
    grpc:
      target: "localhost:50051"
      # uds: /var/run/grpc-plugin.sock  # use UDS instead of TCP

See gRPC Transport Guide for gRPC configuration including TLS/mTLS, or Unix Socket Transport for maximum local performance.

Getting Started

Using Native Plugins

1. Choose plugins from the catalog above
2. Add configuration to plugins/config.yaml
3. Set PLUGINS_ENABLED=true in .env
4. Restart the gateway: make dev

Using External Plugins

1. Build the external plugin: cd plugins/external/opa && make build
2. Start the plugin server: make start
3. Configure gateway to use external plugin in plugins/config.yaml
4. Restart the gateway: make dev

Plugin Development

To create your own plugin, see:

• Plugin Framework Guide
• Plugin Lifecycle Guide
• Plugin Architecture Specification

Support & Contributing

• Documentation: Plugin Framework Guide
• Issues: GitHub Issues
• Contributing: Follow plugin structure guidelines and include comprehensive tests

For plugin-specific questions, consult the README in each plugin directory.