Playfab MCP Server

Playfab mcp server lets Claude, Cursor and other MCP clients work with Playfab directly. PlayFab MCP Server.

What Playfab does

This server is a middleware that enables large language models (like Claude and VS Code) to interact directly with PlayFab services. Acting as a secure and efficient translator, it connects your AI assistant with various PlayFab functionalities, such as item search, segment inquiries, player profile lookups, inventory management, and PlayFab ID conversion.

Tools it exposes

Once connected, the assistant can call these 7 tools directly:

• ESLint — Configured for TypeScript with recommended rules for code consistency
• Prettier — Automatic code formatting with project-specific settings
• TypeScript — Strict mode enabled for enhanced type safety
• Jest — Testing framework configured for TypeScript
• Prerequisites — The Prerequisites tool exposed by this server
• Testing — Tests are written using Jest and can be found in tests directories or files with .test.ts extension. Run tests before committing changes to ensure code
• Types — The Types tool exposed by this server

Installing the playfab mcp server

Setup follows the standard MCP pattern: clone or install the server, then register it in your client's configuration file and restart the client. The configuration snippets on this page cover Claude Desktop, Claude Code and Cursor.

Configuration

Before the server will start you need to supply 4 environment variables: PLAYFAB_TITLE_ID, PLAYFAB_DEV_SECRET_KEY, PERSONAL_ACCESS_TOKEN, GITHUB_TOKEN. Keep credentials in your client's env block or a secrets manager rather than committing them.

Requirements

• Node.js 18 or higher. - A valid PlayFab account (obtain your Title ID and Developer Secret Key via PlayFab Game Manager). - A supported LLM client such as Claude Desktop.

Where it fits

Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. Playfab sits in that group, and the shape of its toolset — ESLint, Prettier, TypeScript among others — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

• This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
• It will not start until its required credentials are present, so set those before wondering why the tools never appear.
• With 7 tools exposed, expect a noticeable bump in prompt size — disable it in projects that never use Playfab.
• Maintained by akiojin, written in Python.
• MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the playfab mcp server actually does with your data.
• Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.