MCP support in Azure Data API Builder for exposing configured database entities as MCP tools, including entity discovery and DML operations over Azure databases and supported on-premises data stores.
Open the source and read safety notes before installing.
Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.
Decision playbook
Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.
0
63
—
No baseline selected
No major trust-signal divergence detected in the current selection.
Confirm ownership and provenance before trusting install instructions.
Source link availableRequired
Open the canonical repository and verify ownership.
Source provenance statusRequired
Marked as source-backed.
Metadata reviewed
No reviewed flag detected in metadata.
Validate risk disclosures before installation or API wiring.
Safety notes presentRequired
Review the listed safety guidance before running commands.
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
Trust level risk gateRequired
Trust level does not block evaluation.
Check package metadata and artifact integrity signals.
Install payload available
Install or copy payload is available for review.
Package verification flag
No package verification flag provided.
Checksum metadata
No checksum provided for downloaded artifact.
Use compare context to validate trade-offs before adoption.
Compare tray has multiple entries
Add at least one more entry to compare trust differences.
Baseline comparison available
No baseline peer selected yet.
Diverging trust signals identified
No major trust-signal divergence found.
Setup at a glance
Copy-ready — paste the snippet to get started.
Adoption plan
Current risk score 24/100. Use staged verification before broader rollout.
Validate source and review signals before any execution.
Confirm source provenanceRequired
Source URL/provenance metadata is present.
Confirm metadata review state
No review metadata found; increase manual validation.
Verify install payload
Install/config payload exists and can be inspected.
Confirm safety, privacy, and package integrity signals.
Review safety notesRequired
Safety notes are present.
Review privacy notesRequired
Privacy notes are present.
Verify package integrity metadata
No package verification/checksum metadata.
Adopt in controlled steps based on the selected plan.
Run in isolated sandbox firstRequired
Use a constrained sandbox and observe behavior across multiple tasks.
Roll out graduallyRequired
Roll out to a small cohort before wider usage.
Set monitoring and fallback
Define rollback path and monitor errors after adoption.
Evidence readiness
Missing required evidence: Metadata review. Risk score 31.
Source repository/provenance is listed.
Required in this preset
Review metadata is missing.
Required in this preset
Safety notes are present.
Required in this preset
Privacy notes are present.
Optional in this preset
Package integrity metadata is missing.
Optional in this preset
Install payload is available.
Required in this preset
Required gaps: Metadata review
Decision timeline
Blocking gaps: Check metadata review status. Risk 28.
triage
Source/provenance metadata is available.
triage
Review metadata is missing.
verify
Safety notes are available.
verify
Privacy notes are available.
verify
Package integrity metadata is missing.
rollout
Install payload is available.
Blockers: Check metadata review status
Prerequisite readiness
5 prerequisites to line up before setup. Includes a review or approval gate.
Safety & privacy surface
5 safety and 4 privacy notes across 5 risk areas. Review closely: permissions & scopes, network access.
Disclosure: MIT-licensed Azure Data API Builder project with active MCP source, samples, and testing guidance. Treat the MCP surface as release-sensitive and verify current DAB release notes before using it outside a reviewed environment.
{
"mcpServers": {
"data-api-builder": {
"url": "https://<dab-host>/mcp"
}
}
}Data API Builder MCP Tools are the MCP support being added to Azure Data API Builder for exposing configured database entities as tools. The source tree includes MCP server code and built-in tools for describing entities, reading records, creating records, updating records, deleting records, and related DAB database operations.
Use it when a team is already using Data API Builder and wants to evaluate an MCP interface to the same entity model, permissions, and database-backed CRUD surface that DAB exposes through its API configuration.
These sources were reviewed on 2026-06-06. Prefer the live repository, MCP Inspector testing guide, license, sample configuration, MCP server source, and built-in DML tool sources for current setup and behavior details.
Enable the MCP runtime section in a reviewed Data API Builder configuration:
{
"runtime": {
"mcp": {
"enabled": true,
"path": "/mcp"
}
}
}
Start DAB with the approved configuration, then connect the MCP client to the configured MCP path:
{
"mcpServers": {
"data-api-builder": {
"url": "https://<dab-host>/mcp"
}
}
}
Because the public README still describes MCP endpoint support as coming soon, verify the exact DAB release, package, and deployment mode before relying on the MCP interface outside testing.
describe_entities before planning database work.Data API Builder MCP Tools can read and mutate database records. Treat the MCP endpoint as database access, not as documentation search. Start with read-only roles, disable DML tools where possible, and require explicit approval before create, update, delete, aggregate, execute, or stored-procedure workflows.
Treat schema metadata, record payloads, primary keys, role headers, connection details, request bodies, query results, logs, and MCP transcripts as sensitive. Do not expose customer, production, regulated, or irreplaceable databases to an agent without backups, audit logging, query limits, and rollback procedures.
No Azure/data-api-builder, Data API Builder MCP, DAB MCP tools, Azure database
MCP, or matching source URL entry was found in content/mcp or README.md.
Existing database MCP entries do not cover Azure Data API Builder's source-level
MCP support for configured DAB entities.
Show that Data API Builder MCP Tools is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/mcp/data-api-builder-mcp-tools)Data API Builder MCP Tools side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
| Field | MCP support in Azure Data API Builder for exposing configured database entities as MCP tools, including entity discovery and DML operations over Azure databases and supported on-premises data stores. Open dossier | Official Alpaca MCP server for Trading API workflows, including account and portfolio data, orders, positions, watchlists, assets, stocks, crypto, options, news, corporate actions, and market data. Open dossier | Apache-licensed TypeScript MCP server for Obsidian vaults with stdio and Streamable HTTP transports, Local REST API access, note search, section-aware edits, tag/frontmatter management, path policies, and read-only controls. Open dossier | Official data.gouv.fr MCP server for searching French national open datasets, exploring organizations and data services, inspecting resources, querying tabular data, and retrieving dataset metrics through Claude. Open dossier |
|---|---|---|---|---|
| Next steps | ||||
| Trust | ||||
| Review status | Not reviewed | Not reviewed | Not reviewed | Not reviewed |
| Package trust | Package not verified | Package not verified | Package not verified | Package not verified |
| Source provenance | Source-backed | Source-backed | Source-backed | Source-backed |
| Submitter | oktofeesh1 | oktofeesh1 | oktofeesh1 | oktofeesh1 |
| Install risk | Review first | Review first | Review first | Review first |
| Notes | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ |
| Brand | — | |||
| Category | mcp | mcp | mcp | mcp |
| Source | Source-backed | Source-backed | Source-backed | Source-backed |
| Author | Azure | Alpaca | cyanheads | data.gouv.fr |
| Added | 2026-06-06 | 2026-06-06 | 2026-06-06 | 2026-06-06 |
| Platforms | ||||
| Harness | ||||
| Source repo | — | — | — | — |
| Safety notes | ✓Data API Builder MCP tools can expose database entity metadata and perform DML operations depending on DAB configuration and permissions. Built-in tools include entity discovery and record read, create, update, delete, aggregate, and execute-style workflows in the MCP source tree. The upstream README still labels endpoint support as coming soon while source, samples, and testing docs expose MCP behavior; verify the exact release before production use. Use least-privilege roles, disable DML tools where not required, and require approval before write, delete, execute, or stored-procedure operations. Do not connect MCP clients to production databases without backups, audit logging, query limits, and rollback procedures. | ✓Alpaca MCP Server can expose account balances, buying power, positions, orders, activities, watchlists, assets, market data, news, corporate actions, stocks, crypto, options data, and trading tools to the MCP client. Trading tools can place stock, ETF, crypto, and option orders, cancel orders, close positions, liquidate portfolios, replace orders, and exercise or mark do-not-exercise option contracts. Paper trading is the default documented mode; setting `ALPACA_PAPER_TRADE=false` points trading calls at live Alpaca accounts and can result in real financial losses. Require explicit human approval before any order placement, cancellation, liquidation, option exercise, live-account change, or strategy involving leverage, margin, extended hours, crypto, or options. Use `ALPACA_TOOLSETS` to restrict the server to read-only or data-only toolsets when trading tools are not needed. The upstream order override code warns that read timeouts may happen after an order was sent; users should check open orders before retrying to avoid duplicate trades. | ✓Cyanheads Obsidian MCP can read, list, search, create, append, patch, replace, delete, tag, and edit frontmatter in the configured vault through the Local REST API plugin. The server defaults to full-vault access unless read paths, write paths, or read-only mode are configured. Set `OBSIDIAN_READ_ONLY=true` for research-only workflows, then narrow writes with `OBSIDIAN_WRITE_PATHS` before allowing note edits. Delete operations are permanent in the vault and should require human review even when the MCP host supports destructive-tool prompts. Command-palette tools are disabled unless `OBSIDIAN_ENABLE_COMMANDS=true`; command execution can trigger opaque or destructive Obsidian plugin behavior. Streamable HTTP deployments should use JWT or OAuth auth before being exposed beyond a trusted local machine. | ✓The hosted endpoint is documented as publicly available without access restrictions, so treat requests and returned public-data context as externally visible. Tools are read-only but can retrieve dataset metadata, resource URLs, rows from tabular resources, service OpenAPI specs, metrics, and organization details that may influence decisions. Public open data can be stale, incomplete, licensed with reuse conditions, or unsuitable for operational decisions without checking the dataset publisher and update cadence. Tabular queries can return rows from large resources; use small page sizes and pagination instead of asking an agent to pull entire datasets through chat. If self-hosting, review MCP_HOST, allowed hosts, allowed origins, Sentry, Matomo, and API-environment settings before exposing the server. |
| Privacy notes | ✓Entity metadata can expose database names, table names, view names, stored procedure names, field names, key fields, relationships, permissions, and role design. Read and DML tool calls can expose or change customer records, internal data, regulated fields, identifiers, audit fields, and business workflow state. Connection strings, role headers, MCP URLs, logs, request bodies, result payloads, and MCP transcripts can contain sensitive operational or personal data. Redact database values, connection details, entity names, role names, and query results before sharing prompts, screenshots, logs, or generated notes. | ✓Alpaca API keys, secret keys, account IDs, balances, buying power, portfolio history, activities, positions, orders, watchlists, option contracts, crypto holdings, and trade history can be exposed to the MCP client. Prompts and responses may include private trading strategy, portfolio allocation, order intent, symbols, quantities, prices, client order IDs, and market data queries. MCP clients, model providers, terminal history, logs, and chat transcripts may retain financial data and trading instructions. Upstream documentation states the server sends an Alpaca MCP user agent string for API calls; review Alpaca privacy and disclosure materials for account data handling. | ✓Vault notes, headings, block references, frontmatter, tags, file metadata, outgoing links, search queries, command names, plugin status, and edit history may be exposed to the MCP client and model provider. API keys, local plugin endpoints, HTTP auth settings, path allowlists, logs, OpenTelemetry traces, and Docker environment variables can reveal private vault structure or credentials. Tag listing is vault-wide in upstream behavior and can reveal tag names outside narrowed read paths. Notes may contain personal journals, client work, credentials, meeting notes, research plans, health data, or other sensitive knowledge-base content. | ✓Search terms, dataset interests, resource IDs, user-agent headers, request URLs, tool names, and returned dataset rows may be visible to the hosted MCP service, MCP client, model provider, and logs. The server includes optional Matomo and Sentry instrumentation in source; hosted deployments may apply their own analytics and error-reporting policies. Public datasets can still contain personal data, geographic sensitivity, business identifiers, or regulated information; review source metadata and reuse terms before sharing results. Avoid placing private investigation notes, customer context, or unpublished analysis inside prompts when a generic dataset search is enough. |
| Prerequisites |
|
|
|
|
| Install | | | | |
| Config | | | | |
| Citations | ||||
| Claim | Unclaimed | Unclaimed | Unclaimed | Unclaimed |
Connect Claude to Alpaca Trading API workflows for account data, market data, orders, positions, watchlists, stocks, crypto, and options.
Give Claude scoped access to Obsidian vault notes, tags, frontmatter, sections, search, UI opening, and guarded write tools through the Local REST API plugin.
Source-backed guides for putting this to work.
Loading live community signals…
A short, calm digest of reviewed Claude resources. Unsubscribe any time.