Dynamics 365 Finance & Operations MCP Server

Search for available OData actions in D365 F&O using simple keyword-based search.

IMPORTANT: When searching for actions, break down user requests into individual keywords and perform MULTIPLE searches:

1. Extract keywords from requests (e.g., "posting actions" → "post", "posting")

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

3. Combine and analyze results from all searches

4. Look for actions that match the combination of concepts

SEARCH STRATEGY EXAMPLES:

• "posting actions" → Search for "post", then look for posting-related actions

• "validation functions" → Search for "valid" and "check", then find validation actions

• "workflow actions" → Search for "workflow" and "approve", then combine results

Use simple keywords, not complex patterns. Actions are operations that can be performed on entities or globally.

Args: pattern: Simple keyword or text to search for in action names. Use plain text keywords, not regex patterns. For requests like 'posting actions': 1) Extract keywords: 'post', 'posting' 2) Search for each keyword: 'post' 3) Perform multiple searches for related terms 4) Analyze combined results. Use simple text matching. entityName: Optional. Filter actions that are bound to a specific data entity (e.g., 'CustomersV3'). bindingKind: Optional. Filter by binding type: 'Unbound' (can call directly), 'BoundToEntitySet' (operates on entity collections), 'BoundToEntityInstance' (requires specific entity key). isFunction: Optional. Filter by type: 'true' for functions (read-only), 'false' for actions (may have side-effects). Note: This filter may not be fully supported yet. limit: Maximum number of matching actions to return. profile: Configuration profile to use (optional - uses default profile if not specified)

Returns: Dictionary with matching actions