Does this work with Claude Code specifically, or just Claude.ai?

Both. The MCP server and CLI approach work in Claude Code, and the MCP server also works in Claude.ai and Claude Cowork.

Is this only for Claude?

No. MCP is an open protocol and the Public API is platform-agnostic, other assistants that support MCP or can call an API can connect the same way.

Do I need to be a developer to use this?

Not for the chat-based approach. If you can describe what you want in plain language, Claude can usually carry it out through the MCP server.

Claude × AppShare

Ship a Build Without Leaving the Chat

Tell Claude to push a build, check who's downloaded it, or spin up a Quick Release, and it happens right there in the conversation. No dashboard tab, no context switch.

Connect to Claude Now

Three Ways In

Pick However You Already Work

MCP Server

Connect Claude to the AppShare MCP server, and push builds or check release stats, right in chat.

Public API

Build your own automation on AppShare's Public API, and let Claude call it inside a larger workflow.

Claude Code + CLI

Claude Code can run AppShare CLI as a shell command, so build and share become one instruction.

From Instruction to Install Link

Connect

Add the AppShare MCP server to Claude, or set your API key as an environment variable for Claude Code.

Ask

Tell Claude what you want, a build pushed, stats checked, an expiry set.

Claude Acts

It calls the right tool, MCP, API, or CLI, and carries out the actual request.

Release Created

The install link, QR code, or data comes straight back into the conversation.

Do It Right

A Skill Built for AppShare

Not a one-off prompt, a Skill: packaged instructions Claude reads before acting, so it knows AppShare's commands instead of guessing.

Create your own custom skill on Claude suited to your needs and environment.

name: appshare
description: Use when uploading, releasing, or
checking status of AppShare builds. Covers the
AppShare CLI, MCP server calls, and Public API.

AppShare Skill

Uploading a build

Run appshare <file-path> --app-id <slug>
after building. Omit --app-id for a
one-off Quick Release.

Checking release stats

Use the MCP server or Public API to fetch
install counts, expiry, and status.

Setting release options

Pass flags for expiry and password
where the CLI supports them.

The Case

Less Tab-Switching, More Shipping

Ask instead of click

How many installs did the last release get, beats opening the dashboard to check.

Build and ship in one breath

Claude Code can compile the app and push it to AppShare as a single instruction.

No new syntax to learn

If you can describe what you want, Claude can usually do it, no CLI flags to memorize.

Fits into what you're already doing

Claude Code sessions that build your app can now also finish the job by sharing it.

Not Just Claude

Works with More than Just One LLM

MCP is an open protocol, and the Public API doesn't care which assistant is calling it. If your team already works with Gemini, ChatGPT, or Kimi K3, the same AppShare MCP server and API are there to connect to, this page just happens to be about Claude specifically.

Gemini

Connect through the same MCP server, or call the Public API directly instead.

ChatGPT

Works the same way, MCP support or direct API calls, depending on your setup.

Kimi AI

Also MCP-compatible, so the exact same connection method applies here too.

FAQ

Got Questions?

Do I need the MCP server, or can I just use the API?

Either works. MCP is the more direct route for chat-based use, the Public API is better if you're building your own automation around it.

Can Claude Code build my app and push it to AppShare in one go?

Yes. Claude Code can run your build command and the AppShare CLI upload as part of the same instruction.

What is the AppShare Skill, exactly?

A packaged set of instructions that teaches Claude AppShare's actual commands and conventions, so results stay consistent instead of depending on how well you explained it that session.