EDT MCP Server

MCP (Model Context Protocol) server plugin for 1C:EDT, enabling AI assistants (Claude, GitHub Copilot, Cursor, etc.) to interact with EDT workspace.

[!IMPORTANT]
EDT version compatibility:
EDT 2025.x is supported up to and including plugin version 1.26.1.
Starting from plugin version 1.27.0, only EDT 2026.1+ is supported.

Features

• 🔧 MCP Protocol 2025-11-25 - Streamable HTTP transport with SSE support
• 📊 Project Information - List workspace projects and configuration properties
• 🔴 Error Reporting - Get errors, warnings, problem summaries with filters
• 📝 Check Descriptions - Get check documentation from markdown files
• 🔄 Project Revalidation - Trigger revalidation when validation gets stuck
• 🔖 Bookmarks & Tasks - Access bookmarks and TODO/FIXME markers
• 💡 Content Assist - Get type info, method hints and platform documentation at any code position
• 🧪 Query Validation - Validate 1C query text in project context (syntax + semantic errors, optional DCS mode)
• 🧩 BSL Code Analysis - Browse modules, inspect structure, read/write methods, search code, and analyze call hierarchy
• 🖼️ Form Screenshot Capture - Get PNG screenshots from the form WYSIWYG editor for visual inspection
• 🚀 Application Management - Get applications, update database, launch in debug mode
• 🎯 Status Bar - Real-time server status with tool name, execution time, and interactive controls
• ⚡ Interruptible Operations - Cancel long-running operations and send signals to AI agent
• 🏷️ Metadata Tags - Organize objects with custom tags, filter Navigator, keyboard shortcuts (Ctrl+Alt+1-0), multiselect support
• 📁 Metadata Groups - Create custom folder hierarchy in Navigator tree per metadata collection
• ✏️ Metadata Refactoring - Rename/delete metadata objects with full cascading updates across BSL code, forms and metadata; add new attributes to existing objects

Installation

Only EDT 2026.1+ (for plugin v1.27.0+; use plugin v1.26.1 for EDT 2025.x)

From Update Site

1. In EDT: Help → Install New Software...
2. Add update site URL: https://ditrixnew.github.io/EDT-MCP/
3. Select EDT MCP Server Feature
4. Restart EDT

From Windows command line - "one shot" very fast install

Close your EDT (!) and run:

rem Here  "%VER_EDT% = 2025.2.3+30"  just for example - please, set YOUR actual version !
set VER_EDT=2025.2.3+30

"\your\path\to\EDT\components\1c-edt-%VER_EDT%-x86_64\1cedt.exe" -nosplash ^
    -application org.eclipse.equinox.p2.director ^
    -repository https://ditrixnew.github.io/EDT-MCP/ ^
	-installIU com.ditrix.edt.mcp.server.feature.feature.group ^
	-profileProperties org.eclipse.update.reconcile=true

Installation Result

After that, EDT will automatically monitor the update site and install available updates when detected.

As well, we can also manually check via Help → About → Installation Details → Select MCP → Update

Configuration

Go to Window → Preferences → MCP Server:

