Dynamics 365 Table Relationship Explorer CLI and MCP

Created By
duggurda year ago
CLI tool and MCP server for finding and exploring Dynamics 365/Axapta table relationships
Overview

What is Dynamics 365 Table Relationship Explorer?

Dynamics 365 Table Relationship Explorer is a CLI tool and MCP server designed for finding and exploring table relationships in Dynamics 365/Axapta.

How to use Dynamics 365 Table Relationship Explorer?

To use the tool, install the core package or MCP package, and utilize the command-line interface to find related tables, relationship paths, and optimize relationship files.

Key features of Dynamics 365 Table Relationship Explorer?

  • Find directly related tables in a case-insensitive manner.
  • Discover relationship paths between tables with configurable levels of intermediate tables.
  • Retrieve detailed relationship information and statistics.
  • Optimize relationship files for better performance.
  • Integrate with AI assistants through the MCP server.

Use cases of Dynamics 365 Table Relationship Explorer?

  1. Analyzing data relationships in Dynamics 365 for better data management.
  2. Assisting developers in understanding table connections for application development.
  3. Enhancing AI assistant capabilities by providing relationship data through MCP integration.

FAQ from Dynamics 365 Table Relationship Explorer?

  • Can I use this tool for any version of Dynamics 365?

Yes, it is designed to work with Dynamics 365/Axapta.

  • Is there a graphical interface available?

No, this tool is CLI-based, but it can be integrated with AI assistants for enhanced usability.

  • How do I install the packages?

You can install the core and MCP packages using the provided commands in the documentation.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
duggurd
Star
0
Language
Python
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago