back4app.com
Back4app exposes a Parse REST API at `https://parseapi.back4app.com` authenticated with `X-Parse-Application-Id` + `X-Parse-REST-API-Key`, a Parse GraphQL API at `https://parseapi.back4app.com/graphql` authenticated with `X-Parse-Application-Id` + `X-Parse-Client-Key` (optionally plus `X-Parse-Session-Token` for logged-in user context), and a stdio MCP server run via `npx @back4app/mcp-server-back4app` authenticated with a Back4app account key/personal access token.
- Back4app MCP server packagediscovered
- Back4app Parse REST APIdiscovered
- Back4app Parse GraphQL APIdiscovered
Create a Back4app app, then in your app dashboard open App Settings → Security & Keys to copy the Application ID. The quickstart says you always need the Application ID plus another key appropriate to the SDK/API you use. Start from the Quickstart.
Log into Back4app, open the Hello, [username] menu, go to Account Keys, create a new key, and copy it securely; the docs note you won't be able to see it again. This token is used by Back4app MCP and the Back4app CLI. See Model Context Protocol (MCP) and Command Line Interface Setup.
This is an end-user session token obtained by logging a user in or signing a user up through the Parse API, then sending it in X-Parse-Session-Token for user-context operations. This is documented for GraphQL, but it is an application user's credential rather than a developer-issued integration credential. See Authenticating a logged user through the Parse GraphQL API.
conventions · 1/7 published
- integrations.json——
- llms.txt✓https://back4app.com/llms.txt
- API catalog✗
/.well-known/api-catalog - OpenAPI document✗
/api/schema/, /openapi.json, /swagger.json, /api/openapi.json, or /v1/openapi.json - MCP server card✗
/.well-known/mcp/server-card.json - OAuth protected resource✗
/.well-known/oauth-protected-resource - Agent card✗
/.well-known/agent-card.json - Agent skills✗
/.well-known/agent-skills/index.json
Publish these signals → /publishing