Aisley for developers and agents

The Aisley connector

Aisley runs a Model Context Protocol server so Claude and ChatGPT can ask Aisley about your wedding. It speaks Streamable HTTP and exposes one tool, ask_aisley, which answers a question from the couple's plan in Aisley (venues, vendor conversations, tasks, budget, the facts in the wiki) and changes nothing.

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.

Connect from Claude

1. In Claude.ai or Claude Desktop, open Settings, then Connectors, and choose Add 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. In ChatGPT, open Settings, then Connectors, and choose Create.
2. Paste https://getaisley.com/mcp as the MCP server URL, choose OAuth for authentication, and save.
3. ChatGPT sends you to getaisley.com to log in, choose the wedding, and allow the connection.

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 stops getting answers for this wedding the next time it asks. 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.