I just shared a video of our Snappy Xano MCP on LinkedIn and would really appreciate some engagement! I tried something different with the demo - set it to piano music and just let the AI go through building! If you could: - Give it a watch - Drop a like/comment on LinkedIn I would very much appreciate it! Linkedin Post Thanks for being part of this community - you all have been watching this come together from day one!

Hey, I'm working in n8n and trying to pass an array of values to the JSON body of the HTTP Request node, but I keep getting a comma-separated string instead of an actual array. I managed to fix it by adding square brackets and using .map() to wrap each item in quotes: "keywords": [{{ $json.output.keywords.map(k => `"${k}"`) }}] It works, but I'm wondering — is there a simpler or more elegant way to achieve this?

I've been constantly deploying major updates to Snappy’s MCP tool, now featuring 98 tools covering virtually the entire Xano API surface! Here’s an overview of the current Snappy MCP tools: Core Tools (4) 1. xano_auth_me - Get current auth status 2. whoami - Get current user info 3. xano_list_instances - List available Xano instances 4. xano_get_instance_details - Get instance configuration Database Tools (5) 5. xano_list_databases - List all workspaces/databases 6. xano_get_workspace_details - Get workspace information 7. xano_list_workspace_branches - List workspace branches 8. xano_export_workspace - Export workspace configuration 9. xano_export_workspace_schema - Export workspace schema only Table Management Tools (13) 10. xano_list_tables - List all tables in workspace 11. xano_get_table_details - Get table metadata 12. xano_get_table_schema - Get table field definitions 13. xano_create_table - Create new table 14. xano_update_table - Update table properties 15. xano_delete_table - Delete a table 16. xano_get_table_with_script - Get table XanoScript definition 17. xano_update_table_with_script - Update table via XanoScript 18. xano_truncate_table - Remove all records from table 19. xano_get_specific_schema_field - Get single field details 20. xano_replace_entire_schema - Replace complete table schema 21. xano_update_table_autocomplete - Configure autocomplete 22. xano_update_table_meta - Update table metadata Field Management Tools - Expanded (31 field types) 23. xano_add_field_to_schema - Add field to table (supports all types below) 24. xano_rename_schema_field - Rename existing field 25. xano_delete_field - Remove field from table 26. xano_create_table_reference_field - Create foreign key field - integer reference - uuid reference 27. xano_create_basic_field - Create simple field types: - text - Text field with max_length, min_length validation - int - Integer field with min, max validation - bool - Boolean field (true/false) - timestamp - Timestamp field with default_now option

I'm using Robert's Claude MCP tools to build 30+ tables for a new system. I wanted to test out what is possible and found a few limitations, such as being unable to create table reference fields (I tried, but they aren't right). With others, it cannot initially select all options (like adding Enum values) during the xano_create_table, but can alter them using the update_table_with_script afterwards. It also seemed to be unaware of Xano's default fields and tried to add a 'created_at' field more than once. So with a bit of training, my Claude session now has a set of rules for making all my tables, which it named itself as "Table-Building Machine". Here is its self-declared workflow: 🤖 Complete Table-Building Machine Workflow v4.0 📋 Enhanced Process for Every Table: 1. 🏗️ Create Base TableUse xano_create_table (defaults to int primary key)Includes: id (int) + created_at (timestamp) - Xano auto-adds these 2. 🔑 Set Primary Key Type (if UUID needed)Use xano_update_table_with_script to change int id → uuid idSkip this step if sequential int is fine 3. 📝 Add Standard Tracking Fieldslast_edited_at - timestamp (optional/nullable)last_edit_user_id - int (optional/nullable)Use xano_add_field_to_schema for these 4. ➕ Add Regular Custom FieldsAll fields default to: required = false, nullable = trueOnly set required = true when you explicitly specify "(required)"Use xano_add_field_to_schema for: text, int, email, bool, decimal, etc. 5. 💰 Add Currency Fields (£)Use decimal field type for all monetary valuesEnsures accurate financial calculations without rounding errorsExamples: pay_rate, charge_rate, invoice_amount, total_amount 6. 🔗 Add URL FieldsUse text field type with URL validation patternApply regex pattern: ^https?:\/\/(www\.)?[-a-zA-Z0-9@:%._\+~#=]{1,256}\.[a-zA-Z0-9()]{1,6}\b([-a-zA-Z0-9()@:%_\+.~#?&//=]*)$Examples: website_url, logo_image, video_link, zoom_url 7. 📷 Add Image Fields Only ✅ NEW!Use xano_add_field_to_schema for image type onlyOther storage types (file, video, audio) must use script method 8. 🎯 Add ENUM Fields (if any)Use xano_update_table_with_script methodAdd ENUM fields with proper values arrayEnsures values are stored correctly in Xano 9. 📦 Add Object Fields (if any)First add basic object field with xano_add_field_to_schema (type: object, style: list)Then use xano_update_table_with_script to add custom columnsSupports list configuration with multiple custom columns 10. 📁 Add Storage Fields (file, video, audio) ✅ NEW!Use xano_update_table_with_script method for: file, video, audio typesXanoScript syntax: file ?field_name?, video ?field_name?, audio ?field_name?Image fields can be added earlier via regular method 11. 🏁 Table Creation CompleteComplete table with all 4 standard fields + custom fieldsProper field types, validation, and complex data structuresReady for YOUR manual table reference field additions 12. 🔗 Manual Table Reference Addition ✅ NEW STEP!YOU manually add table reference fields in Xano UIThese create proper dropdown relationships between tablesEssential for data integrity and user experience 13. 🚀 API Development ReadyAfter table references are complete, ready for CRUD API creationFull validation, relationships, and business logic support

I started using Snappy MCP for the first time yesterday so I might be doing something wrong, but from Xano I used my MCP secret key to establish the connection with the snappy MCP, everything connected just fine and I was able to get Claude to look into my database and API end points. The thing I struggled with was getting Claude to create API end points or custom function stacks. It’s handled generating new tables and schemas with no problem but when it comes to creating an API end point, 2 times it said that it had created the API end point but then when going into my instance there was no API endpoint created when I mentioned this to Claude it simply said oh yes, I couldn’t do that because I couldn’t work out the syntax. I just wondered if anyone else has had this problem and if I’m doing anything wrong. P.S I love snappy I can see it been super useful in the coming time to get tables and API points created in a breeze thank you so much.