During Tool Execution:

• Shows the tool name (e.g., MCP: update_database)
• Shows the elapsed time in MM:SS format
• Click to access the 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. The 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 the 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 the agent to retry
• Want to switch the agent's focus to a different task

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, you can add 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"
    }
  }
}

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 the cursor after the dot (.) for method/property suggestions.
3. Pagination: Use offset to get the 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 the dot (e.g. Structure.Insert, Array.Add)
   • Object properties and fields
   • Configuration objects and modules

Validation Tools

• clean_project: Refreshes the 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 the 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 the error location (objectPresentation)
• FQN examples:
  • Document.SalesOrder - all errors in the document
  • Catalog.Products - all errors in the catalog
  • CommonModule.MyModule - all errors in the common module
  • Document.SalesOrder.Form.ItemForm - errors in the 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 a list of metadata objects from the 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 a 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 a list of all tags defined in the project. Tags are user-defined labels for organizing metadata objects.

Parameters:

Returns: Markdown table with the 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 the total objects found

Application Management Tools

Get Applications Tool

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

Parameters:

Update Database Tool

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

Parameters:

Debug Launch Tool

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

Parameters:

Notes:

• Requires a launch configuration to be created in EDT first (Run → Run Configurations...)
• If no configuration exists, returns a list of available configurations
• updateBeforeLaunch=true skips the update if the 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 the module path, type, and parent object.

Parameters:

Get Module Structure Tool

get_module_structure: Get the 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 an EDT project. Returns the source with line numbers. Supports reading the 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 the entire file), append (add to the 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 a 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 the method source code with line numbers and signature. If the method is not found, returns a 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 the method call hierarchy: who calls this method (callers) or what this method calls (callees). Uses semantic BSL analysis via the BM-index, not text search.

Parameters:

Notes:

• Requires the 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 the 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 the editor.

Use cases:

• Determine the inferred type of a variable (BSL is dynamically typed).
• Get the 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 an 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.