Recipes MCP Server

MCP Server in Phoenix

Expose your app’s actions to Claude Code, Cursor, and other AI coding agents over the Model Context Protocol. Your Jido actions become tools an AI can call — list_users, get_site_stats, whatever you define — from inside the user’s editor.

This is the pattern behind Petal Pro’s admin MCP server. The same Jido.Action modules power both the in-app admin chat and the external MCP endpoint. Add a tool once, get it in two places.

MCP is JSON-RPC 2.0 over HTTP. Phoenix handles it natively — no special framework needed.

What you can actually do with this

  • Ask Claude Code from your editor: "how many users signed up this week?" — it calls your get_site_stats tool and answers from real data.
  • Use it as a customer support copilot: "summarise this user's account" pulls their full profile, memberships, and recent activity.
  • Pair with the tool calling recipe — the same Jido actions work for in-app admin chat and the external MCP endpoint. One registry, two surfaces.
  • Reference impl: mcp.petal.build exposes the petal_components schemas to AI coding tools via this exact pattern.