Aisley for developers and agents

The Aisley connector

Aisley runs a Model Context Protocol server so Claude and ChatGPT can read your wedding plan and work on it. It speaks Streamable HTTP. ask_aisley answers a question from the plan in Aisley (venues, vendor conversations, tasks, budget, your notes). Other tools show the plan, change it, or email a venue or vendor when you ask.

• Read the wedding: ask_aisley, open_aisley, open_wedding_panel, show_venue_shortlist, show_vendor_conversations, get_venue_detail, list_tasks, list_venue_searches, get_venue_search, list_venues, get_venue, get_wedding, list_members, list_aisley_threads, read_aisley_thread, get_gmail_status, connect_gmail, get_billing_status, open_billing, list_conversations, get_conversation, get_batch_outreach, list_follow_ups, get_budget, list_notes, read_note, list_moodboard and find_inspiration.
• Change the plan: create_task, update_task, set_task_status, assign_task, draft_task_plan, search_venues, load_more_venue_results, undo_venue_dismissal, save_venue, update_venue, set_venue_status, add_venue_note, update_wedding_details, set_follow_up_settings, set_wedding_role, send_feedback, mark_conversation_read, draft_venue_email, start_batch_outreach, update_batch_draft, mute_follow_ups, resolve_quiet_conversation, save_expense, set_budget_total, estimate_budget, save_note, add_moodboard_image_by_link, set_moodboard_facet, set_moodboard_hero, add_moodboard_label, remove_moodboard_label, save_inspiration and dismiss_inspiration.
• Remove or dismiss one item: dismiss_task, dismiss_venue_result, remove_venue, remove_venue_note, dismiss_reply_suggestion, discard_batch_draft, discard_batch_outreach, dismiss_follow_up, remove_expense and remove_moodboard_image.
• Send email, after the couple confirms: invite_partner, reply_to_vendor, send_venue_email, send_batch_outreach and send_follow_up.

Each tool tells your assistant whether it only reads, changes the plan, removes something or sends email, so Claude and ChatGPT ask you before anything changes. No email leaves your Gmail until you confirm it there.

You sign in with your Aisley account through OAuth and pick one wedding. That connection answers for that wedding alone; connect again to add a second one.

Aisley files each question as a chat in the app, so you can carry on there. When an answer takes longer than the client waits (about 50 seconds), the tool says so and the full reply waits for you in Aisley.

Your wedding inside ChatGPT

In ChatGPT, Aisley is also a plugin with its own screens. Open it from the sidebar for the countdown, what needs you, your venues and your inbox, or keep the Wedding at a glance panel beside a conversation. Ask about venues or vendor replies and the answer arrives as a card: the shortlist with each venue's status, price and whether your date is free, or each conversation with the latest reply, who is waiting on whom, and the reply Aisley has drafted.

Aisley drafts, you decide. The cards show the plan and change nothing: ask in the chat to send the reply Aisley drafted, rule a venue in or out, or tick off a task, and ChatGPT checks with you first. Every card also links back to Aisley. The plugin tools are show_venue_shortlist, show_vendor_conversations, open_aisley and open_wedding_panel, and they follow the open MCP Apps standard, so clients other than ChatGPT can render the same screens.

Connect from Claude

1. In Claude.ai or Claude Desktop, open Customize, then Connectors, press + Add and choose Add custom connector. Claude's free plan allows one custom connector.
2. Name it Aisley and paste https://getaisley.com/mcp as the URL.
3. Claude sends you to getaisley.com: log in, choose the wedding, and press Allow.

Connect from ChatGPT

1. Until Aisley is listed in the ChatGPT plugin directory, turn on Developer mode in ChatGPT under Settings, then Security and login.
2. Open chatgpt.com/plugins, press +, name it Aisley, and paste https://getaisley.com/mcp as the MCP server URL with OAuth for authentication.
3. ChatGPT sends you to getaisley.com to log in, choose the wedding, and allow the connection. Aisley then appears in the sidebar, and you can call on it with @Aisley in a chat.

Connect from Gemini

Google offers custom apps in Gemini only to people 18 or over in the US, signed in with a personal Google Account and with Keep Activity on, and in English only for now. Couples in the UK can't add Aisley to Gemini yet. Google's help page has the current requirements.

1. On a computer, go to gemini.google.com and open Settings, then Connected Apps.
2. Under Custom apps, choose Add a custom app, paste https://getaisley.com/mcp as the MCP server URL and press Next. Aisley supports dynamic client registration, so Advanced features can stay closed.
3. Gemini sends you to getaisley.com to log in, choose the wedding, and allow the connection. You add custom apps on the web, and Google makes them available in the Gemini mobile app too.

Disconnecting

Open the wedding's settings in Aisley and find Connected apps. Each connection lists the app and who connected it. Remove one and that app can no longer read or change this wedding, or send email for it, from its next request. You can also remove Aisley from the client's own connector settings.

Aisley in plain markdown

A machine-readable index of everything on this site lives at getaisley.com/llms.txt, and the full text of every guide and doc in one file at getaisley.com/llms-full.txt.

Every public page is also served as clean markdown: request any URL with an Accept: text/markdown header, or append a .md suffix to any guide or doc URL. New guides land in the feed at getaisley.com/feed.xml, and every public URL is listed at getaisley.com/sitemap.xml.

The machine-readable surface

The OpenAPI description at getaisley.com/openapi.json documents everything a program can reach: the MCP endpoint, the OAuth server that protects it (dynamic client registration, authorization code with PKCE, refresh token rotation, revocation), and the discovery documents. Every endpoint in it answers errors as JSON with an error code and a description that says how to fix it.

The MCP server card lives at /.well-known/mcp and at /mcp/server-card, and an RFC 9727 API catalog at /.well-known/api-catalog ties the pieces together.

Rate limits are in the headers, so an agent can pace itself without reading this page. Every response under /api carries RateLimit-Policy and RateLimit (the IETF draft format) and the X-RateLimit-* legacy forms: 60 requests per 60-second window per client. Past that you get a 429 with a JSON rate_limited error and Retry-After in seconds. Wait that long and try again.

What Aisley does not have

There is no API key, no webhooks, no separate data API, and no tool that answers without a signed-in Aisley account. The connector and the OAuth server around it are the whole developer surface for now. When that changes, we announce it here and in llms.txt first.

Building something with Aisley, or need early access? Write to hello@getaisley.com and a founder will reply.