# AI Maturity Engineering teams have adopted the use of AI coding assistants and other tools, and many companies are launching internal initiatives around using AI tools for increased efficiency.
Use Cortex MCP as part of your AI adoption efforts.
### How Cortex helps with AI adoption and maturity Your organization can drive AI Maturity with Cortex by: * Ensuring that AI tools are being adopted by engineering teams via [Scorecards](/solutions/ai-maturity/configure.md#step-2-configure-scorecards-to-track-ai-adoption-and-standards) * Configuring [Workflows](/solutions/ai-maturity/configure.md#step-3-automate-processes-via-workflows) to automate the process of requesting access to AI tools such as GitHub Copilot * Using [Cortex MCP](/solutions/ai-maturity/configure.md#step-4-configure-cortex-mcp), a tool that enables engineers to query information in natural language and receive quick answers. It uses relevant context from your Cortex workspace, ensuring awareness of your system's structure when answering your questions. * Reviewing [Eng Intelligence](/solutions/ai-maturity/configure.md#step-5-review-eng-intelligence-metrics-attributable-to-ai) metrics to watch how trends change as AI tools are adopted and used consistently ## Drive AI Maturity in Cortex Learn how to use Cortex features to drive AI Maturity: [**Automate AI Maturity**](/solutions/ai-maturity/configure.md). Learn about maintaining and continuously improving your AI initiatives: [**AI Maturity in action**](/solutions/ai-maturity/in-action.md). --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.cortex.io/solutions/ai-maturity.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.