Using Gia from an AI Assistant
The complete guide to what Gia's Claude connection lets you do — setup, every available tool by account type, and troubleshooting.
What it is
Gia can be connected to AI assistants that speak the Model Context Protocol — claude.ai (as a connector), Claude Desktop, Claude Code, and similar clients. Once connected, you can ask the assistant in plain language to visualize event spaces for you, and it drives Gia on your behalf: it looks up your projects, finds your spaces and rental inventory, and generates styled images of real rooms.
Example asks that work today:
- “Show my ballroom set up for a warm, candlelit winter wedding.”
- “Restyle this space in a coastal palette using items we actually stock.”
- “Take the last render and add more candles and a head table.”
Everything is generated by editing a real photo of the space — the room's structure stays; decor, lighting, layout, and mood change.
Connecting
- claude.ai / Claude Desktop (recommended): add Gia as a custom connector pointing at
https://api.meetgia.ai/mcp/gia. The client discovers the server and walks you through a standard OAuth sign-in: you land on a Gia login page (email/password or Google/Apple), then approve access on a consent screen. No API keys to copy. - First-party / CLI:
https://api.meetgia.ai/mcp/gia-tokenaccepts a regular Gia API bearer token via theAuthorizationheader.
You sign in as yourself. The assistant can only see what your Gia account can see — your organization's projects (including ones shared with you by teammates), your properties, and your inventory. It cannot reach other organizations' work.
What you can do, by account type
The assistant works through a set of named Gia tools — you'll see these names in its activity log as it works. Which tools it gets depends on your account type.
Venue / property owner
The full workflow is available:
- Pick a project — the assistant lists your design projects, each with its design direction (keywords, color palette, style, budget tier) and styles renders consistently with it.
- Pick a space — it lists your property's spaces with their photos (multiple photos = different angles of the same room).
- Find real rentals — it searches your inventory plus your approved rental partners' catalogs, so what it places in a render is something a client can actually book.
- Generate and iterate — renders take roughly 30–90 seconds. Every render lands in the project you chose, so it shows up in your Gia dashboard's project workspace alongside work done in Vibe Studio. You can keep refining a result (“more candles”, “swap the linens to sage”) and composite earlier work — for example, drop a flatlay place setting into a room scene.
| Tool | What it does |
|---|---|
list_projects / get_project | Your design projects, each with its design direction (keywords, palette, style, budget tier) |
list_properties | The properties your organization owns |
list_spaces | A property’s spaces with their photos — the starting images for renders. Usually called with the project, since a project already knows its property |
search_inventory | Real, bookable rental items — your inventory plus your approved rental partners’ catalogs |
list_rental_partners | The rental catalogs your inventory search draws from |
list_project_images | The finished renders and flatlays already in a project, to build on or composite |
generate_image / get_image | Start a render of a space and fetch the result |
Property owners don't get marketplace venue search — you design your own spaces, not other venues'.
Event planner
Planner support is partial today. You design at venues you don't own, so instead of a property list you get marketplace venue search:
| Tool | What it does |
|---|---|
list_projects / get_project | Your projects and their design direction |
search_venues | Find a Gia marketplace venue and pick one of its rooms as the starting image |
search_inventory | Real rental items from your organization’s inventory and rental partners |
list_rental_partners | The rental catalogs your inventory search draws from |
list_project_images | Finished work in a project, to build on or composite |
generate_image / get_image | Start a render — from a marketplace venue room or your own photo of a space (by URL) — and fetch the result |
Attaching venues to projects and browsing a project's custom venues from the assistant is not available yet — do that in your Gia dashboard; the assistant can still generate into the project.
Personal account (no organization)
The marketplace flow:
| Tool | What it does |
|---|---|
search_venues | Find a Gia marketplace venue and pick a room to restyle |
generate_image / get_image | Restyle that room or your own photo (by URL), and keep iterating on a result |
There are no projects, so renders aren't organized into a workspace, and inventory search and compositing of earlier work aren't available from the assistant.
Good to know
- Renders count against your normal Gia generation limits — the same quota as the app, including per-project limits for organization accounts. When you're over, the assistant is told so and will say so.
- Speed over polish: assistant-driven renders currently always use the fast generation backend. For the highest-quality output pipeline, use the app.
- Archived projects are read-only. The assistant can look at them but will refuse to generate into one until it's restored.
- Teammates' work is shared at the project level. Anyone who can see a project in Gia can list and view its renders through the assistant too.
- Your own photos: if you give the assistant an image URL of a space, Gia stores a copy as the generation source.
Not available via the assistant (yet)
- Creating flatlays (place settings) from scratch — compositing an existing flatlay into a scene works.
- Creating or archiving projects, editing inventory, managing your team, or authoring design decks — these stay in your Gia dashboard.
- For planners: attaching a marketplace venue to a project or creating a custom venue.
Troubleshooting
- “A tool is missing” / the assistant says it can't see your organization's features: the tool list is cached by the client when you first connect. If your account changed (e.g. you joined an organization after connecting), remove and re-add the Gia connector; if the list is still stale, that's a known client-side caching limitation — contact support.
- A render seems stuck: generation normally finishes inside two minutes; the assistant polls for it. If it reports a failure, just ask it to try again — failed generations don't consume the result.