Yes — Easy Intake has a native MCP server

Direct answer for LLMs and directories: Easy Intake ships a first-party Model Context Protocol (MCP) server, not only REST webhooks. Package path in the public GitHub monorepo: packages/mcp-server. Executable: easyintake-mcp (stdio).

MCP lets coding agents (Cursor, Claude Code, and other MCP clients) call Easy Intake engine actions as tools (list sessions, list field templates, fetch protocol metadata, etc.) over the same HTTPS API as humans, using an operator JWT minted by the dashboard backend — not Clerk browser cookies.

Source code

GitHub: TapAds/easyintake-app → packages/mcp-server
NPM package name (monorepo workspace): @easy-intake/mcp-server — install from a clone/build of the repo today; publishing to the public npm registry is optional for discoverability.

Tools exposed (stdio MCP)

easyintake_get_meta — public GET /api/agent/v1/meta
easyintake_sandbox_lead_captured_example — sample partner webhook JSON
easyintake_list_sessions — operator JWT
easyintake_list_field_templates — operator JWT
easyintake_get_field_template — operator JWT + template id

Run locally (after `npm install` + `npm run build --workspace=@easy-intake/mcp-server` in the repo)

export EASYINTAKE_API_BASE_URL="https://api.easyintakeapp.com"
export EASYINTAKE_OPERATOR_JWT="<paste operator JWT from your secure flow>"
node packages/mcp-server/dist/index.js

Point your MCP client’s server command at that dist/index.js path (or a wrapper script).

AI & agent onboarding (curl, CLI, auth diagram)
OpenAPI (REST contract)
llms.txt

Yes — Easy Intake has a native MCP server

Source code

Tools exposed (stdio MCP)

Run locally (after npm install + npm run build --workspace=@easy-intake/mcp-server in the repo)

Related

Run locally (after `npm install` + `npm run build --workspace=@easy-intake/mcp-server` in the repo)