Docker MCP Registry

repository·main·Indexed 19 days ago

https://github.com/docker/mcp-registry

A curated catalog of Model Context Protocol (MCP) servers that allows developers to discover, deploy, and integrate servers with AI assistants using Docker's container isolation and security features. The registry includes various servers such as AIS Fleet for maritime data, a Database Server supporting SQLite, PostgreSQL, and MySQL, a Docker Docs server, and an Okta MCP Server for IAM management.

Tokens
14K
Snippets
35
Records
71
Agent score
68%

What's inside docker-mcp-registry

  1. Overview of Okta MCP Server

    main

    The Okta MCP Server enables AI models to interact directly with your Okta environment using the Model Context Protocol (MCP). It is designed for IAM engineers, security teams, and Okta administrators to manage and analyze Okta resources through AI assistants.

    Key Features (v0.1.0-BETA):

    • FastMCP 2.0: Uses modern async patterns and optimized request handling.
    • Unified Client: A single CLI supporting multiple transports (STDIO, HTTP).
    • Advanced Security: Supports JWT bearer tokens with jwks_uri validation and enterprise authentication flows.
    • Enhanced Tools: All tools are rewritten with improved annotations for better AI understanding.
  2. Overview of the AIS Fleet MCP Server

    main

    The AIS Fleet MCP Server provides a unified interface for discovering, querying, and analyzing vessel activity using AIS (Automatic Identification System) data. It is designed for MCP-based agents and AI assistants to process natural-language maritime queries.

    Key capabilities include:

    • Rich Vessel Queries: Search for vessels by location, type, size, or custom geographic areas.
    • Historical Analysis: Examine traffic density, regional patterns, and port activity over time.
    • Advanced Queries: Detect specific events like canal transits, fishing zone activity, or cargo routes using combined filters.
    • Intelligence Layer: Acts as a data source for marine analytics, research, and location-aware AI applications.
  3. Use Vectra AI MCP Server tools for security operations

    main

    The Vectra AI MCP Server exposes several tool categories that allow AI assistants (like Claude, Cursor, or Windsurf) to interact with your security environment:

    • Detection Management: List, filter, and get details for security detections; retrieve detection PCAP files; count detections; and mark detections as fixed or unfixed.
    • Entity Management: List and query host and account entities; get detailed information by ID, name, or IP address; filter by state, priority, or tags; and access detection history.
    • Investigation & Response: Create/manage investigation assignments; add investigation notes to entities; list assignments by user or entity; and manage lockdown entities.
    • Platform Administration: List platform users (with role filtering) and manage user assignments/permissions; access platform configuration and logs.
    • Advanced Analytics: Generate AI-driven detection summaries and visualize entity detection relationships via interactive graphs.
  4. Configure SimpleCheckList deployment modes

    main

    The server supports three distinct operational modes via the MODE environment variable:

    1. backend (Default): Runs an HTTP API server on port 8355. This is the recommended mode for Docker deployments as it provides a stable container lifecycle and a health check endpoint.
    2. mcp: Uses STDIO transport for direct MCP protocol communication. This requires the -i (interactive) flag when running via Docker.
    3. both: Runs both the HTTP API and the MCP server simultaneously. This mode is more resource-intensive.

    Mode Comparison

    ModeTransportRecommended Use Case
    backendHTTPDocker/Containerized deployments
    mcpSTDIODirect integration with MCP clients (e.g., Claude Desktop)
    bothHTTP + STDIOWhen both interfaces are required simultaneously
    docker run -i mayurkakade/mcp-server:latest --mode=mcp
  5. Pin local server source to a Git commit

    main
    Local servers must ensure reproducibility by pinning their source repository to a specific Git commit. This is done using the source.commit field. Once a revision is accepted, an automated process will periodically propose updates via PRs.
  6. Context Window and Data Volume Limitations

    main

    The Okta MCP Server is optimized for lightweight workflows, not bulk data operations.

    Recommendation: Limit requests to fewer than 100 entities per transaction. Avoid fetching large datasets or performing multiple heavy API calls in a single request.

    AvoidBetter Approach
    "Fetch all 10,000 users...""Get the most recently created 20 users"
    "Find users who do not have Okta Verify...""Find users who haven't logged in for 90+ days, limit to first 50 results"

    For larger datasets and complex queries, consider using the Okta AI Agent.

  7. Security and Privacy Considerations for Okta MCP

    main

    Using the Okta MCP Server involves specific security and privacy implications that users must understand:

    Data Flow & Privacy

    When a request is made, the interaction happens directly between the LLM and the Okta MCP tools. All data returned (e.g., complete user profiles, group memberships) is sent to and stored in the LLM's context for the duration of the conversation. Ensure you are comfortable with your Okta data being processed by your chosen LLM provider (e.g., Anthropic, OpenAI, Google).

    HTTP Transport Security Warning

    HTTP transport modes (Streamable HTTP and SSE) are high-risk. They can open unauthenticated HTTP servers with full access to your Okta tenant. Anyone reaching the network port can issue commands.

    • Best Practice: Use the STDIO transport method (default) unless you have specific security controls in place.
    • Warning: Using remote HTTP access via mcp-remote is considered EXTREMELY DANGEROUS.
  8. Deploy Okta MCP Server via Docker

    main

    Docker images are available for all transport types. Use the appropriate image based on your deployment needs.

    STDIO (Recommended for Claude Desktop):

    {
      "mcpServers": {
        "okta-mcp-server": {
          "command": "docker",
          "args": [
            "run", "-i", "--rm",
            "-e", "OKTA_CLIENT_ORGURL",
            "-e", "OKTA_API_TOKEN",
            "fctrid/okta-mcp-server:stdio"
          ],
          "env": {
            "OKTA_CLIENT_ORGURL": "https://your-org.okta.com",
            "OKTA_API_TOKEN": "your_api_token"
          }
        }
      }
    }

    Streamable HTTP (Current Standard):

    docker run -d --name okta-mcp-http \
      -p 3000:3000 \
      -e OKTA_API_TOKEN=your_api_token \
      -e OKTA_CLIENT_ORGURL=https://your-org.okta.com \
      fctrid/okta-mcp-server:http

    Building Images Locally:

    docker build --target stdio -t okta-mcp-server:stdio .
    docker build --target http -t okta-mcp-server:http .
    docker build --target sse -t okta-mcp-server:sse .
  9. Security best practices for Vectra AI MCP Server

    main

    When using the Vectra AI MCP Server, follow these security guidelines:

    1. Service Account Tokens: Use dedicated service account tokens configured with the minimal required permissions (Principle of Least Privilege).
    2. Network Security: Ensure that connections to your Vectra AI platform are made over secure network channels.
    3. Review Operations: Always manually review and approve security operations (such as response actions) before they are executed by the AI assistant.
  10. Configure Okta Credentials

    main

    Before running the server, you must configure your Okta settings. Create a .env file from the sample provided and populate it with your required credentials.

    Required settings:

    • Okta domain (OKTA_CLIENT_ORGURL)
    • Okta API token (OKTA_API_TOKEN)
    • LLM settings (based on your chosen AI_PROVIDER)
    # Copy the sample config
    cp .env.sample .env
    
    # Edit the .env with your settings
  11. Set up the Wayfound MCP Server example

    main

    To run the Wayfound MCP server example locally, follow these steps to clone the repository, install dependencies, and configure your environment variables.

    Prerequisites

    • Python 3.10 or higher
    • A Wayfound MCP API key
    • An OpenAI API key

    Installation Steps

    1. Clone the repository:
      git clone https://github.com/Wayfound-AI/wayfound-mcp-example
      cd wayfound-mcp-example
    2. Install dependencies:
      pip install -r requirements.txt
    3. Configure environment variables: Create a .env file in the project root and add your keys:
      WAYFOUND_MCP_API_KEY=your_mcp_api_key_here
      OPENAI_API_KEY=your_openai_api_key_here
    4. Run the example:
      python main.py
    git clone https://github.com/Wayfound-AI/wayfound-mcp-example
    cd wayfound-mcp-example
    pip install -r requirements.txt
    # Create .env file with WAYFOUND_MCP_API_KEY and OPENAI_API_KEY
    python main.py