glitchless-mcp 0.1.0 → 0.1.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/package.json +15 -6
- package/src/index.js +3 -3
package/package.json
CHANGED
|
@@ -1,18 +1,27 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "glitchless-mcp",
|
|
3
|
-
"version": "0.1.
|
|
4
|
-
"
|
|
3
|
+
"version": "0.1.2",
|
|
4
|
+
"mcpName": "io.github.glitchless-gg/glitchless",
|
|
5
|
+
"description": "Game observability MCP server: lets coding agents (Claude Code, Codex, Cursor and others) read your game's player telemetry and ranked findings, and run playtest bots.",
|
|
5
6
|
"keywords": [
|
|
6
7
|
"mcp",
|
|
8
|
+
"mcp-server",
|
|
7
9
|
"model-context-protocol",
|
|
8
|
-
"
|
|
10
|
+
"game-observability",
|
|
9
11
|
"observability",
|
|
12
|
+
"gamedev",
|
|
13
|
+
"game-development",
|
|
14
|
+
"threejs",
|
|
15
|
+
"godot",
|
|
16
|
+
"performance",
|
|
17
|
+
"playtesting",
|
|
18
|
+
"ai-agents",
|
|
10
19
|
"coding-agent",
|
|
11
|
-
"claude",
|
|
20
|
+
"claude-code",
|
|
12
21
|
"codex",
|
|
13
22
|
"cursor"
|
|
14
23
|
],
|
|
15
|
-
"homepage": "https://
|
|
24
|
+
"homepage": "https://www.glitchless.gg",
|
|
16
25
|
"bugs": {
|
|
17
26
|
"url": "https://github.com/glitchless-gg/glitchless/issues"
|
|
18
27
|
},
|
|
@@ -39,7 +48,7 @@
|
|
|
39
48
|
"dependencies": {
|
|
40
49
|
"@modelcontextprotocol/sdk": "^1.32.1",
|
|
41
50
|
"zod": "^4.6.7",
|
|
42
|
-
"glitchless-playtest": "^0.
|
|
51
|
+
"glitchless-playtest": "^0.2.0"
|
|
43
52
|
},
|
|
44
53
|
"devDependencies": {
|
|
45
54
|
"esbuild": "^0.28.2"
|
package/src/index.js
CHANGED
|
@@ -4,7 +4,7 @@
|
|
|
4
4
|
// hotspots and version comparisons. Pair it with WebMCP (live tools exposed by the running game)
|
|
5
5
|
// and the agent can go from "players are rage quitting" to a verified fix.
|
|
6
6
|
//
|
|
7
|
-
// claude mcp add glitchless -e GLITCHLESS_URL=http://localhost:7777 --
|
|
7
|
+
// claude mcp add glitchless -e GLITCHLESS_URL=http://localhost:7777 -- npx -y glitchless-mcp
|
|
8
8
|
|
|
9
9
|
import { McpServer } from '@modelcontextprotocol/sdk/server/mcp.js';
|
|
10
10
|
import { StdioServerTransport } from '@modelcontextprotocol/sdk/server/stdio.js';
|
|
@@ -16,10 +16,10 @@ const API_KEY = process.env.GLITCHLESS_API_KEY || '';
|
|
|
16
16
|
const DEFAULT_SERVICE = process.env.GLITCHLESS_SERVICE || '';
|
|
17
17
|
|
|
18
18
|
const server = new McpServer(
|
|
19
|
-
{ name: 'glitchless', version: '0.1.
|
|
19
|
+
{ name: 'glitchless', version: '0.1.2' },
|
|
20
20
|
{
|
|
21
21
|
instructions:
|
|
22
|
-
'Glitchless is observability for
|
|
22
|
+
'Glitchless is observability for games made with Three.js, Phaser, Unity or Godot. Start with glitchless_triage to get ranked, evidence-backed findings for a game, then drill in with glitchless_performance, glitchless_get_error, glitchless_death_hotspots or glitchless_session. Before changing game code, run glitchless_playtest with save_as "baseline"; after the change, run glitchless_playtest again to compare, and treat a FAIL as unfinished work. After shipping a fix (bump the version passed to Glitchless.init), use glitchless_compare_versions to confirm it with real players. If the game is running in a browser with WebMCP connected, its live tools (glitchless_live_performance, glitchless_measure, glitchless_inspect_scene, and game tools such as zoomies_load_level) let you reproduce and measure issues directly. Unity and Godot builds measure themselves when run with --glitchless-measure=SECONDS.',
|
|
23
23
|
},
|
|
24
24
|
);
|
|
25
25
|
|