Operations | Monitoring | ITSM | DevOps | Cloud

Introducing Cortex MCP in Devin: AI Engineering Guided by Your Best Practices

Cortex is now in the Devin Marketplace keeping your AI within the guardrails of your org wide best practices With this integration, Devin, the world’s first AI software engineer, can use Cortex data & best practices, like Scorecards, to understand your engineering standards and automatically fix issues at scale. Here’s how it works: Watch the demo to see how Eyal, one of the engineers at Cortex, used Cortex & Devin to turn best practices into action.

Go beyond the dashboard: Operationalize DORA with our new Scorecard and Academy course

If you've adopted DORA metrics as your standard for measuring DevOps performance, stop us if this hypothetical scenario doesn't sound familiar. You check your DORA dashboard during a lunch break, full of optimism that you’ll get a clear picture of your team’s performance. Instead, you leave with nothing but a sandwich in your stomach and the nagging feeling that you’re focusing too much on the results of the game instead of the people that are playing it.

From insight to impact: Key takeaways from our DORA webinar with Nathen Harvey

For most engineering leaders, getting a DORA dashboard up and running feels like a huge win. You can finally track performance, compare it to industry benchmarks, and report on your progress. But then a nagging question settles in: how do you actually make the numbers go up? That frustration points to a common gap between the dashboard and the daily engineering practices that drive those outcomes.

Building a DORA metrics Scorecard

There are a lot of ways to gauge the performance of your DevOps teams and the health of your software, but DORA metrics have emerged as the industry standard. If you aren’t familiar with DORA metrics, take a few minutes to read this comprehensive guide to understanding DORA metrics. DORA metrics were designed to offer a high-level, long-term view of how your teams are performing.

Top AI Prompts for Engineering Leaders using the Cortex MCP

AI assistants have transformed how developers work. And now coupled with the Cortex MCP that connects AI assistants directly to live service data, ownership records, and organizational standards, developers can get accurate, context-rich answers about their services and standards right in their IDE. → Tips and prompts for developers using the Cortex MCP But what about engineering leaders?! Your opportunities with AI assistants extend far beyond code generation.

Tips and prompts for developers using the Cortex MCP

AI coding assistants are already transforming how developers work, helping them write code faster, answer tough questions, and automate repetitive tasks. It’s exciting, it’s powerful… and it’s just the beginning. Cortex MCP connects your AI assistant directly to your live service data, ownership, and organizational standards so it can give accurate, context-rich answers right in your IDE.

Cortex MCP set up

Learn how to set up the Cortex MCP in under 5 minutes. The MCP integrates directly into your IDE, giving instant access to Cortex data without leaving your coding environment. It reduces context switching by enabling natural questions about services and teams, and streamlines workflows with real-time data from Cortex, Jira, GitHub, and more.

Cortex MCP set up

Learn how to set up the Cortex MCP in under 5 minutes. The MCP integrates directly into your IDE, giving instant access to Cortex data without leaving your coding environment. It reduces context switching by enabling natural questions about services and teams, and streamlines workflows with real-time data from Cortex, Jira, GitHub, and more.

Introducing the Cortex MCP Server

Cortex gives engineering teams full visibility and control over their services, from ownership and standards to service history and production readiness. Our goal is to help teams stay aligned and move faster so they are ready for whatever is ahead. The reality for any engineering team is that developers spend the most of their time in their IDE, not their IDP. And while developers love the context Cortex provides, they don’t love context switching.