You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat: enhance MCP server, README, and AI discoverability
- Enhanced MCP README with installation guides for Claude, Cursor, Windsurf
- Added get_best_practices and get_ar_setup tools to MCP server
- Expanded package.json keywords for npm discoverability
- Enhanced README with better getting started guide
- Improved llms.txt in MCP package
https://claude.ai/code/session_01Jf51Xrp1Fs4ByDmchZfGQ5
The official [Model Context Protocol](https://modelcontextprotocol.io/) server for **SceneView** — giving AI assistants deep knowledge of the SceneView 3D/AR SDK so they generate correct, compilable Kotlin code.
8
10
11
+
---
12
+
9
13
## What It Does
10
14
11
-
When connected to an AI assistant (Claude, GPT, Cursor, Windsurf, etc.), this MCP server provides:
15
+
When connected to an AI assistant (Claude, Cursor, Windsurf, etc.), this MCP server provides **10 tools** and **2 resources** that give the assistant expert-level knowledge of the SceneView SDK:
16
+
17
+
### Tools
12
18
13
19
| Tool | Description |
14
20
|------|-------------|
15
-
|`get_node_reference`| Complete API reference for any SceneView node type |
21
+
|`get_node_reference`| Complete API reference for any SceneView node type (22+ types) |
16
22
|`list_node_types`| List all available node composables |
17
-
|`validate_code`| Check SceneView code for 15+ common mistakes |
18
-
|`get_sample`| Get complete, compilable sample code for any scenario |
19
-
|`list_samples`| Browse 15 sample applications by tag |
20
-
|`get_setup`| Get Gradle + manifest setup for 3D or AR |
21
-
|`get_migration_guide`| Full v2→v3 migration instructions |
23
+
|`validate_code`| Check SceneView code for 15+ common mistakes before presenting it |
24
+
|`get_sample`| Get complete, compilable sample code for any of 14 scenarios |
25
+
|`list_samples`| Browse all sample applications, optionally filtered by tag |
26
+
|`get_setup`| Gradle + manifest setup for 3D or AR projects |
27
+
|`get_migration_guide`| Full SceneView 2.x to 3.0 migration instructions |
@@ -43,20 +117,71 @@ Add to your MCP configuration:
43
117
}
44
118
```
45
119
46
-
### Cursor / Windsurf / Other MCP Clients
120
+
### Other MCP Clients
121
+
122
+
The server communicates via **stdio** using the MCP protocol. Start it directly:
47
123
48
124
```bash
49
125
npx sceneview-mcp
50
126
```
51
127
52
-
The server communicates via stdio using the MCP protocol.
128
+
---
53
129
54
-
###Verify Installation
130
+
## Verify Installation
55
131
56
132
Once connected, ask your AI assistant:
133
+
57
134
> "List all SceneView node types"
58
135
59
-
It should return the full list of 22+ composable nodes.
136
+
It should return the full list of 22+ composable nodes. If it does, the MCP server is working.
137
+
138
+
---
139
+
140
+
## Tool Examples
141
+
142
+
### Get a sample project
143
+
144
+
> "Show me an AR tap-to-place sample with SceneView"
145
+
146
+
The assistant will call `get_sample("ar-model-viewer")` and return a complete, compilable Kotlin composable with all imports and dependencies.
147
+
148
+
### Validate generated code
149
+
150
+
> "Create a 3D model viewer and validate the code"
151
+
152
+
The assistant will generate the code, then call `validate_code` to check it against 15+ rules (threading, null safety, API correctness, lifecycle) before presenting it.
153
+
154
+
### Look up a node's API
155
+
156
+
> "What parameters does LightNode accept?"
157
+
158
+
The assistant will call `get_node_reference("LightNode")` and return the exact function signature, parameter types, defaults, and a usage example.
159
+
160
+
### Get setup instructions
161
+
162
+
> "How do I set up ARCore with SceneView in my project?"
163
+
164
+
The assistant will call `get_ar_setup` and return the complete Gradle dependency, AndroidManifest.xml changes, session configuration options, and working AR starter templates.
165
+
166
+
### Get best practices
167
+
168
+
> "What are the performance best practices for SceneView?"
169
+
170
+
The assistant will call `get_best_practices("performance")` and return guidance on model optimization, runtime performance, environment/lighting setup, and common anti-patterns.
171
+
172
+
### Check the roadmap
173
+
174
+
> "Does SceneView support iOS?"
175
+
176
+
The assistant will call `get_platform_roadmap` and return the current multi-platform status and future plans.
177
+
178
+
### Migrate from v2 to v3
179
+
180
+
> "I'm upgrading from SceneView 2.x. What changed?"
181
+
182
+
The assistant will call `get_migration_guide` and return every breaking change with before/after code examples.
183
+
184
+
---
60
185
61
186
## Why Use This?
62
187
@@ -74,6 +199,54 @@ It should return the full list of 22+ composable nodes.
74
199
- Validate code against 15+ rules before presenting it
75
200
- Provide working sample code for any scenario
76
201
202
+
---
203
+
204
+
## Troubleshooting
205
+
206
+
### "MCP server not found" or connection errors
207
+
208
+
1. Ensure Node.js 18+ is installed: `node --version`
209
+
2. Test the server manually: `npx sceneview-mcp` — it should start without errors and wait for input
210
+
3. Restart your AI client after changing the MCP configuration
211
+
212
+
### "npx command not found"
213
+
214
+
Install Node.js from [nodejs.org](https://nodejs.org/) (LTS recommended). npm and npx are included.
215
+
216
+
### Server starts but tools are not available
217
+
218
+
- In Claude Desktop, check the MCP icon in the input bar. It should show "sceneview" as connected.
219
+
- In Cursor, check **Settings > MCP** and verify the server shows a green status.
220
+
- Try restarting the MCP server by restarting your AI client.
221
+
222
+
### Stale data from `sceneview://known-issues`
223
+
224
+
GitHub issues are cached for 10 minutes. Wait for the cache to expire or restart the server.
225
+
226
+
### Validation false positives
227
+
228
+
The `validate_code` tool uses pattern matching and may flag valid code in some edge cases. If a validation warning seems incorrect, review the rule explanation in the output — it includes the rule ID and a detailed explanation.
229
+
230
+
### Firewall or proxy issues
231
+
232
+
The only network call is to the GitHub API (for `sceneview://known-issues`). All other tools work fully offline. If you are behind a corporate proxy, set the `HTTPS_PROXY` environment variable:
0 commit comments