odatav4-mcp
An MCP server for OData v4 endpoints, especially Microsoft Dataverse/Dynamics 365, enabling authentication, schema discovery, querying, CRUD, and more via natural language.
README
odatav4-mcp
An MCP (Model Context Protocol) server for OData v4 endpoints, tuned for Microsoft Dataverse / Dynamics 365 but usable with any OData v4 service.
- Zero-registration auth: signs in with Entra ID using the well-known
Microsoft public client (
51f81489-12ee-4a9e-aac9-25749fb2a1de, the same app XrmToolBox and the Dataverse samples use). The default flow opens your browser with a localhost redirect (works where Conditional Access blocks device-code flow); device-code flow is available for headless/SSH sessions. MFA works; tokens are cached on disk so you sign in once, not per session. - One config value: just the endpoint URL.
- Full OData surface: metadata discovery, queries ($filter/$select/$expand/ $apply/$count), paging, CRUD, associations, functions/actions, and a raw request escape hatch.
Install
git clone <this-repo> odatav4-mcp
cd odatav4-mcp
npm install # also compiles TypeScript (prepare script)
Optional but recommended — sign in once from a terminal so the MCP client never has to relay sign-in instructions:
ODATA_URL=https://yourorg.crm.dynamics.com npm run login
# headless / SSH (no local browser):
ODATA_URL=https://yourorg.crm.dynamics.com npm run login -- --devicecode
Configuration
| Env var | Required | Description |
|---|---|---|
ODATA_URL |
yes | Service root. A bare Dataverse org URL (https://yourorg.crm.dynamics.com) is expanded to /api/data/v9.2/ automatically. |
ODATA_TENANT |
no | Tenant id or domain (default organizations). Set this if your account exists in multiple tenants. |
ODATA_CLIENT_ID |
no | Override the Entra app id (default: the well-known Dataverse dev-tools client). |
ODATA_LOGIN_FLOW |
no | interactive (default: opens a browser, localhost redirect) or devicecode (enter a code at microsoft.com/devicelogin — for headless/SSH, or if your tenant blocks the browser flow). |
ODATA_AUTH |
no | Set to none for anonymous OData services (e.g. public test services). |
ODATA_CACHE_DIR |
no | Where tokens and $metadata are cached (default ~/.config/odatav4-mcp/<host>). |
Hook up to your client
Use the absolute path to dist/index.js in all cases.
GitHub Copilot (VS Code)
Create .vscode/mcp.json in your workspace (or add via MCP: Add Server):
{
"servers": {
"dataverse": {
"type": "stdio",
"command": "node",
"args": ["/path/to/odatav4-mcp/dist/index.js"],
"env": { "ODATA_URL": "https://yourorg.crm.dynamics.com" }
}
}
}
Claude Code
claude mcp add dataverse --env ODATA_URL=https://yourorg.crm.dynamics.com -- node /path/to/odatav4-mcp/dist/index.js
Codex CLI
In ~/.codex/config.toml:
[mcp_servers.dataverse]
command = "node"
args = ["/path/to/odatav4-mcp/dist/index.js"]
env = { ODATA_URL = "https://yourorg.crm.dynamics.com" }
Tools
| Tool | Purpose |
|---|---|
login, auth_status, logout |
Device-code sign-in and token management |
service_info, whoami |
Connection status; Dataverse WhoAmI |
list_entity_sets, describe_entity, list_operations |
Schema discovery from $metadata (cached 6h) |
query, next_page, get_record |
Reads with full OData query options and paging |
create_record, update_record, delete_record |
CRUD (update sends If-Match: * to prevent accidental upserts) |
associate_records, disassociate_records |
N:N / collection navigation $ref operations |
call_function, call_action |
OData functions (GET) and actions (POST), bound or unbound — covers Dataverse messages and custom APIs |
raw_request |
Any other request, restricted to the configured host |
Notes
- Auth flow: silent token refresh from the on-disk MSAL cache first; if that
fails, tools return an instruction to run the
logintool. By default that opens your system browser (on WSL it launches the Windows browser viawslvieworrundll32.exe) and completes through a localhost redirect; MSAL runs the loopback listener automatically. Thelogintool accepts{"flow": "devicecode"}to switch flows per call. Both flows are attempted against the same well-known client id, which hashttp://localhostregistered as a redirect URI. - The token cache (
msal-cache.json) contains refresh tokens; it is written with mode 600 into your home config directory. Delete it (or uselogout) to revoke local access. - Dataverse
$metadatais large (10 MB+); it is cached on disk for 6 hours. Passrefresh: truetolist_entity_setsto force a re-download.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
Neon Database
MCP server for interacting with Neon Management API and databases
E2B
Using MCP to run code via e2b.
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.