Quickstart

Deploy the AppXen Platform appliance from AWS Marketplace into your own AWS account, then sign in to its console:

1. Open the stack's ConsoleUrl output. Accept the self-signed certificate warning unless you set a domain.
2. Sign in as the AdminEmail you gave the stack, using the stack's InstanceId output as the temporary password. The console makes you change it at once.
3. Check the health panel on the Home page. It shows your AWS identity, the services, and Amazon Bedrock access for each model.

The full steps are in First sign-in. Amazon Bedrock model access, a one-time step that the Claude models need before Agent Orchestrator workflows can use them, is a separate prerequisite: see Amazon Bedrock model access.

Once signed in, open API Keys (under General in the console sidebar). Click "Create Key" to generate a new API key.

Your API key will look like: axgw_live_k1_xxxxxxxxxxxx

Go to MCP Gateway → Gateway in the console sidebar and click "Add Server" in the Custom Servers section. You can add any remote MCP server that supports SSE or Streamable HTTP transport.

For example, to add the GitHub MCP server:

Check out the Connecting Servers guide for more examples.

Use your API key to authenticate requests to the gateway. The gateway aggregates all your connected servers into a single MCP endpoint.

List Available Tools

curl -X POST https://<your-appliance-host>/mcp \
  -H "Authorization: Bearer axgw_live_k1_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","method":"tools/list","id":1}'

Call a Tool

curl -X POST https://<your-appliance-host>/mcp \
  -H "Authorization: Bearer axgw_live_k1_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "method": "tools/call",
    "params": {
      "name": "github__get_me",
      "arguments": {}
    },
    "id": 2
  }'

Tools are namespaced with the server alias (e.g., github__get_me). This prevents naming conflicts when you have multiple servers connected.