codelogic

This MCP server exposes CodeLogic integration tools that help you analyze code impact and automate DevOps tasks. The five tools include: codelogic-method-impact to get an impact assessment for a specific method and its class, codelogic-database-impact to analyze impacts between code and database entities, codelogic-docker-agent to generate Docker agent configurations for CI/CD pipelines, codelogic-build-info to generate and send build information, and codelogic-pipeline-helper to generate complete CI/CD pipeline configurations. Use these tools to understand how changes propagate through code and databases, and to quickly scaffold CI/CD configurations with best practices. In agent mode, you can selectively enable or disable tools depending on your current task, such as running a quick method-impact analysis while drafting a patch or generating a new Docker agent configuration for a pipeline.

To use a tool, invoke its name through your MCP-enabled editor or IDE integration (e.g., Copilot agent mode, Claude Desktop, Windsurf, Cursor). Provide the required inputs (like method and class for the method-impact tool, or the database entity type and name for the database-impact tool), and the MCP server will query CodeLogic and return structured results that you can act on within your development workflow. For CI/CD integration, leverage the docker-agent, build-info, and pipeline-helper tools to generate configuration blocks and ensure they align with your chosen CI platform (Jenkins, GitHub Actions, Azure DevOps, GitLab CI).

Prerequisites:\n- Ensure you have Astral UV installed and available in your environment. See the Astral UV installation docs for your OS.\n\n1) Install Astral UV (if not already installed): follow the official guide at https://docs.astral.sh/uv/getting-started/installation/.\n2) Install the MCP server client/runner (uvx-based): ensure uvx is accessible in your PATH. If your IDE requires a specific path, adjust accordingly (e.g., /path/to/uvx).\n3) Configure your MCP server entry in your environment or editor: create or edit your mcp.json (or equivalent) to include the codelogic-mcp-server configuration as shown in the repository example.\n4) Set required environment variables for authentication and workspace: CODELOGIC_SERVER_HOST, CODELOGIC_USERNAME, CODELOGIC_PASSWORD, CODELOGIC_WORKSPACE_NAME, and optionally CODELOGIC_DEBUG_MODE.\n5) Start or reload your editor/IDE integration to load the MCP server and its tools.\n6) (Optional) If you encounter macOS-specific launch issues, consider switching to v1 uv (uv) or adjusting PATH/absolute paths as described in the MacOS workaround in the README for uvx.

Tips and notes:\n- The MacOS workaround suggests using uv instead of uvx in certain IDEs; if you experience the 'Failed to connect client closed' error, switch the command to uv and adjust the mcp.json accordingly. Ensure CODELOGIC_SERVER_HOST is reachable from your environment.\n- When using multiple IDEs (VS Code, Claude Desktop, Windsurf, Cursor), keep a consistent configuration for host, workspace, and credentials to avoid authentication prompts.\n- For CI/CD integration, the docker-agent tool helps generate platform-specific configurations for Jenkins, GitHub Actions, Azure DevOps, and GitLab CI, including environment variables and volume mounts.\n- If you encounter issues with specific tools, check the CodeLogic service endpoints and verify that the API credentials have the required permissions for the requested operations (method and database impact analysis, build info collection, and pipeline generation).