2 Sept 20254 min read

Explyt 4.1 with Python and MCP support is Out!

Explyt TeamPublished 2 Sept 2025

Media

4 videos

Explyt 4.1 introduces new powerful features for an even better coding, testing, and debugging experience.

Key improvements include:

Reproduce, inspect and fix inside JetBrains IDEs, with the debugger, run configurations and IDE facts as evidence.

Overall improvements:

  • enhanced stability of the agent and tools
  • support for running and fixing tests for IntelliJ IDEA users on Windows under WSL
  • better Gradle and Maven support: the agent now reuses your IDE build settings and suggests syncing when configurations change

Added LLM models:

  • OpenAI GPT-5-mini
  • OpenAI GPT-5

Python support

You can use assistant’s features in PyCharm.

Rules: how they improve your coding experience

The Rules feature allows you to ensure the Explyt Agent follows your instructions for specific contexts. A rule is a Markdown snippet that is added to the system prompt.

Well-defined rules can significantly improve your experience with the Explyt Agent

Tips to start:

  • specify a scope for when the rule should be applied
  • instruct the agent on the expected steps the agent should follow when completing your queries
  • instruct the agent what it should not do (for example, editing forbidden files)
  • define the desired output format (for example: plan, proposed edits, summary) to make results predictable
  • ask agent

Workflows: save you time and tokens working with prompts

The Workflows feature allows you to save repeated prompts and manually use them when appropriate. A workflow is a simple Markdown file that you add to your prompt via the input area. This allows you to reuse effective pipelines and boost your productivity.

Tips to start:

  • instruct the agent to ask you appropriate questions before moving to the implementation
  • instruct the agent on how to gather context for the request
  • specify the expected steps the agent should take
  • you can attach files to your request and reference them in your workflow
  • keep workflows reusable by using placeholders (for example: {goal}, {files}) and filling them when invoking

MCP servers

With MCP, developers don't need to build custom integrations for every single tool.

The protocol supports two-way communication: AI agents can not only request and receive data, but also perform actions in external applications or even directly in the operating system. In short, MCP provides a universal interface that makes it easier for LLMs to work with external tools and resources.

Explyt 4.1 supports test frameworks: JUnit 5, JUnit 4, TestNG, kotlin-test, mocking frameworks: Mockito, Mockito-Kotlin, MockK, SpringMockK, and build systems: Maven, Gradle, IntelliJ Build System.

You can access language models either through Explyt servers or by using your API-keys.

Explyt Enterprise with Virtual Private Cloud (VPC) or self-hosting solution guarantees corporate data security. Your company's code is not sent to the internet and is not used for model training.

Reproduce, inspect and fix inside JetBrains IDEs, with the debugger, run configurations and IDE facts as evidence.

Newsletter

Get Explyt updates in your inbox

Release notes, engineering deep dives, and new articles like this one. No spam, unsubscribe anytime.

Comments

Loading comments...

Keep reading

All articles

Why choose Explyt?

Feature

Debugger

Yes

Ultimate only

No

No

No

No

SAST vulnerability scanner

Yes

No

No

No

No

No

IDE refactorings (Rename, Change Signature…)

Yes

No

No

No

No

No

Test coverage guarantees

Yes

Coverage gates

No

No

No

No

No

Semantic code model (types, find-usages)

Yes

Full code model

Yes

LSP

No

LSP

No

Reads dependency source

Yes

No

LSP

No

No

No

Auto-review of generated code

Yes

Via verify

/review

PR only

No

No

Context compression

Yes

No

Yes

No

No

Yes

Multi-IDE support

JB only

JB only

Yes

Yes

Yes

Yes

Pricing (all top models)

$15-200/mo

Credit-based

$20–200/mo

$20–60/mo

$10–39/mo

BYOK

What IDE-native AI feels like

What impressed me most is how well the agent understands the existing project. Its plans fit naturally into what is already built, even when I am working outside my usual tech stack.

Mariya Remenyuk
Mariya Remenyuk

Senior Analyst Developer · DXC Technology

LSP gives an agent coordinates; the full IDE gives it the project model. That native IDE context makes all the difference on real Java code.

Akiner Alkan
Akiner Alkan

Software Architect & AI Board Lead · Siemens

IDE-native stepping makes the difference on stateful Java applications.

Masaood
Masaood

Software Engineer

Webinar: Working with AI Tools at the User Level

Methodology, SDD + TDD, feedback loops, and subagents — a practical framework for getting predictable results from AI coding agents. For senior Java developers and team leads using JetBrains IDEs.

Explyt 5.20

Explyt 5.20: stop waiting in the chat — a background task panel and notifications outside the IDE

Frequently Asked Questions

Getting Started

IDE Integration & Workflow

How Explyt Compares

Models & BYOK

Pricing & Billing

Privacy & Security