---
title: Appside MCP server
nav: MCP
order: 9
---
# Appside MCP: game web store docs for your coding agent

Appside's public MCP server lets compatible coding agents search developer documentation, retrieve SDK examples and read published pricing. Its three tools are read-only: they do not create stores, publish sites or process payments.

## Connect your coding agent

Use **https://appside.build/mcp** with a client that supports remote Streamable HTTP. No account, API key or payment credentials are required. For clients supporting this URL configuration:

```json
{"mcpServers":{"appside":{"url":"https://appside.build/mcp"}}}
```

Configuration fields vary by client. Choose its remote HTTP connector, rather than a local executable or SSE-only connection. See the [MCP remote connection guide](https://modelcontextprotocol.io/docs/develop/connect-remote-servers).

## Available tools

| Tool | Arguments | Result |
|---|---|---|
| `search_docs` | `query`: 1–200 characters | Up to five documentation excerpts with source links |
| `get_sdk_snippet` | `platform`: one of the names below | SDK README examples and documented verification status |
| `get_pricing` | An empty object | Published fee, fee basis and source URL |

Supported platform names: `web`, `ios`, `android`, `unity`, `react-native`, `flutter`, `node`, `python`. Available examples do not mean every platform has been tested on a device: check the returned status and [SDK verification details](/docs/sdks/).

The server also exposes **https://appside.build/llms.txt** as a read-only MCP resource. For clients without MCP, use [the documentation index](/llms.txt), [full developer text](/llms-full.txt) or this page's **View as Markdown** link.

## Try a useful integration prompt

Ask your agent: “Search Appside's docs for signed webhooks, get the Node SDK example, and explain how my backend grants each order only once. Include source links and identify any test-mode limitations.”

Expected sequence: `search_docs` with `{"query":"signed webhooks"}`, followed by `get_sdk_snippet` with `{"platform":"node"}`. Read the linked [webhook guide](/docs/webhooks/) before integrating. A return-to-game link or client callback is a UI hint; grant items only after verified backend delivery.

## Verify the connection

The endpoint speaks protocol **2025-03-26**. This initialization request can be run without credentials:

```sh
curl https://appside.build/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  --data '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"docs-check","version":"1.0.0"}}}'
```

A public endpoint check on **2026-10-24 UTC** returned server name `appside-mcp`, version `0.1.0`, all three tools above, and a successful `get_pricing` response. You can reproduce the pricing call:

```sh
curl https://appside.build/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  --data '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"get_pricing","arguments":{}}}'
```

The text content contains `feePercent: 3.9`, `basis: "per successful payment"`, and zero setup, subscription and minimum fees, with a source link. This is published pricing information, not a payment-processing tool or confirmation that a merchant is approved for live payments. See [testing and payment status](/docs/testing/).

## Limits and troubleshooting

- Stateless JSON POST responses; notification POSTs return an empty 202. GET returns 405: there is no optional SSE stream, session state or server-initiated messaging.
- Set both headers shown above. Missing JSON content type returns 415; missing accepted response types returns 406.
- Limits: 64 KiB messages, 20-message batches, 10s body deadline, 60 requests/minute per socket IP and 600/minute globally. Behind the edge proxy, clients may share a socket bucket.
- A 429 response includes `Retry-After: 60`. Wait before retrying instead of polling repeatedly.
- There is no cross-origin browser CORS access. If an Origin header is present, it must match an allowed HTTPS site origin. Connect from your MCP client's server-side transport.

## Discovery and next steps

Find the public [Appside Developer Docs listing on Glama](https://glama.ai/mcp/connectors/build.appside/appside-developer-docs). The listing is live; the ownership claim is pending. The official MCP registry entry and npm package are not published, so use the remote endpoint above.

Start with the [first-purchase quickstart](/docs/quickstart/), connect [player identity](/docs/player-tokens/), then implement [signed fulfillment](/docs/webhooks/). Publishers with an Appside account create and manage the store in the [Appside builder](https://app.appside.build/build); to see the app-to-store journey first, open the [live demo](https://demo.appside.build/demo).