Packages

ectomancer

1.1.0

1.4.0 1.3.1 1.3.0 1.2.1 1.1.0 1.0.0 0.1.0-rc.4 0.1.0-rc.3 0.1.0-rc.2

Add an AI brain to your Phoenix app - Auto-expose Ecto schemas as MCP tools

HexDocs

Current section

Files

Jump to

Readme 9 Versions 6 Dependencies 0 Dependants Files Activity

ectomancer priv templates mcp_module.eex

Raw

priv/templates/mcp_module.eex

defmodule MyApp.MCP do
  use Ectomancer,
    name: "<%= mcp_name %>",
    version: "<%= mcp_version %>"

  <% for schema <- schemas do %>
    # Auto-generated tool for <%= schema.module %>
    expose <%= inspect(schema.module) %>,
      actions: <%= determine_actions(schema) %>
  <% end %>
end

Search filters

Type any of these into the search box. They can be combined with free text which searches package names and descriptions.

Operator	Description	Example
name:	Match package name. Supports * wildcards and repo/package form	name:phx* or name:hexpm/phoenix
description:	Full-text search of package descriptions	description:auth
depends:	Packages depending on a given package. Supports repo:package form	depends:ecto or depends:hexpm:ecto
build_tool:	Filter by build tool	build_tool:mix
updated_after:	Packages updated after an ISO8601 datetime	updated_after:2025-01-01T00:00:00Z
extra:	Match custom metadata (key,value). Nested keys are separated by commas	extra:license,MIT

Wrap values in double quotes to include spaces, e.g. name:"my package".