Skip to main content

Keyban MCP Server — Overview

Integrate Keyban’s backend directly into your AI workflows. The Model Context Protocol (MCP) server lets assistants discover your applications, update loyalty programs, manage digital product passports, and more, without touching the admin UI.

What the server provides​

  • Operational tools for common admin actions (create/update/delete applications, manage loyalty settings, control DPP claim permissions, maintain point-of-sale data).
  • Rich resources that expose read-only views of the same entities your dashboards rely on.
  • Argument completion so assistants can suggest valid IDs, emails, and other parameters while you type.

Who should use it?​

  • Product and ops teams who want to adjust Keyban data in real time from MCP-enabled assistant.
  • Developers automating workflows or building custom tooling on top of Keyban’s APIs.
  • Support engineers who need quick insights or targeted updates without navigating multiple dashboards.

If you only need to read data, stick to the resources. If you need to make changes, ensure your API key has the required permissions, every action maps directly to the underlying REST endpoint.

  • Quick Start: Connect an assistant (Codex + MCP Inspector) in minutes