Announcing the AISLE MCP Server. Marek Pavelka 11/09/2026 AI code assistants have changed software engineering, yet most security tools still ask developers to tab-toggle. Today, Aisle, Inc. is excited to announce that the AISLE MCP server provides access to your security findings in the code editor you already use. Now you can chat with your backlog to see what issues to prioritize, explain complex findings, and inspect AISLE-generated patches, all without breaking flow. Here's why it matters, how to set it up, and 4 prompts you can use now. What you can do with the AISLE MCP server. By serving security findings directly to your agent harness, AISLE's MCP server ensures that fixes get made right away instead of waiting for someone to open a ticket. Simply connect AISLE to an AI agent that supports the MCP standard, such as Claude Code, OpenAI Codex, or Cursor, to get started. Here are just a few of the things you can do with the server: * Fix issues directly from your code editor: Review each open issue, tell your agent to fix it, and keep shipping. * Don't build on vulnerable code: Before changing a file, check its open AISLE findings so you don't extend a vulnerable pattern or write new code that depends on it. Then fix the findings in their own PR. * Eliminate shared API keys: Devs login with their own AISLE credentials, so you no longer need shared API keys. Read-only callout. To help teams roll out the AISLE MCP server as fast as possible, Aisle, Inc. has made it read-only. Its goal is to deliver AISLE's code analysis and triage to engineers without inviting a drawn-out review process. With read-only access, the server can't modify findings, change settings, or trigger scans. Instead, the agent edits code locally under your normal git permissions, and you only see the findings your AISLE role allows. This balance delivers advanced cyber reasoning while ensuring full human control. 4 example prompts. Here are four prompts you can use to get value from the MCP server on day one: * Focus on high-priority issues: "What findings does AISLE have a proof-of-exploit for?" * Understand proposed fixes: "Explain how AISLE's recommended patch remediates this vulnerability." * Iterate on an AISLE-generated patch: "The patch doesn't cover every variant. Iterate upon it to fix the whole class." * Review IaC issues: "Do we have any exposed secrets in our IaC files?" The AISLE MCP tools. So far, Aisle, Inc. is rolling out five tools with the AISLE MCP server: * issue-list: returns a list of open issues. * issue-detail: provides full technical details for each issue * issue-count: gets you the total number of open issues * fix-list: serves a list of AISLE's issue fixes * repo-list: lists the repositories uploaded to AISLE How to start using the AISLE MCP server. Here's how to get started: Claude Code. OAuth: Add the server, then run /mcp in Claude Code and follow the sign-in prompt. Shell 1claude mcp add -transport http aisle https://your-company.api.aisle.cloud/mcp PAT: Add the same server with your token: Shell 1claude mcp add -transport http aisle https://your-company.api.aisle.cloud/mcp \ 2 -header "Authorization: Bearer YOUR_AISLE_PAT" Run /mcp to check the connection. Cursor. Open your personal MCP configuration at ~/.cursor/mcp.json. Use one of these entries under mcpServers. JSON 1{ 2 "mcpServers": { 3 "aisle": { 4 "url": "https://your-company.api.aisle.cloud/mcp" 5 } 6 } 7} JSON 1{ 2 "mcpServers": { 3 "aisle": { 4 "url": "https://your-company.api.aisle.cloud/mcp", 5 "headers": { 6 "Authorization": "Bearer YOUR_AISLE_PAT" 7 } 8 } 9 } 10} Restart Cursor. For OAuth, follow its sign-in prompt; then check that Aisle appears among your available MCP tools. Keep a config containing a PAT private. Codex. Shell 1codex mcp add aisle -url https://your-company.api.aisle.cloud/mcp 2codex mcp login aisle PAT: Set AISLE_PAT in the environment where Codex runs. Add this to ~/.codex/config.toml: JavaScript 1[mcp_servers.aisle] 2url = "https://your-company.api.aisle.cloud/mcp" 3bearer_token_env_var = "AISLE_PAT" Restart Codex and run codex mcp list to check the configuration. Want more capabilities? If you want to access more AISLE capabilities through the MCP server, let Aisle, Inc. know. Aisle, Inc. is always looking for ways to improve the user experience, whether on the AISLE platform or in your code editor. Talk to the team. FAQs. See what AISLE can find and fix autonomously in your own code.

Cohere and AISLE signed an LOI for a proposed acquisition. The October 15 proposal would combine AISLE's security research with Cohere's AI work, with leadership and Prague changes dependent on completion. November 9, 2026 Key points * 01 Cohere and AISLE announced a signed LOI for the proposed acquisition on October 15, 2026. * 02 Cohere plans to combine AISLE's security research with AI development and deployments for enterprise and public-sector customers. * 03 The announced leadership roles and conversion of AISLE's Prague headquarters depend on the transaction completing. * 04 AISLE and Cohere report more than 500 vulnerabilities across more than 100 codebases, and AISLE's co-founders say customer continuity remains a priority. Cohere and AISLE signed a letter of intent for a proposed acquisition. The plan covers AI security, future leadership, Prague and AISLE customers. What Cohere and AISLE proposed. On October 15, 2026, Cohere and AISLE announced that they had signed a letter of intent (LOI) for Cohere to acquire AISLE. The proposal would bring AISLE's security research into a planned Cohere cybersecurity business called Cohere Cyber; the company changes described in the announcements depend on the transaction completing. Cohere and AISLE announced the LOI. How AISLE's security work fits the plan. AISLE describes a system that combines foundation-model capabilities with security expertise to examine code, validate potential vulnerabilities, filter false positives and produce patches for maintainers to review. Cohere's plan is to connect that work with its AI-model development and secure deployment efforts. Cohere says the proposed Cohere Cyber business is intended to serve enterprise and public-sector customers, including organizations deploying AI in private clouds, on their own premises or in air-gapped environments, systems isolated from external networks. These are planned capabilities, not established outcomes of a completed integration. Cohere's announcement describes the intended scope. Leadership and Prague plans. Cohere named AISLE co-founder Ondrej Vlcek as the planned leader of Cohere Cyber and future senior vice president. The announced roles also place AISLE co-founder Jaya Baloo as Cohere's global chief information security officer and co-founder Stanislav Fort as vice president of AI security. AISLE says Fort would work with Cohere co-founder and chief technology officer Ivan Zhang to connect security research with core-model development and training. AISLE says its Prague headquarters would become Cohere's Prague office if the transaction completes. Cohere separately says it plans a substantial, long-term investment in the city. AISLE's announcement describes the office change as conditional on completion. Reported vulnerability findings and customer priority. AISLE and Cohere report that AISLE found more than 500 previously unknown vulnerabilities assigned CVEs, or Common Vulnerabilities and Exposures identifiers, across more than 100 codebases during its first year out of stealth. They also report that AISLE found all 12 vulnerabilities in an OpenSSL security release issued in January, and 18 of the 24 CVEs in curl's latest release at the time of the announcement. The OpenSSL release year was not specified in the companies' statements. AISLE and Cohere attribute these figures to AISLE's work. For AISLE customers, the co-founders' stated focus is continuity and stronger products; the Prague office change depends on the transaction completing. AISLE's three co-founders say continuity for customers and partners remains a priority as the transaction progresses. Other Languages Read this article in another available language.