See what your AI found as real cards you can trust and act on.
When Claude, ChatGPT or another MCP Apps host finds a plumber, a hotel or a flight, Inkview draws it right in the chat: a card that says where the data came from and takes you straight to the business. Free hosted server, open source. Why and where it's heading: docs/direction.md.
Installs the server and a short Skill that tells Claude when to use each component:
/plugin marketplace add feimacode/inkview
/plugin install inkview@inkview
Claude Desktop, Claude Code, Codex, Cursor and VS Code start Inkview over stdio:
{ "mcpServers": { "inkview": { "command": "npx", "args": ["-y", "@feimacode/inkview"] } } }Hosts that support MCP Apps (Claude Desktop) draw the component; text-only
clients (Claude Code, Codex) print its markdown version. Each release also has a
.mcpb desktop extension for one-click install in Claude Desktop. Setup for
each app: docs/local-quickstart.md.
These connect from the cloud, so they need an HTTPS URL ending in /mcp: the
hosted server (coming with the public launch), your own deployment
(self-hosting, Docker included), or for a quick test
npm run dev plus a tunnel (guide).
ChatGPT app setup: docs/chatgpt-app.md. What the hosted
server does with your data: docs/privacy.md.
npm install # also builds
node packages/inkview/dist/inkview.js # stdio
npm run dev # HTTP on http://localhost:3001/mcp
npm run preview # gallery of every component, light and dark, at http://localhost:5174| Tool | Draws | Try asking |
|---|---|---|
show_profile_card |
A person: avatar, role, tags, links. Shortlist, open profile, draft outreach | "Find Ada Lovelace and show her profile card" |
show_profiles |
2 to 24 people as a responsive grid of compact cards. Select several to ask about, add to a shortlist, expand one into the full profile | "Who is speaking at AI Summit 2026? Show me the speakers" |
show_timeline |
Up to 50 dated events on a vertical timeline. Expand details, filter categories, reverse order, open links or ask about an event | "Show Northstar's company history as a timeline" |
show_tasks |
Up to 50 tasks with a status, as a grouped checklist or a board. Check items off, move them between statuses, send the changes back. Overdue and priority cues | "Show the website relaunch tasks as a checklist" |
show_table |
Up to 50 typed rows (text, number, money, date, link, badge, journey). Sort, filter, select rows to ask about, CSV download. A journey column draws a flight, train or bus trip with stops, layovers, next-day arrival and duration | "Compare these Sydney to Tokyo flights" or "Show the 10 largest EU cities by population as a table" |
show_results |
Up to 20 search results or sources with snippets. Open, dig deeper | "Search for MCP Apps docs and show the results" |
show_entity_card |
A company, product, place or organization: facts and links, with an optional phone and address. Open website, call, directions, compare | "Show me a card for Stripe" |
show_comparison |
2 to 5 options side by side, with an optional recommendation. Values can be text, numbers, yes/no, ratings or journeys (flight or train finalists). Choose this | "Compare Notion, Obsidian and Apple Notes for a small team" |
show_chart |
Line or bar chart, up to 5 series. Tooltips, legend toggles, text summary for screen readers | "Chart our monthly signups for this year" |
show_products |
Up to 12 products with price, rating and availability. Sort, view at store, compare (no cart) | "Find noise-cancelling headphones under $300" |
show_document |
One draft document — email, message, post, letter or report — with its header, rendered markdown body, word and character counts and an optional character limit. Edit it in place, copy it, approve it and send it back | "Draft a follow-up email to Marcus about the renewal" |
show_form |
1 to 12 typed inputs — text, long text, number, date, choice, multi-choice, checkbox, email, URL — with labels, help and inline validation. Submit the answers back to chat or cancel | "Ask me a few questions to plan our trip to Lisbon" |
show_map |
Up to 50 places on a fitted map: pan and zoom by pointer, touch or keyboard, linked pins, list and detail, "Open in maps" and "Ask about selected". Pins can carry a short label such as a price. Places with only an address are listed as "Not on map" (Inkview does not look up coordinates). Tiles configured by INKVIEW_MAP_TILES, with a neutral-grid fallback |
"Show these restaurants on a map so I can see how close they are" |
show_listings |
Up to 20 places, services, stays, events or homes as cards with price, rating, badges and distance. Sort, shortlist, ask or compare, switch to a map, and Call, Open at site or Directions (no booking or payment) | "Find a plumber near Parramatta for a leaking tap" |
show_itinerary |
A plan of up to 14 days with ordered stops, times, costs and a map per day. Move, reorder or remove stops and send the changes back; add timed stops to a calendar (.ics) | "Plan 3 days in Kyoto with kids" |
show_auto |
Any JSON: picks the best component above, or formatted text | (fallback when the shape is unclear) |
It looks at the data's shape, in this order, and the first match wins:
- Product grid: an array of items with a title or name, a URL and a price.
- Result list: an array of items with a title or name and a URL.
- Chart: rows of a date or label plus numeric columns (
[{month, users}]), alabel → numbermap ({Mon: 3, Tue: 5}), or{x, series}. - Profile card: one person: a name plus a role (
title,jobTitle,role) or person fields (firstName,linkedin). - Entity card: one organization or place: a name plus org fields such as
website,industry,founded,headquarters,addressortype. - Data table: an array of same-shaped records (first 50 rows kept).
Wrappers like {results: [...]}, {products: [...]} and {rows: [...]} are unwrapped first.
A hint ("table", "chart"...) overrides detection when the data fits that
component. Anything else is shown as formatted text. The text result names the
explicit tool, so the model can call it directly next time.
Every card ends in a step that takes the user to the business itself, and says where its data came from. Inkview only links out or dials: it never books, reserves or pays.
Actions come only from the fields you pass. No field, no button.
| Field passed | Action | What it does |
|---|---|---|
url (websiteUrl on the entity card) |
Open at site (worded per component, such as "View at store") | Opens the page through the host |
phone |
Call | Opens a tel: link through the host |
address, or lat and lng |
Directions | Opens a map search for the place |
start (an ISO date or date-time) |
Add to calendar | Downloads an .ics file; only on hosts that support downloads |
phone, address or url |
Copy | Copies the value, or selects it when the host blocks the clipboard |
At most three actions show as buttons; the rest sit under "More".
| Component | Actions |
|---|---|
show_listings |
Open at site, Call, Directions, Add to calendar, Copy address |
show_entity_card |
Open website, Call, Directions, Copy phone, Copy address |
show_products |
View at store, Copy link |
show_results |
Open, Copy link |
show_comparison |
Open at site, for each option with a url |
show_itinerary |
Directions for each stop with an address or coordinates, Add to calendar for the plan |
show_map |
Open in maps |
Link fields accept only https:// and http:// URLs. A javascript: or
data: URL is rejected with a validation error, and the view refuses to open
any link that is not web, phone or mail.
Sources. Every component with a source takes name, an optional url
and an optional retrievedAt (the ISO 8601 time the agent fetched the data),
and shows them in one footer: "Source: Booking.com · checked 2 hours ago".
Listings, products, comparison options, results (as sourceInfo), itinerary
stops and map places can each carry their own source; the footer names every
site once.
Unverified values. An item's unverified lists the names of its fields the
agent did not fetch (on a comparison option, the criteria; on an entity card,
phone, address or a fact's label). Each one is drawn with a small "◦" mark
that screen readers announce as "not checked", and the footer explains the
mark. Names the item does not have are ignored.
Components that show prices, ratings, phone numbers or availability also say "No source given" when nothing has a source, and "may have changed" when the latest check is more than 24 hours old.
{
"kind": "stay",
"listings": [
{
"title": "Harbour Rocks Inn",
"price": { "amount": 289, "currency": "AUD" },
"address": "34 Harrington St, The Rocks NSW 2000",
"url": "https://example.com/stays/harbour-rocks",
"source": { "name": "Booking.com", "url": "https://www.booking.com", "retrievedAt": "2026-11-12T09:30:00+11:00" }
},
{
"title": "Quay Loft",
"price": { "amount": 240, "currency": "AUD" },
"phone": "(02) 9555 0142",
"unverified": ["price"],
"source": { "name": "Airbnb", "url": "https://www.airbnb.com", "retrievedAt": "2026-11-12T09:32:00+11:00" }
}
]
}In text-only hosts the same call lists the phone as a tel: link, a
"Directions" map link, "(not checked)" after the unverified price, and a source
line with the check time.
Inkview is an MCP server of render tools. The agent gathers data with its own
tools (search, LinkedIn, CRM...), then calls a render tool such as show_table or show_profile_card with it. The
server validates the data and returns:
structuredContentfor the UI, which the host draws from the tool'sui://resource in a sandboxed iframe- a markdown version of the same view, for the model and for text-only hosts (Claude Code, Codex CLI)
The server is stateless: it stores nothing and never logs tool arguments.
| Piece | Where |
|---|---|
One folder per component: meta.ts, schema.ts, markdown.ts, View.tsx, examples.json |
src/components/<name>/ |
Render tools + the shared ui://inkview/v1/app.html resource |
packages/inkview/src/server.ts |
HTTP (/mcp) and stdio entry point |
packages/inkview/src/main.ts |
| SDK for other MCP servers | packages/sdk/src/ |
| Shared view runtime (MCP Apps bridge, theming, states) | src/runtime/ |
| Dev host, preview gallery, render checks | dev/, scripts/ |
The server ships as one dependency-free file (packages/inkview/dist/inkview.js, view HTML
inlined), so a cold npx start takes about a second.
Your own MCP server can render the same components from its tools with
@feimacode/inkview-sdk. Serve the view once, attach the tool
metadata, and return a builder's result:
import { McpServer } from "@modelcontextprotocol/server";
import { registerAppTool } from "@modelcontextprotocol/ext-apps/server";
import { inkview, registerInkview } from "@feimacode/inkview-sdk";
const server = new McpServer({ name: "my-server", version: "1.0.0" });
const view = registerInkview(server);
registerAppTool(
server,
"city_temperatures",
{
title: "City temperatures",
description: "July averages rendered as a table.",
_meta: view.inkviewToolMeta({ component: "data_table" }),
},
async () =>
inkview.table({
columns: [
{ key: "city", label: "City" },
{ key: "celsius", label: "Celsius", type: "number" },
],
rows: [{ city: "Oslo", celsius: 17 }],
}),
);The SDK returns the markdown fallback and the structured result together, so
text-only hosts keep working. Every builder and its limits:
docs/sdk.md. A runnable example:
examples/sdk-server.
npm test # build, bundle size budget, MCP smoke tests (HTTP and stdio), hosting limits, unit tests, render checksRender checks draw every example in light, dark and 320 px, and check contrast,
keyboard focus and each component's actions. They need Playwright's Chromium
(npx playwright install chromium). Screenshots land in dist-test/.
See CONTRIBUTING.md.
| Variable | Default | Purpose |
|---|---|---|
PORT |
3001 |
HTTP port |
HOST |
127.0.0.1 |
Bind address (use 0.0.0.0 in a container) |
INKVIEW_IMAGE_DOMAINS |
Extra avatar image origins for the component CSP, comma separated | |
INKVIEW_UI_DOMAIN |
Dedicated sandbox origin, if a host asks for one |
HTTP mode also has a body limit, per-IP rate limit and a metadata-only access log; see docs/self-hosting.md for those settings.
Avatars only load from origins declared in the CSP (GitHub, LinkedIn media, Gravatar, unavatar.io, Wikimedia, Unsplash, X/Twitter images by default). Anything else falls back to initials.
npm run evals measures whether models pick the right component and avoid
inventing values (needs an Anthropic API key). See evals/README.md.
The MVP is planned as OpenSpec changes: see docs/roadmap.md and openspec/.
MIT










