MCP server

Connect your AI to Wedding Computer

Use Claude, Cursor, or any AI assistant that speaks the Model Context Protocol to read and update your contacts, weddings, run sheets, checklists, and notes — in plain language.

Use your AI to prepare for a wedding

Choose a model that supports tools in your AI app. Wedding Computer supplies current wedding information and permission-checked actions; your AI app chooses and runs the model.

“Brief me on Ava and Leo’s wedding: the run sheet, people, notes, forms, files and outstanding payments.”
“Add a private note to Ava and Leo’s wedding: call the venue about wet-weather access.” Say “vendors only” or “everyone” when you want to share a note.
“Move the ceremony to 3 pm, then check the saved run sheet and tell me whether the change was applied or needs approval.”

Your AI works within your wedding permissions. Notes stay private unless you ask to share them, and timeline changes follow the same approval rules as the dashboard.

Before you start

The MCP server is included in the AI and automation subscription for Pro. See pricing →
Connecting Claude needs no token — you sign in and approve (step 1). Only token-based methods (Claude Code, Cursor, scripts) need an integration token from Settings → Calendar & contacts → Advanced integrations — shown once; paste it in place of YOUR_INTEGRATION_TOKEN.

Connection details

Endpoint: https://wedding.computer/mcp
Transport: Streamable HTTP (JSON-RPC 2.0)
Authentication: OAuth 2.1 sign-in (PKCE), or a Bearer integration token

Set it up

Claude — web, desktop & mobile (recommended)

No token needed — just sign in and approve:

In Claude, open Settings → Connectors → Add custom connector.
Paste https://wedding.computer/mcp as the URL and add it.
Claude sends you to Wedding Computer to sign in and approve — then you’re connected on every Claude surface.

Manage or disconnect it anytime under Settings → Calendar & contacts → Advanced integrations → “Connected apps”.

Claude Code (CLI)

Sign-in flow — run this and approve in the browser when prompted:

claude mcp add --transport http wedding-computer https://wedding.computer/mcp

Prefer a token instead of signing in? Add a header:

claude mcp add --transport http wedding-computer \
  https://wedding.computer/mcp \
  --header "Authorization: Bearer YOUR_INTEGRATION_TOKEN"

Cursor, Windsurf & other MCP clients

Most clients accept a remote URL with a header. For Cursor, add this to ~/.cursor/mcp.json (others use the same shape):

{
  "mcpServers": {
    "wedding-computer": {
      "url": "https://wedding.computer/mcp",
      "headers": { "Authorization": "Bearer YOUR_INTEGRATION_TOKEN" }
    }
  }
}

Older clients (manual bridge)

A client that only speaks stdio can reach the server through the mcp-remote bridge — e.g. in claude_desktop_config.json:

{
  "mcpServers": {
    "wedding-computer": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote", "https://wedding.computer/mcp",
        "--header", "Authorization:${WC_TOKEN}"
      ],
      "env": { "WC_TOKEN": "Bearer YOUR_INTEGRATION_TOKEN" }
    }
  }
}

Requires Node.js. The token is kept in env so it isn’t split on the space.

What your assistant can do

Contacts & leads

List, search, and read your contacts; log a new enquiry.

Weddings

Read a wedding’s details, team, credits, and activity log.

Run sheets

Read and edit the timeline — add, move, or remove items; start and end live mode on the day.

Checklists

Read and tick off a wedding’s to-do list.

Notes

Read and append to the Everyone, vendors-only, and your own private notes.

Weather & sun

Pull the forecast and add sunrise/sunset times for a wedding date and place.

Everything is scoped to your account and the weddings you’re a member of. Machine-readable details live in the server card.

Get your integration token →