Banking Assistant (Metabind demo)

Metabind Finance demo

A personal-finance assistant with no chat transcript. The app asks one question on launch and uses the rendered answer as its home screen; every follow-up opens on a purpose-built surface. The same assistant runs natively on iOS and Android from one MCP App definition.

https://github.com/user-attachments/assets/9a840b88-dc88-4ab4-927e-0a8dc651dbe3

The Finance demo, running in the iOS app.

What is Metabind

Metabind builds agents that answer in your product's own UI, not in a chat window: interactive interfaces that take customers straight to what they came for, in the brand they already know. It's built from the UI, design system, and APIs the app already has. No rewrite. It's governed, rendering only components you've approved, enforced on every render. And it's hosted: you define the tools, we run the server. The same agent runs inside your own iOS, Android, and web apps, and across Claude, ChatGPT, and every MCP host, on the open MCP standard.

This demo shows the inside-your-own-app half, rendered as real native SwiftUI and Jetpack Compose through the Assistant SDK.

Start free at metabind.ai · Read the docs

What this demo is

Finance is a deliberately transcript-free assistant. One question is asked on launch — "Where did my money go this month?" — and its rendered MCP result is the home screen. Later questions come from a pill rail at the bottom and open in sheets. Each turn is routed to a purpose-built surface instead of scrolling by in a message list.

It's the opposite shape to the Retail demo, where the conversation itself is the product. Same SDKs, two shapes — read both before deciding which one your product is.

Working through this README end to end, you get:

• The Finance MCP project — spending breakdowns, transaction lists, subscriptions, and net-worth trends as BindJS components over synthetic data — installed as a project in your own Metabind organization.
• The iOS app running against that project.
• The Android app running against the same project.

All financial data is synthetic. Nothing here connects to a real bank, reads a secret, or calls an external host.

What's in this folder

Before you start

• A Metabind account and organization — sign up at metabind.ai/signup.

• The metabind CLI, 0.9.0 or newer:

  sh

  brew install metabindai/tap/metabindmetabind --version

• An LLM provider API key (Anthropic, OpenAI, or Google). The Metabind Agent proxy holds it server-side and runs the conversation with it — the apps never ship a provider key.

• For iOS: Xcode 26+ (the app targets iOS 17+).

• For Android: Android Studio, JDK 17+, and GitHub Packages credentials — GitHub requires authentication even to read a public package.

Part 1 — install the MCP project

Run these from this directory (finance/).

1. Sign up at metabind.ai if you haven't already — that creates your account and organization. Then sign in to the CLI and pick the organization to install into:

   sh

   metabind auth loginmetabind org listmetabind use --clearmetabind use --org <org-id>

   use --clear matters if you have used the CLI before. install in step 3 creates a project only when none is bound, and installs into the bound one otherwise — after the Retail demo, for instance. Setting the org alone does not release a project bound earlier; metabind status shows the active scope.

2. See what the tree declares before creating anything:

   sh

   metabind inspect --dir mcp

   Finance declares no secrets and no outbound calls — inspect is how you confirm that from the tree itself.

3. Install:

   sh

   metabind install --dir mcp --name "Banking Assistant" --yes

   install mints fresh ids for everything it creates, records where the tree came from, and creates drafts only — nothing serves traffic until you publish. Copy the project id it prints.

4. Scope the CLI to the new project and set the agent's LLM key:

   sh

   metabind use --project <project-id>echo $ANTHROPIC_API_KEY | metabind agent set --provider anthropic --api-key-stdin

5. Publish:

   sh

   metabind publish

6. Mint the API key the apps sign in with:

   sh

   metabind api-key create --name "Banking Assistant"

   Copy the value now — it is shown once, at creation. One Metabind API key authenticates both the Agent proxy and the MCP server.

7. Optionally, apply the project settings and thumbnail. install creates the components and tools; the settings in mcp/metabind.jsonc — the MCP instructions and the agent system prompt — are applied by push:

   sh

   metabind asset upload mcp/assets/files/project-thumbnail.pngmetabind sync repair --out mcp --org <org-id> --project <project-id>metabind push --out mcpmetabind project get <project-id>metabind project update <project-id> \  --data '{"settings":{"thumbnailUrl":"<url from asset upload>"}}'metabind publish

   push rewrites the tool drafts, so publish once more to release them.

   The project get is not decoration. project update refuses to write an entity the CLI has not read recently, so that it can tell the project hasn't moved underneath you:

   CONFLICT: Refusing project update <project-id>: no recent read recorded.

   A project you just installed has never been read, so the first update trips this without it.

   Set thumbnailUrl after pushing, not before: project update replaces nested settings objects rather than merging them, so writing settings.mcp here would drop the instructions push just applied.

[!NOTE] Configure the clients with the org and project ids that install printed — the stable internal ids, not the organization slug.

Part 2 — run the iOS app

1. Create the gitignored local configuration from its template:

   sh

   cd applecp Config/Local.xcconfig.example Config/Local.xcconfig

2. Fill in the ids from Part 1:

   xcconfig

   FINANCE_DEMO_ORG_ID = your_stable_internal_org_idFINANCE_DEMO_PROJECT_ID = your_project_id

   Leave FINANCE_DEMO_API_KEY empty — you'll enter the key on first launch. FINANCE_DEMO_BUNDLE_ID and DEVELOPMENT_TEAM matter only for signed device builds.

3. Open the project and run it (⌘R) on an iOS 17+ simulator:

   sh

   open MetabindFinanceDemo.xcodeproj

4. Enter your Metabind API key on the launch screen and tap Start. The home screen loads by asking "Where did my money go this month?". Tap a suggested follow-up or Ask anything to open the next answer in a sheet.

For signing, Xcode Cloud, TestFlight, and how the integration works, see the iOS app's README.

Part 3 — run the Android app

1. Give Gradle credentials for GitHub Packages, either as environment variables (GITHUB_ACTOR / GITHUB_TOKEN) or in ~/.gradle/gradle.properties:

   properties

   gpr.user=your-github-usernamegpr.key=your-github-token

2. Create the gitignored local configuration from its template, and fill in the same ids from Part 1:

   sh

   cd androidcp local.properties.example local.properties

3. Build, install, and launch on a device or emulator (API 26+, with the WebView JavaScript Sandbox available — BindJS runs component code in androidx.javascriptengine):

   sh

   ./gradlew :app:installDebugadb shell am start -n ai.metabind.finance.demo/.MainActivity

4. Enter your Metabind API key and tap Start — the same first-launch flow as iOS.

For the Compose architecture and the deliberate divergences from the iOS app, see the Android app's README.

Where to next

• Edit the MCP project — change a component, validate, push, and publish, with the reconcile scripts that keep every card's figures agreeing.
• The Retail demo — the same SDKs with the opposite shape: the transcript is the product.
• Metabind for Apple and Metabind for Android — SDK installation and API reference.
• docs.metabind.ai — the full guides.

License

Apache 2.0. See LICENSE and NOTICE at the repository root; apple/, android/, and mcp/ carry their own copies because they are meant to be copied out as starters.