Taskriz
Taskriz, MCP Apps and MCP Elicitation
MCP Apps and MCP Elicitation let an AI Agent show the person in the chat an interface or a form. Taskriz goes where they can’t: to someone who isn’t in the chat — on their phone, now or hours later — and it works through MCP.
Different jobs
MCP Apps and Elicitation
Two parts of the open Model Context Protocol. MCP Apps lets a tool show an interactive interface — HTML in a sandboxed iframe — inside the chat of a host such as Claude, ChatGPT or VS Code. Elicitation lets a server ask the person using the chat for input on a simple form, mid-task.
Taskriz
A service for reaching people who aren’t in the chat. Your Agent sends a request whose interface it designs to anyone paired with it, and gets their answer back whenever they give it. It works through MCP: the Taskriz MCP server lets any MCP host’s Agent send requests.
What they share
- Input mid-task. Both let an Agent get a person’s input before it carries on.
- Structured answers. Both return what the person entered as data, not just text.
- MCP underneath. Taskriz is used through MCP too — the Taskriz MCP server works with any MCP client.
Side by side
| MCP Apps and Elicitation | Taskriz | |
|---|---|---|
| What it is | An open standard: MCP Apps, an official extension stable since January 2026, and Elicitation, in the core specification (current revision 2026-07-28) | A hosted service that gives any Agent a way to reach people — with plugins, an MCP server and an API, and no app for you to build |
| Who answers | The person using the AI chat or editor, in the conversation that asked | Anyone paired with your Agent — your team, your customers, contractors, family — wherever they are, straight away or hours later |
| Where people answer | Inside the MCP host — such as Claude, ChatGPT, VS Code or Goose — where it supports them | The Taskriz app, in the browser on any phone or computer — nothing to install; email notices, and text messages in Australia (the United States soon) |
| What a request can ask | MCP Apps: any HTML interface your server provides. Elicitation: a flat form of text, numbers, yes or no, dates and choices — no files | An interface your Agent designs for each request, from iOS-style building blocks — screens, lists, choices, switches, dates and times, numbers, notes, photos and documents — following world-leading human interface guidelines |
| Answers back to the Agent | Within the conversation: tool calls from the interface, or the form’s answer when the request is retried | As structured data, matched to the request: through the plugins, a signed webhook, a WebSocket or the events list — whenever the person answers |
| Connecting your Agent | Build and host an MCP server; each host decides what it supports | Plugins for Claude Code and ChatGPT (desktop and Codex), the Taskriz MCP server for any MCP client, and an HTTPS API for any Agent or workflow |
| Cost | Free and open; you build, host and run your MCP server | Free to start — 500 requests a month, no card; then Builder at $29 or Business at $99 a month. No seats, and the people who answer never pay |
Security
MCP is careful inside the conversation: MCP Apps run in a sandboxed iframe, the host shows which server is asking, and forms mustn’t ask for passwords or payment details. Reaching someone outside the conversation isn’t part of it — and there, Taskriz’s protections come built in.
| MCP Apps and Elicitation | Taskriz | |
|---|---|---|
| Who can reach a person | The person in the conversation; the host shows which server is asking | Only people who paired with your Agent — by accepting an invitation, scanning a QR code or entering a pairing code — and every new pairing is confirmed by email |
| Encryption | Set by your server and the host’s connection to it | Each request is sealed to the person’s own devices and stored that way, and travels over TLS 1.2 or later |
| Who can read a request | The host, your server and the AI model’s conversation | Only the person’s devices — a request passes through Taskriz while it’s delivered, and is never stored or logged readable |
| Running the interface | MCP Apps: a sandboxed iframe with a strict content security policy. Elicitation: the host’s own form | In a WebAssembly sandbox with no network or file access of its own; pictures come through Taskriz, so a picture’s server never learns who opened a request |
To be plain about Taskriz too: files sent with a request or reply are encrypted on our servers but not sealed to devices, and two-step sign-in is on the Roadmap. Security has the details.
When Taskriz fits
- The person your Agent needs isn’t the one in the chat — a customer, a colleague, someone in the field.
- They should be able to answer later, on their phone, and your Agent should get the answer whenever it comes.
- Your Agent needs more than a flat form — photos, documents, proper screens and lists.
- You want to use it from any MCP host, through the Taskriz MCP server — no MCP server of your own to build.
When MCP fits
- The person you need is the one using the chat, right now.
- You’re building an MCP server and want a rich interface inside Claude or ChatGPT.
Questions
What’s the difference between MCP Apps and Taskriz?
MCP Apps shows an interface to the person using an AI chat, inside that chat. Taskriz takes your Agent’s request to someone else — anyone paired with your Agent — on their phone or computer, and brings the answer back whenever they give it.
Can MCP Elicitation ask someone other than the user?
No. Elicitation asks the person using the MCP client, in the task that asked — even its URL mode requires the same person to open the link. Taskriz sends your Agent’s request to anyone paired with it.
Does Taskriz work with MCP?
Yes. The Taskriz MCP server, at https://www.taskriz.com/mcp with OAuth sign-in, lets any MCP client’s Agent create and send requests and read the answers.
About this comparison
MCP Apps and MCP Elicitation were checked in October 2026 — the MCP Apps specification of 2026-01-26 and the MCP revision of 2026-07-28 — from MCP Apps and MCP Elicitation on modelcontextprotocol.io. The Model Context Protocol is an open project; Taskriz is not affiliated with it. What Taskriz is building next is on the Roadmap.