← Delight demo

FULL IRON DESIGN STUDIO / DELIGHT

Public work. Clear connections.

Help people and agents find projects, understand the evidence and open a demo — on the web or inside a compatible AI conversation.

Delight combines an MCP server, WebMCP tools and an MCP Apps gallery. The ready-to-run reference app uses Full Iron’s public catalog. A different catalog requires adapting the source implementation.

For your team

Marketers
Show projects with context, evidence and a clear path to the demo.
Website operators
Test discovery and the gallery, then choose the connection your client supports.
Developers & agents
Use explicit schemas, stable IDs and structured results.

Start in one command

Node.js 22+. No API key needed.

npx delight-mcp@0.1.3

Keep the CLI running and open http://127.0.0.1:3001. Search for Python to see matching projects and source links.

Choose your connection

  • MCP / stdio: a local client launches the CLI with --stdio.
  • MCP / HTTPS: cloud clients need a publicly reachable HTTPS /mcp endpoint.
  • WebMCP: experimental document.modelContext in a supporting browser.
  • MCP Apps: interactive gallery rendering requires host support.
{"mcpServers":{"delight":{"command":"npx","args":["-y","delight-mcp@0.1.3","--stdio"]}}}

Example for clients using mcpServers JSON; use your client’s configuration format. Windows clients may require npx.cmd.

Public reference endpoint: https://fulliron-portfolio-agent.vercel.app/mcp

The ordinary demo works without WebMCP. MCP support does not imply Apps support. An npm install does not automatically connect ChatGPT or Codex.

Agent contract

ToolArgumentsResult
get_profilelocale?Public background and sources
search_portfolioquery, limit?, locale?Projects, stable IDs and sources
get_projectid, locale?Evidence, limitations and links
get_contact_optionslocale?Contact links

locale: en | uk · limit: 1–6 · query: 1–120 Unicode characters, with a non-whitespace character.

  1. Discover schemas through tools/list or agentToolDefinitions from delight-mcp/webmcp.
  2. Search with search_portfolio. Use the returned project IDs.
  3. Read evidence and limitations with get_project.
  4. Answer with source links. An empty search is a valid result.

Tools read public data only. Contact links do not send messages. Project descriptions are catalog claims, not independent audits.

If something does not work

Check that the CLI is running and the port is available. A cloud client cannot reach 127.0.0.1. If a card does not render, use structured results and check Apps support.

Exports, browser integration, HTTPS and deployment →