Bridges JetBrains IDE tools and features to MCP-compatible clients, enabling interaction with the IDE environment and tools via the Model Context Protocol.
Allows MCP clients to interact with PyCharm's IDE tools and features, facilitating AI-driven development within the Python-focused IDE.
Allows MCP clients to interact with WebStorm's IDE tools and features, facilitating AI-driven development within the web-focused IDE.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@JetBrains MCP Bridge run the unit tests for the AuthController in IntelliJ"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Bridge MCP permettant d'utiliser les outils JetBrains IDE depuis Cascade (Windsurf) ou tout autre client MCP.
┌─────────────────┐ ┌──────────────────┐ ┌─────────────────┐
│ Cascade/ │────▶│ MCP Bridge │────▶│ JetBrains IDE │
│ Windsurf │ │ (stdio) │ │ (SSE :64342) │
│ │◀────│ │◀────│ │
└─────────────────┘ └──────────────────┘ └─────────────────┘Related MCP server: JetBrains MCP Proxy Server
JetBrains IDE (IntelliJ, WebStorm, PyCharm, etc.) avec le plugin MCP activé
Node.js >= 18
Windsurf avec Cascade
npm install
npm run build:mcpAjoutez cette configuration dans les paramètres MCP de Windsurf (~/.codeium/windsurf/mcp_config.json) :
{
"mcpServers": {
"jetbrains": {
"command": "node",
"args": ["C:/Users/chris/IdeaProjects/test/dist/mcp-server.js"],
"env": {
"JETBRAINS_MCP_HOST": "127.0.0.1",
"JETBRAINS_MCP_PORT": "64342"
}
}
}
}Note: Adaptez le chemin
argsselon l'emplacement de votre projet.
Ouvrez votre IDE JetBrains avec un projet
Vérifiez que le proxy MCP est actif (port 64342 par défaut)
Redémarrez Windsurf pour charger la configuration MCP
Utilisez Cascade - les outils JetBrains seront disponibles
Variable | Défaut | Description |
|
| Hôte du proxy MCP JetBrains |
|
| Port du proxy MCP JetBrains |
npm run start:mcpUne interface React est également disponible pour tester la connexion :
npm run devOuvrez http://localhost:5173 pour voir les outils MCP disponibles.
This template provides a minimal setup to get React working in Vite with HMR and some ESLint rules.
Currently, two official plugins are available:
@vitejs/plugin-react uses Babel (or oxc when used in rolldown-vite) for Fast Refresh
@vitejs/plugin-react-swc uses SWC for Fast Refresh
The React Compiler is not enabled on this template because of its impact on dev & build performances. To add it, see this documentation.
If you are developing a production application, we recommend updating the configuration to enable type-aware lint rules:
export default defineConfig([
globalIgnores(['dist']),
{
files: ['**/*.{ts,tsx}'],
extends: [
// Other configs...
// Remove tseslint.configs.recommended and replace with this
tseslint.configs.recommendedTypeChecked,
// Alternatively, use this for stricter rules
tseslint.configs.strictTypeChecked,
// Optionally, add this for stylistic rules
tseslint.configs.stylisticTypeChecked,
// Other configs...
],
languageOptions: {
parserOptions: {
project: ['./tsconfig.node.json', './tsconfig.app.json'],
tsconfigRootDir: import.meta.dirname,
},
// other options...
},
},
])You can also install eslint-plugin-react-x and eslint-plugin-react-dom for React-specific lint rules:
// eslint.config.js
import reactX from 'eslint-plugin-react-x'
import reactDom from 'eslint-plugin-react-dom'
export default defineConfig([
globalIgnores(['dist']),
{
files: ['**/*.{ts,tsx}'],
extends: [
// Other configs...
// Enable lint rules for React
reactX.configs['recommended-typescript'],
// Enable lint rules for React DOM
reactDom.configs.recommended,
],
languageOptions: {
parserOptions: {
project: ['./tsconfig.node.json', './tsconfig.app.json'],
tsconfigRootDir: import.meta.dirname,
},
// other options...
},
},
])This server cannot be installed
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
MCP server for AI access to SmartBear tools, including BugSnag, Reflect, Swagger, PactFlow, QTM4J.
The MCP server for Azure DevOps, bringing the power of Azure DevOps directly to your agents.
MCP server exposing the Backtest360 engine API as tools for AI agents.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/CodeCraftingDevelopment/CodeCraftingDevelopment-mcp-jetbrain'
If you have feedback or need assistance with the MCP directory API, please join our Discord server