• Server Port: HTTP port (default: 8765)
• Check descriptions folder: Path to check description markdown files
• Auto-start: Start server on EDT launch
• Default result limit: Default number of results returned by tools (default: 100)
• Maximum result limit: Maximum number of results that can be requested (default: 1000)
• Plain text mode (Cursor compatibility): Returns results as plain text instead of embedded resources (for AI clients that don't support MCP resources)
• Show tags in Navigator: Display tags as decorations in the Navigator tree
• Tag decoration style: How tags are displayed — all tags as suffix, first tag only, or tag count

Status Bar Controls

The MCP server status bar shows real-time execution status with interactive controls.

Status Indicator:

• 🟢 Green - Server running, idle
• 🟡 Yellow blinking - Tool is executing
• ⚪ Grey - Server stopped

During Tool Execution:

• Shows tool name (e.g., MCP: update_database)
• Shows elapsed time in MM:SS format
• Click to access control menu

When a tool is executing, you can send signals to the AI agent to interrupt the MCP call:

How it works:

1. When you click a button, a dialog appears showing the message that will be sent to the agent
2. You can edit the message before sending
3. The MCP call is immediately interrupted and returns control to the agent
4. The EDT operation continues running in the background
5. Agent receives a response like:

USER SIGNAL: Your message here

Signal Type: CANCEL
Tool: update_database
Elapsed: 20s

Note: The EDT operation may still be running in background.

Use cases:

• Long-running operations (full database update, project validation) blocking the agent
• Need to give the agent additional instructions
• EDT showed an error dialog and you want agent to retry
• Want to switch agent's focus to a different task

Connecting AI Assistants

VS Code / GitHub Copilot

Create .vscode/mcp.json:

{
  "servers": {
    "EDT MCP Server": {
      "type": "sse",
      "url": "http://localhost:8765/mcp"
    }
  }
}

Cursor IDE

Note: Cursor doesn't support MCP embedded resources. Enable "Plain text mode (Cursor compatibility)" in EDT preferences: Window → Preferences → MCP Server.

Create .cursor/mcp.json:

{
  "mcpServers": {
    "EDT MCP Server": {
      "url": "http://localhost:8765/mcp"
    }
  }
}

Claude Code

Note: By editing the file .claude.json can be added to the MCP either to a specific project or to any project (at the root). If there is no mcpServers section, add it.

Add to .claude.json (in Windows %USERPROFILE%\.claude.json):

"mcpServers": {
  "EDT MCP Server": {
    "type": "http",
    "url": "http://localhost:8765/mcp"
  }
}

Claude Desktop

Add to claude_desktop_config.json:

{
  "mcpServers": {
    "EDT MCP Server": {
      "url": "http://localhost:8765/mcp"
    }
  }
}

Cline - extension for VSCode.

{
  "mcpServers": {
    "EDTMCPServer": {
      "type": "streamableHttp",
      "url": "http://localhost:8765/mcp"
    }
  }
}

Available Tools

Content Assist Tool

get_content_assist - Get content assist proposals at a specific position in BSL code. Returns type information, available methods, properties, and platform documentation.

Parameters:

Important Notes:

1. Save the file first - EDT must read the current content from disk to provide accurate proposals
2. Column position - Place cursor after the dot (.) for method/property suggestions
3. Pagination - Use offset to get next batch of proposals (e.g., first call with limit=5, second call with offset=5, limit=5)
4. Filtering - Use contains to filter by method/property name (case-insensitive)
5. Works for:
   • Global platform methods (e.g. NStr(, Format()
   • Methods after dot (e.g. Structure.Insert, Array.Add)
   • Object properties and fields
   • Configuration objects and modules

Validation Tools

• clean_project: Refreshes project from disk, clears all validation markers, and triggers full revalidation using EDT's ICheckScheduler
• revalidate_objects: Revalidates specific metadata objects by their FQN:
  • Document.MyDocument, Catalog.MyCatalog, CommonModule.MyModule
  • Document.MyDoc.Form.MyForm for nested objects
• validate_query: Validates query language text in project context and returns syntax/semantic errors.
  • Parameters: projectName (required), queryText (required), dcsMode (optional, default false)
  • Use dcsMode=true for Data Composition System (DCS) queries

Project Errors Tool

get_project_errors - Get detailed configuration problems from EDT with multiple filter options.

Parameters:

Objects filter format:

• Array of FQN strings: ["Document.SalesOrder", "Catalog.Products"]
• Case-insensitive partial matching
• Matches against error location (objectPresentation)
• FQN examples:
  • Document.SalesOrder - all errors in document
  • Catalog.Products - all errors in catalog
  • CommonModule.MyModule - all errors in common module
  • Document.SalesOrder.Form.ItemForm - errors in specific form

Platform Documentation Tool

get_platform_documentation - Get documentation for platform types (ValueTable, Array, Structure, Query, etc.) and built-in functions (FindFiles, Message, Format, etc.)

Parameters:

Metadata Objects Tool

get_metadata_objects - Get list of metadata objects from 1C configuration.

Parameters:

Metadata Details Tool

get_metadata_details - Get detailed properties of metadata objects.

Parameters:

Find References Tool

find_references - Find all references to a metadata object. Returns all places where the object is used: in other metadata objects, BSL code, forms, roles, subsystems, etc. Matches EDT's built-in "Find References" functionality.

Parameters:

Returns markdown with references in EDT-compatible format:

# References to Catalog.Items

**Total references found:** 122

- Catalog.ItemKeys - Attributes.Item.Type - Type: types
- Catalog.ItemKeys.Form.ChoiceForm.Form - Items.List.Item.Data path - Type: types
- Catalog.Items - Attributes.PackageUnit.Choice parameter links - Ref
- Catalog.Items.Form.ItemForm.Form - Items.GroupTop.GroupMainAttributes.Code.Data path - Type: types
- CommonAttribute.Author - Content - metadata
- Configuration - Catalogs - catalogs
- DefinedType.typeItem - Type - Type: types
- EventSubscription.BeforeWrite_CatalogsLockDataModification - Source - Type: types
- Role.FullAccess.Rights - Role rights - object
- Subsystem.Settings.Subsystem.Items - Content - content

### BSL Modules

- CommonModules/GetItemInfo/Module.bsl [Line 199; Line 369; Line 520]
- Catalogs/Items/Forms/ListForm/Module.bsl [Line 18; Line 19]

Reference types included:

• Metadata references - Attributes, form items, command parameters, type descriptions
• Type usages - DefinedTypes, ChartOfCharacteristicTypes, type compositions
• Common attributes - Objects included in common attribute content
• Event subscriptions - Source objects for subscriptions
• Roles - Objects with role permissions
• Subsystems - Subsystem content
• BSL code - References in BSL modules with line numbers

Note: find_references supports top-level metadata objects only (e.g. Catalog.DataAreas, CommonModule.Saas). Passing a sub-object FQN such as Catalog.DataAreas.Attribute.DataAreaStatus returns a descriptive error indicating that sub-objects are not supported. Use rename_metadata_object or delete_metadata_object to work with attributes and nested objects.

Metadata Refactoring Tools

Rename Metadata Object Tool

rename_metadata_object - Rename a metadata object or attribute with full refactoring support. All references in BSL code, forms, and metadata are updated automatically.

Workflow:

1. Call without confirm to preview all change points
2. Review change point indices and optionally skip some with disableIndices
3. Call with confirm=true to apply

Parameters:

Supported child types in FQN: Attribute, TabularSection, Dimension, Resource

Delete Metadata Object Tool

delete_metadata_object - Delete a metadata object or attribute. References in BSL code, forms, and other metadata are cleaned up automatically.

Workflow:

1. Call without confirm to preview affected references and problems
2. Call with confirm=true to apply

Parameters:

Add Metadata Attribute Tool

add_metadata_attribute - Add a new attribute to a metadata object via BM write transaction. The attribute is created with default properties.

Parameters:

Supported parent types: Catalog, Document, ExchangePlan, ChartOfCharacteristicTypes, ChartOfAccounts, ChartOfCalculationTypes, BusinessProcess, Task, DataProcessor, Report, InformationRegister, AccumulationRegister, AccountingRegister

Tag Management Tools

Get Tags Tool

get_tags - Get list of all tags defined in the project. Tags are user-defined labels for organizing metadata objects.

Parameters:

Returns: Markdown table with tag name, color, description, and number of assigned objects.

Get Objects By Tags Tool

get_objects_by_tags - Get metadata objects filtered by tags. Returns objects that have any of the specified tags.

Parameters:

Returns: Markdown with sections for each tag including:

• Tag color and description
• Table of object FQNs assigned to the tag
• Summary with total objects found

Application Management Tools

Get Applications Tool

get_applications - Get list of applications (infobases) for a project. Returns application ID, name, type, and current update state. Use this to get application IDs for update_database and debug_launch tools.

Parameters:

Update Database Tool

update_database - Update database (infobase) configuration. Supports full and incremental update modes.

Parameters:

Debug Launch Tool

debug_launch - Launch application in debug mode. Automatically updates database before launching and finds existing launch configuration.

Parameters:

Notes:

• Requires a launch configuration to be created in EDT first (Run → Run Configurations...)
• If no configuration exists, returns list of available configurations
• updateBeforeLaunch=true skips update if database is already up to date

BSL Code Analysis Tools

List Modules Tool

list_modules - List all BSL modules in an EDT project. Can filter by metadata type or specific object name. Returns module path, type, and parent object.

Parameters:

Get Module Structure Tool

get_module_structure - Get structure of a BSL module: all procedures/functions with signatures, line numbers, regions, execution context (&AtServer, &AtClient), export flag, and parameters.

Parameters:

Returns: Markdown with:

• Module summary (procedure/function counts, total lines)
• Regions list with line ranges
• Methods table: type, name, export, context, lines, parameters, region, description (when includeComments=true)
• Variables table: name, export flag, line, region (when includeVariables=true)

Read Module Source Tool

read_module_source - Read BSL module source code from EDT project. Returns source with line numbers. Supports reading full file or a specific line range. Max 5000 lines per call.

Parameters:

Write Module Source Tool

write_module_source - Write BSL source code to 1C metadata object modules. Modes: searchReplace (content-based find and replace, default), replace (replace entire file), append (add to end). Specify modulePath or objectName + moduleType. Automatically checks BSL syntax before writing.

Parameters:

*One of modulePath or objectName is required.

**Required for searchReplace mode.

Notes:

• Content-based editing: searchReplace mode finds oldSource in the file and replaces it with source. If oldSource is not found or matches multiple locations, the operation fails safely. This eliminates line-number drift issues when making multiple edits
• Creates new module file if it does not exist (only in replace mode)
• Preserves UTF-8 BOM encoding
• Syntax check validates the complete resulting file, not just the inserted fragment

Read Method Source Tool

read_method_source - Read a specific procedure/function from a BSL module by name. Returns method source code with line numbers and signature. If method not found, returns list of all available methods.

Parameters:

Returns: Method source code with:

• Method type (Procedure/Function), signature, export flag
• Line range and line count
• Source code with line numbers

Search in Code Tool

search_in_code - Full-text search across all BSL modules in a project. Supports plain text and regex patterns, case sensitivity, context lines around matches, and file path filtering.

Parameters:

Get Method Call Hierarchy Tool

get_method_call_hierarchy - Find method call hierarchy: who calls this method (callers) or what this method calls (callees). Uses semantic BSL analysis via BM-index, not text search.

Parameters:

Notes:

• Requires EMF model (BSL AST) — does not work in text fallback mode
• callers uses IReferenceFinder to search across the entire project
• callees traverses the method's AST to find all invocations

Go To Definition Tool

go_to_definition - Navigate to the definition of a symbol. Resolves method calls like CommonModuleName.MethodName to the actual definition with source code, signature, and location. Also resolves metadata object FQNs like Catalog.Products. Supports both English and Russian metadata type names.

Parameters:

Returns: Markdown with:

• Method signature, export flag, line range
• Source code with line numbers (when includeSource=true)
• File path for navigation
• For metadata objects: FQN, synonym, available modules

Get Symbol Info Tool

get_symbol_info - Get type and hover information about a symbol at a specific position in a BSL module. Returns inferred types, signatures, and documentation — the same info that EDT shows on mouse hover. Useful for understanding variable types in dynamically-typed BSL code.

Parameters:

Returns: Markdown with symbol information. Uses a multi-level approach:

1. Editor hover (best): Returns inferred types, method signatures, documentation — same as IDE hover tooltip
2. EObject analysis (fallback): Returns structural info — symbol kind, name, signature, export flag, line range
3. EMF model (last resort): Basic node info without opening editor

Use cases:

• Determine the inferred type of a variable (BSL is dynamically typed)
• Get method signature and documentation at a call site
• Inspect property types on objects accessed via dot notation
• Understand platform method parameter types

Output Formats

• Markdown tools: list_projects, get_project_errors, get_bookmarks, get_tasks, get_problem_summary, get_check_description - return Markdown as EmbeddedResource with mimeType: text/markdown
• JSON tools: get_configuration_properties, clean_project, revalidate_objects - return JSON with structuredContent
• Text tools: get_edt_version - return plain text

API Endpoints

Metadata Tags

Organize your metadata objects with custom tags for easier navigation and filtering.

Why Use Tags?

Tags help you:

• Group related objects across different metadata types (e.g., all objects for a specific feature)
• Quickly find objects in large configurations
• Filter the Navigator to focus on specific areas of the project
• Share object organization with your team via version control

Getting Started

Assigning Tags to Objects:

1. Right-click on any metadata object in the Navigator
2. Select Tags from the context menu
3. Check the tags you want to assign, or select Manage Tags... to create new ones

Managing Tags:

In the Manage Tags dialog you can:

• Create new tags with custom names, colors, and descriptions
• Edit existing tags (name, color, description)
• Delete tags
• See all available tags for the project

Viewing Tags in Navigator

Tagged objects show their tags as a suffix in the Navigator tree:

To enable/disable tag display:

• Window → Preferences → General → Appearance → Label Decorations
• Toggle "Metadata Tags Decorator"

Filtering Navigator by Tags

Filter the entire Navigator to show only objects with specific tags:

1. Click the tag filter button in the Navigator toolbar (or right-click → Tags → Filter by Tag...)
2. Select one or more tags
3. Click Set to apply the filter

The Navigator will show only:

• Objects that have ANY of the selected tags
• Parent folders containing matching objects

To clear the filter: Click Turn Off in the dialog or use the toolbar button again.

Keyboard Shortcuts for Tags

Quickly toggle tags on selected objects using keyboard shortcuts:

Features:

• Works with multiple selected objects
• Supports cross-project selection (each object uses tags from its own project)
• Pressing the same shortcut again removes the tag (toggle behavior)
• Tag order is configurable in the Manage Tags dialog (Move Up/Move Down buttons)

To customize shortcuts: Window → Preferences → General → Keys → search for "Toggle Tag"

Filtering Untagged Objects

Find metadata objects that haven't been tagged yet:

1. Open Filter by Tag dialog (toolbar button or Tags → Filter by Tag...)
2. Check the "Show untagged objects only" checkbox
3. Click Set

The Navigator will show only objects that have no tags assigned, making it easy to identify objects that need categorization.

Multi-Select Tag Assignment

Assign or remove tags from multiple objects at once:

1. Select multiple objects in the Navigator (Ctrl+Click or Shift+Click)
2. Right-click → Tags
3. Select a tag to toggle it on/off for ALL selected objects

Behavior:

• ✓ Checked = all selected objects have this tag
• ☐ Unchecked = none of the selected objects have this tag
• When objects are from different projects, only objects from projects that have the tag will be affected

Tag Filter View

For advanced filtering across multiple projects, use the Tag Filter View:

Window → Show View → Other → MCP Server → Tag Filter

This view provides:

• Left panel: Select tags from all projects in your workspace
• Right panel: See all matching objects with search and navigation
• Search: Filter results by object name using regex
• Double-click: Navigate directly to the object

Where Tags Are Stored

Tags are stored in .settings/metadata-tags.yaml file in each project. This file:

• Can be committed to version control (VCS friendly)
• Is automatically updated when you rename or delete objects
• Uses YAML format for easy readability

Example:

assignments:
  CommonModule.Utils:
    - Utils
  Document.SalesOrder:
    - Important
    - Sales
tags:
  - color: '#FF0000'
    description: Critical business logic
    name: Important
  - color: '#00FF00'
    description: ''
    name: Utils
  - color: '#0066FF'
    description: Sales department documents
    name: Sales

Metadata Groups

Organize your Navigator tree with custom groups to create a logical folder structure for metadata objects.

Why Use Groups?

Groups help you:

• Create custom folder hierarchy in the Navigator tree
• Organize objects by business area, feature, or any logical structure
• Navigate large configurations faster with nested groups
• Separate grouped objects from ungrouped ones

Getting Started

Creating a Group:

1. Right-click on any metadata folder (e.g., Catalogs, Common modules) in the Navigator
2. Select New Group... from the context menu
3. Enter the group name and optional description
4. Click OK to create the group

Create Group Dialog:

Adding Objects to a Group:

1. Right-click on any metadata object in the Navigator
2. Select Add to Group...
3. Choose the target group from the list

Removing Objects from a Group:

1. Right-click on an object inside a group
2. Select Remove from Group

Viewing Groups in Navigator

Grouped objects appear inside their group folders in the Navigator tree:

Key Features:

• Groups are created per metadata collection (Catalogs, Common modules, Documents, etc.)
• Objects inside groups are still accessible via standard EDT navigation
• Ungrouped objects appear at the end of the list

Group Operations

Where Groups Are Stored

Groups are stored in .settings/groups.yaml file in each project. This file:

• Can be committed to version control (VCS friendly)
• Uses YAML format for easy readability
• Is automatically updated when you rename or delete objects

Example:

groups:
- name: "Products & Inventory"
  description: "Product and inventory catalogs"
  path: Catalog
  order: 0
  children:
    - Catalog.ItemKeys
    - Catalog.Items
    - Catalog.ItemSegments
    - Catalog.Units
    - Catalog.UnitsOfMeasurement
- name: "Organization"
  description: "Organization structure catalogs"
  path: Catalog
  order: 1
  children:
    - Catalog.Companies
    - Catalog.Stores
- name: "Core Functions"
  description: "Core shared functions used across the application"
  path: CommonModule
  order: 0
  children:
    - CommonModule.CommonFunctionsClient
    - CommonModule.CommonFunctionsServer
    - CommonModule.CommonFunctionsClientServer
- name: "Localization"
  description: "Multi-language support modules"
  path: CommonModule
  order: 1
  children:
    - CommonModule.Localization
    - CommonModule.LocalizationClient
    - CommonModule.LocalizationServer
    - CommonModule.LocalizationReuse

Requirements

• 1C:EDT 2025.2 (Ruby) or later
• Java 17+

License

Copyright (C) 2026 DitriX

Licensed under GNU AGPL v3.0