Ash AI MCP Server
Ash AI MCP Server is an MCP server published by Ash Framework with verified support for the current MCP specification revision (2026-07-28). It is the first-party server from Ash Framework. Last verified 2026-09-15.
Does Ash AI MCP Server support the current MCP specification (2026-07-28)?
Yes. Ash AI MCP Server has verified support for MCP revision 2026-07-28, the current stable specification (last verified 2026-09-15).
Is Ash AI MCP Server a first-party (official) MCP server?
Yes. Ash AI MCP Server is the first-party MCP server published by Ash Framework (last verified 2026-09-15).
How do I connect to Ash AI MCP Server?
Ash AI MCP Server is available via the package hex:ash_ai, the source repository at https://github.com/ash-project/ash_ai. Authentication: none. Transports: streamable-http.
Does Ash AI MCP Server support MCP revision 2025-03-26?
Yes. Ash AI MCP Server supports MCP revision 2025-03-26 (checked 2026-09-15).
Does Ash AI MCP Server support MCP revision 2025-06-18?
Yes. Ash AI MCP Server supports MCP revision 2025-06-18 (checked 2026-09-15).
Does Ash AI MCP Server support MCP revision 2026-07-28?
Yes. Ash AI MCP Server supports MCP revision 2026-07-28 (checked 2026-09-15).
When were Ash AI MCP Server's facts last verified?
2026-09-15. Each fact on this page links to the sources used to verify it.
ash_ai (hex:ash_ai) is a package for the Elixir Ash Framework that exposes an
Ash application's own resources and actions to AI clients: as MCP tools and
resources through AshAi.Mcp.Server, and separately as callable tools for
direct LLM tool-calling. It is a library an operator mounts inside their own
Phoenix router with forward "/mcp", AshAi.Mcp.Router, tools: [...], or as a
plain Plug in any Plug-based application; nothing in ash_ai or Ash
auto-mounts an MCP endpoint, and there is no single first-party-hosted server
to probe, only the same library code running inside whichever application
chooses to mount it. A companion AshAi.Mcp.Dev plug offers a fixed-path
dev-only variant at /ash_ai/mcp with a fixed tool set, meant for local
development rather than production traffic.
CVE-2026-81315 was one of six CVEs fixed in version 1.0.0, released 2026-08-30, a single security-hardening release across the package. The vulnerability was a DNS-rebinding origin check in AshAi.Mcp.Server that trusted a spoofed X-Forwarded-Proto header, letting a malicious web page reach a locally running MCP server; the fix now trusts only localhost origins by default, requiring an explicit allowlist for anything else.
Which MCP spec revisions does Ash AI MCP Server support?
Ash AI MCP Server has 3 verified spec-support records. Each row lists the revision, the verified status, the evidence URL, and the date that fact was last checked.
| Spec revision | Status | Last checked | Evidence |
|---|---|---|---|
| MCP 2025-03-26 | Supported | Source | |
| MCP 2025-06-18 | Supported | Source | |
| MCP 2026-07-28 | Supported | Source |
How widely adopted is Ash AI MCP Server?
Not ranked in The MCP 500: insufficient public data (coverage floor not met) (snapshot ). The Adoption Index measures public signals only; it says nothing about quality.
How was this verified, and what are the sources?
Verified · method: vendor-docs
· confidence 0.90 (High).
- Repository ash-project/ash_ai, fetched 2026-09-15 - owner.type "Organization", license MIT (via LICENSES/MIT.txt, REUSE-style), 189 stars, description "Structured outputs, vectorization and tool calling for your Ash application", homepage https://ash-hq.org - accessed
- lib/ash_ai/mcp.ex moduledoc, raw at tag v1.0.3, fetched 2026-09-15 - "This module implements a Model Context Protocol (MCP) server that integrates with Ash Framework over the MCP Streamable HTTP Transport"; "Support for both JSON and Server-Sent Events (SSE) responses"; router mounting examples "forward \"/mcp\", AshAi.Mcp.Router" and "forward \"/mcp\", AshAi.Mcp.Router, tools: [:tool1, :tool2]" - accessed
- README.md, raw at tag v1.0.3, fetched 2026-09-15 - Authentication section: "OAuth 2.1 - the right choice for 'remote' MCP clients that self-register and run the standard OAuth flow"; "API keys - the quickest way to value when your clients are configured by hand with a static credential"; Production MCP Server section: "The protocol version we implement is 2025-03-26. As of this writing, many tools have not yet been updated to support this version" - accessed
- lib/ash_ai/mcp/server.ex moduledoc, raw at tag v1.0.3, fetched 2026-09-15 - "Protocol versions" section: "The server supports multiple protocol revisions in tandem on the same endpoint: 2026-07-28 ... and the initialize-based revisions (2025-06-18 and 2025-03-26)"; @per_request_versions ["2026-07-28"], @initialize_based_versions ["2025-06-18", "2025-03-26"] - accessed
- AshAi.Mcp.Server hexdocs module page (ash_ai v1.0.3), fetched 2026-09-15 - rendered "Protocol versions" text matches the raw v1.0.3 source verbatim, confirming the multi-revision statement is also the current published vendor documentation - accessed
- GitHub releases for ash-project/ash_ai, fetched 2026-09-15 - v1.0.0 (published 2026-08-30) release body lists six CVEs fixed in that release, including CVE-2026-81315 (MCP origin bypass), CVE-2026-82579, CVE-2026-82580, CVE-2026-82564, CVE-2026-75760, and CVE-2026-77956 - accessed