MCP Overview
What DMTR MCP is for and how it connects LLMs to private market data.
Overview
DMTR MCP is a Model Context Protocol server that exposes DMTR's private market infrastructure to large language models (LLMs). The deployed server exposes the energy toolset; a general registry toolset (positions, transfers, inventory, reports) is planned. The MCP server translates LLM tool calls into DMTR API requests and returns structured data for the model to reason over.
What is MCP
The Model Context Protocol (MCP) is an open standard for connecting LLMs to external data sources and tools. MCP defines three primitives: resources (read-only data identified by URIs), tools (functions the LLM can invoke), and prompts (pre-built templates for common tasks). DMTR implements all three, giving LLMs full access to registry, transfer, and lifecycle capabilities.
Why DMTR + MCP
Private market data is fragmented across spreadsheets, cap tables, and proprietary systems. DMTR unifies this into a single registry. MCP makes that registry accessible to AI assistants, so users can ask "What positions do I have in SPV LLC?" or "Can participant X buy position Y?" without writing code. The combination enables AI copilots for portfolio review, transfer feasibility, compliance checks, and reporting.
Architecture summary
The DMTR MCP server runs as a process that your LLM client connects to (stdio or HTTP). The server authenticates to DMTR using your API key, exposes tools and resources, and forwards LLM requests to the DMTR API. Responses are returned to the LLM for natural language synthesis. The server is stateless; all state lives in DMTR.
Key capabilities
- Resources: Position, portfolio, participant, and lifecycle event data via URI schemes (
position://,portfolio://, etc.). - Tools (shipped): the energy toolset — slot inventory, demand submission/compliance, regulatory-corpus inspection, capacity-payment preview, and chip-SKU lookup. See energy tools.
- Tools (planned): a general registry toolset — query registry, evaluate transfer feasibility, surface inventory, express intent, generate reports — designed but not yet deployed.
- Prompts: Pre-built templates for portfolio review, transfer feasibility, and compliance checks.
Getting started
Install the DMTR MCP server, add it to your MCP client (Claude Desktop, Cursor, or custom), and configure your DMTR API key. See the Quickstart for a 5-minute setup. For full reference, explore Tools, Resources, and Prompts.