James Aspinwall | February 2026
2026 is officially the year of the Agentic Interface. Your digital presence should feel as integrated and fluid as the MCP servers you build. What follows is a design concept for both a personal “Calling Card” and a high-conversion landing page for a boutique AI consultancy.
1. The Digital Handshake: Pixel 10 “Calling Card”
Android 16’s Material 3 Expressive update gives the Pixel 10 Pro a native Calling Card feature. This is the first thing people see when you tap phones at a conference like the MCP Dev Summit.
Design Specs
- Visual Style: Glassmorphism with a deep indigo-to-teal gradient — evoking clean, structured data flow.
- Dynamic Element: A subtle animated SVG node network in the background, reacting to the phone’s gyroscope.
- Primary Text: Your Name + “Principal Architect, MCP & A2A Integration.”
The Secret Sauce: The Action Button
Skip “Save Contact.” Add a custom Agentic Follow-up button instead.
How it works: the button triggers a lightweight MCP client that instantly sends your technical portfolio and a link to book a 15-minute discovery call. No friction, no manual follow-up. The agent handles the handshake after the handshake.
2. The Consultancy Hub: Landing Page Layout
For an enterprise consultancy, move away from “chatbots” and toward Context Engineering. If you’re an Elixir developer, your site should be lightning-fast — Phoenix LiveView is the natural choice.
Section 1: The Hero
Stop Building Chatbots. Start Building Systemic Intelligence.
We architect secure Model Context Protocol (MCP) gateways and A2A coordination layers that turn fragmented enterprise data into a unified, actionable semantic layer.
CTA: Download the 2026 Enterprise MCP Security Whitepaper
Section 2: The Problem/Solution Matrix
Speak directly to enterprise data access pain points with a clean two-column layout:
| The Old Way (Pre-MCP) | The Boutique Approach (2026) |
|---|---|
| Brittle, custom-coded API connectors | Universal, plug-and-play MCP Servers |
| Ungoverned “Shadow AI” data leaks | OAuth 2.1 governed sandboxes |
| Static, stale RAG embeddings | Real-time, dynamic context fetching |
Section 3: The “Live Context” Demo
This is the closer. Embed a Real-Time MCP Inspector on the page — a terminal-style window where visitors watch a mock agent request data from a legacy database through your custom MCP server.
This demonstrates low latency and auditability — the two things enterprise CTOs care about most right now. Elixir’s concurrency model makes this trivial to build and impossible to fake.
3. The QR-to-Context Flow
When you’re at a seminar in Miami or San Francisco, don’t send people to a generic homepage. Use a dynamic QR code on your physical badge that appends a Context ID:
yourbusiness.com/connect?event=mcp_summit_2026When they scan it, your landing page greets them with:
“Great meeting you at the MCP Dev Summit! Here is the specific technical brief on Enterprise Data Access we discussed.”
Every touchpoint becomes contextual. Every interaction feels like it was built for them — because it was.
The Open-Source Play
One final thought. If you’re building MCP servers in Elixir, consider open-sourcing a Skeleton MCP Server. The current ecosystem is overwhelmingly Python and TypeScript. An Elixir skeleton would be a massive lead magnet for a consultancy — it positions you as the authority in a space where nobody else is building, and it gives enterprise teams a reason to call you first.
The best business card in 2026 isn’t a card. It’s a running server.