# Platforms

Core ships on four platforms. They share accounts, key management, and the
approval pipeline, but expose different integration surfaces — which one
your users run determines how your software reaches them.

## Core Web — core.app

The wallet as a website: portfolio, trading, staking, DeFi, and the
settings that govern the [MCP agent policy](/docs/core-web/ai-connectors).
No integration API of its own — see
[Core Web dapp connections](/docs/connect-your-dapp/core-web) for what that
means in practice.

## Core Extension

The browser extension, and the main dapp target. Injects the
[EIP-1193 provider](/docs/reference/provider-api), announces via EIP-6963,
supports [hardware wallets](/docs/core-extension/hardware-wallet) and
[WalletConnect sessions](/docs/core-extension/walletconnect). Chrome and
Chromium-based browsers.

## Core Mobile — iOS and Android

Full wallet on the phone. Connects to dapps exclusively through
[WalletConnect](/docs/connect-your-dapp/core-mobile); there is no injected
provider in mobile browsers.

## The MCP server

Not a user-facing platform, but a fourth surface: the
[Core MCP Server](/docs/mcp/overview) lets AI agents operate a wallet under
a [signed policy](/docs/mcp/policy), authenticated with the user's core.app
identity.

## Choosing what to build against

| You are building… | Integrate with |
| --- | --- |
| A web dapp | [EIP-6963 detection](/docs/connect-your-dapp/detect-core) + [WalletConnect](/docs/connect-your-dapp/core-mobile), or a [library](/docs/connect-your-dapp/library-guides) that does both |
| A desktop or non-browser app | [WalletConnect](/docs/core-extension/walletconnect) |
| An AI agent | The [MCP server](/docs/mcp/overview) |
| X/P-Chain tooling | The [`avalanche_*` methods](/docs/connect-your-dapp/avalanche-chains) |