PlayFab MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

What is PlayFab MCP Server?

PlayFab MCP 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 for various functionalities such as item search, player profile lookups, and inventory management.

How to use PlayFab MCP Server?

To use the PlayFab MCP Server, set up your project, add your project details to your LLM client's configuration, and start interacting with PlayFab data naturally.

Key features of PlayFab MCP Server?

  • Search for items using PlayFab's search_items API.
  • Retrieve segment information and player profiles.
  • Manage inventory items and convert PlayFab IDs.

Use cases of PlayFab MCP Server?

  1. Integrating AI assistants with PlayFab services.
  2. Automating player data queries for games.
  3. Enhancing game development workflows with AI.

FAQ from PlayFab MCP Server?

  • What is required to run the PlayFab MCP Server?

You need Node.js 14 or higher and a valid PlayFab account.

  • Is there a specific AI model that works with this server?

The server is designed to support any AI model, currently available as a developer preview.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
JavaScript
License
MIT license

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago