Game Development

multimate.net

Provides Multimate game development platform documentation, engine version and release notes, and account game listings.

1 endpoint14 known toolsFirst detected September 17, 2026Last detected September 17, 2026

ENDPOINT 1

https://multimate.net/mcp

No auth detected

MCP server metadata

Name: multimate
Version: 1.0.0

Capabilities

tools.listChangedresources.listChanged

Known tools 14

search_docs

Search the Multimate platform documentation (feel contract, config.js options, netcode, lobby, deploys, server authority).

Inferred read-only

get_doc

Fetch a full Multimate documentation page as markdown.

Inferred read-only

get_engine_version

Current Multimate engine version and SDK channel, plus the latest release notes entry.

Inferred read-only

get_changelog

Recent Multimate engine release notes, newest first.

Inferred read-only

my_games

List the games on your Multimate account (requires an MCP token): deployed version, engine version at deploy, authority mode, play URL, repo URL — plus the current engine version to spot games needing a redeploy.

Inferred read-only

game_status

Status of one of your games (requires an MCP token): version stamps, authority, live preview branches, and recent deploy/bug-report activity including version-gate rejections.

Inferred read-only

bug_reports

List recent player bug reports for one of your games (requires an MCP token).

Inferred read-only

bug_report

Fetch one full bug-report trace (requires an MCP token): meta, 1Hz net stats, event ring, and sampled world snapshots for the ~30s before the report.

Inferred read-only

leaderboard

Top persisted leaderboard scores for one of your games (requires an MCP token).

Inferred read-only

live_room_stats

Live room occupancy for your games (requires an MCP token): room codes plus player/spectator COUNTS only — never player names or ids.

Inferred read-only

deploy_status

Deploy + release state for one of your games (requires an MCP token): deployed version vs the current engine, hosted/active/published flags, any pending "Launch on Multimate" request, the last ~10 deploy-family audit events (deploy/publish/unpublish/failures), and the latest nightly playtest verdict.

Potential side effects

latest_playtest

Latest nightly synthetic-playtest result for one of your games (requires an MCP token): pass/fail with the per-check breakdown (loaded, canvas, animating, crash-free) and captured errors.

Inferred read-only

sound_table

Public sound-slot table for a hosted game: every declared sfx slot with its hint, when to play it, and whether audio is assigned and wired (connected).

Inferred read-only

skin_table

Public skin-slot table for a hosted game: every declared skin slot with its hint, states, and whether a sprite sheet is assigned and wired (connected).

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.multimate]
url = "https://multimate.net/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "multimate": {
      "type": "http",
      "url": "https://multimate.net/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: multimate
Remote MCP URL: https://multimate.net/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "multimate": {
      "url": "https://multimate.net/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "multimate": {
      "type": "http",
      "url": "https://multimate.net/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "multimate",
  "transport": "streamable-http",
  "url": "https://multimate.net/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.