Dynamics 365 Finance & Operations MCP Server

Search for D365 F&O data entities using simple keyword-based search.

IMPORTANT: When a user asks for something like "Get data management entities" or "Find customer group entities", break the request into individual keywords and perform MULTIPLE searches, then analyze all results:

1. Extract individual keywords from the request (e.g. "data management entities" → "data", "management", "entities")

2. Perform separate searches for each significant keyword using simple text matching

3. Combine and analyze results from all searches

4. Look for entities that match the combination of concepts

SEARCH STRATEGY EXAMPLES:

• "data management entities" → Search for "data", then "management", then find entities matching both concepts

• "customer groups" → Search for "customer", then "group", then find intersection

• "sales orders" → Search for "sales", then "order", then combine results

Use simple keywords, not complex patterns. The search will find entities containing those keywords.

Args: pattern: Simple keyword or text to search for in entity names. Use plain text keywords, not regex patterns. For multi-word requests like 'data management entities': 1) Break into keywords: 'data', 'management' 2) Search for each keyword separately: 'data' then 'management' 3) Run separate searches for each keyword 4) Analyze combined results. Examples: use 'customer' to find customer entities, 'group' to find group entities. entity_category: Filter entities by their functional category (e.g., Master, Transaction). data_service_enabled: Filter entities that are enabled for OData API access (e.g., for querying). data_management_enabled: Filter entities that can be used with the Data Management Framework (DMF). is_read_only: Filter entities based on whether they are read-only or support write operations. limit: Maximum number of matching entities to return. Use smaller values (10-50) for initial exploration, larger values (100-500) for comprehensive searches. profile: Configuration profile to use (optional - uses default profile if not specified)

Returns: Dictionary with matching entities