@@ -165,6 +165,40 @@ Use validation files to:
165165
166166Access with ` validation://current ` resource.
167167
168+ ### Saving Your Work
169+
170+ The MCP server works with your AI assistant to help you save schemas and validation files to disk.
171+
172+ ** Exporting Schemas**
173+
174+ Ask your assistant to save the current schema to a file:
175+
176+ > You: "Save my schema to schema.zed"
177+
178+ > You: "Write the current schema to permissions/document-sharing.zed"
179+
180+ The assistant reads from ` schema://current ` and writes the schema to your specified file path.
181+
182+ ** Exporting Validation Files**
183+
184+ Save validation test cases to preserve your permission tests:
185+
186+ > You: "Save the validation file to tests/permissions.yaml"
187+
188+ > You: "Export validation to document-tests.yaml"
189+
190+ The assistant reads from ` validation://current ` and writes the validation YAML to your specified file.
191+
192+ ** Loading Existing Files**
193+
194+ You can also load schemas from existing files:
195+
196+ > You: "Load the schema from schema.zed and apply it to the dev server"
197+
198+ > You: "Read permissions/document-sharing.zed and write it to the MCP server"
199+
200+ The assistant reads your file and uses ` write_schema ` to apply it to the development instance.
201+
168202## Security Considerations
169203
170204### Local Development Only
@@ -253,7 +287,9 @@ netstat -an | findstr 9999
253287When ready to move beyond development:
254288
2552891 . ** Export your schema** : Save the final schema from ` schema://current `
290+ - Ask your assistant: "Save my schema to schema.zed"
2562912 . ** Document permissions** : Create comprehensive validation files
292+ - Ask your assistant: "Save validation to tests/permissions.yaml"
2572933 . ** Deploy SpiceDB** : See [ SpiceDB deployment guide] ( # )
2582944 . ** Connect your application** : Use [ SpiceDB client libraries] ( # )
2592955 . ** Import relationships** : Migrate test relationships if appropriate
0 commit comments