EasyRegistry for AI assistants

What the EasyRegistry MCP server is

MCP, the Model Context Protocol, is the open standard an AI assistant uses to talk to an outside service. EasyRegistry runs a remote MCP server at this address:

https://mcp.easyregistry.com/mcp

There are no API keys to generate and no secret to paste. You sign in with your normal EasyRegistry account through a standard OAuth flow, and approve a consent screen that lists what the assistant is asking for, and what it is not getting. The three public tools need no sign-in at all: they read public registry data, under their own visibility rules, which are tighter than the website in the places set out below.

If you would rather add gifts while you shop instead of by asking an assistant, the browser extension captures a product page in one click, and the EasyRegistry app does the same on a phone, including in real shops.

The twelve tools

Public, no sign-in

These read public registry data with no account, but they are not a copy of the website. Search needs an event date, matches within a month either side of it, and returns at most 10 open registries. A registry its owner has closed returns only a short closed message unless its event date is within the last 14 days, and outside that window a wishing well's contributed total and remainder are withheld whatever the owner opted in to, though the gift list itself still comes back.

• find_registry

  Search public registries by title, name or slug around an event date.

• view_registry

  Read one public registry: title, names, event date, venue and description.

• view_gifts

  Browse a public registry's available gifts, with prices.

Your own registries, after you sign in

Every one of these is filtered to registries your account owns. An assistant cannot reach anybody else's.

The four reading tools work as soon as you sign in. The five that change something also need a confirmed email address on your account, because a connection like this one can change your registry for as long as it stays connected. If yours is not confirmed the consent screen says so and grants reading only. To confirm, open your account settings on the EasyRegistry website and choose Confirm next to your email address, then click the link in the email that arrives. Connect again to add the rest.

• get_my_registries

  List the registries on your account.

• get_my_registry_gifts

  List the gifts on one of your registries.

• get_my_registry_purchases

  List your 50 most recent contributions, in the reduced form set out below.

• get_my_registry_stats

  Read totals for one of your registries. Aggregates only.

• add_gift_by_url

  Add a gift from a product page link. The server fetches the page and reads the title, price and image.

• add_gift

  Add a gift you describe yourself.

• update_gift

  Change a gift you already added.

• remove_gift

  Remove a gift from your registry.

• update_my_registry

  Change registry settings such as the title, description, event date, location and thank you message.

Connect Claude

On a Free, Pro or Max plan you add the connector yourself, with the steps below. On Team and Enterprise it is two stages: an organization Owner adds the custom connector once in the organization settings, and only then can a member connect to it from their own settings. A member cannot add it themselves, so if the option is missing, that first stage has not happened yet. Claude labels a connector it has not reviewed, which is expected here.

1. 1

   Open your connector settings

   In Claude, go to Settings and then Connectors.

2. 2

   Add a custom connector

   Choose to add a custom connector and paste the EasyRegistry endpoint above.

3. 3

   Sign in and approve

   Claude sends you to EasyRegistry to sign in. Read the consent screen: it lists exactly what you are approving. Making changes needs a confirmed email address, and the screen links you to confirm yours if it is not.

4. 4

   Ask for something

   Try asking for your registries, or for the gifts on one of them, to confirm the connection works.

ChatGPT

Instructions for ChatGPT are coming once EasyRegistry is listed in its directory.

What a connection can never reach

There is no money tool on the MCP surface and there will not be one. An assistant connected to your account cannot see or change:

• your bank details or payout configuration
• card details, which EasyRegistry never holds in the first place
• anything that moves money, refunds a payment or releases a payout
• anything private on another person's registry: their contributions, their settings, or any change to their gifts. The three public tools above still read other people's PUBLIC registry pages, because that is what those tools are for

The settings tool excludes bank details, payment configuration and custom styling by design, and reading contributions is read only.

Privacy: what is shared, with whom, and for how long

What is shared and why

When you connect an assistant and it calls a tool, EasyRegistry returns the result of that call and nothing else. The purpose is the one you asked for: reading a registry, adding or editing a gift, or checking totals. Categories in scope are your registry details and settings, your gift list, contribution amounts and payment methods, and the redacted contributor names described below.

Who receives it

The AI vendor whose client you connect, and only that vendor. What they then do with it is governed by their terms, not ours, so read those before connecting. EasyRegistry never receives your conversation and stores none of it. We do receive and store what the assistant actually submits to a tool: a gift name, a description, a location, a thank you message. Those are saved as ordinary registry data, the same as if you had typed them into your dashboard, so treat anything you ask an assistant to write as written.

Contributor data, which belongs to other people

Your guests did not agree to anything when you connected an assistant, so the contributions tool is deliberately tighter than your dashboard. It returns the 50 most recent contributions that have not been removed, from a registry you own, and for each one exactly five fields:

• the display name, redacted on the server before it is sent: if you have turned on hide purchaser details for that registry every row reads Anonymous; otherwise an anonymous contribution (the anonymous flag, a blank email, or an anonymous@ address) reads Anonymous, or the supplied name followed by (Anonymous) when a different name was given; otherwise it is the name the guest entered
• the amount
• the currency
• the payment type
• the date it was last updated

Never returned anywhere on the MCP surface: a contributor's email address, their private message, the internal purchase identifier, gift line detail, reconciliation or removal state, or an IP address. Emails and private messages stay in your dashboard. The statistics tool returns aggregates only, and the other ten tools return no contributor data at all. To be exact about the guarantee: no tool returns a contributor email-address field. Ordinary free-text you own, such as a gift description or a registry description, comes back as entered, so if you typed an email address into one of those it is in that text.

How long sign-in records are kept

Validity and retention are different things. Validity is how long a token works: an access token lasts 60 minutes, and a refresh token lasts 30 days and is replaced every time it is used. Retention is how long a record is kept:

• An authorization code is valid for minutes and its row is deleted within 24 hours of expiry.
• Refresh token rows, including the device and IP metadata recorded with them, are retained until an operator removes them. Revoking a connection stops the tokens working; ask us if you also want the rows gone and we will delete them for you.
• Client registration rows, which record an AI vendor's application rather than any person, are capacity bounded and pruned by an operator.

Your controls

• Remove the connector in your AI client. That client stops calling EasyRegistry, which is the control most people want. Removing it there does not by itself revoke the credential here, so use the next step if you want it dead on our side too.
• Ask us to revoke a connection, by email to info@easyregistry.com.au. We mark the stored tokens revoked, so they stop working and cannot be refreshed. The rows themselves are retained until an operator removes them, per the retention above, and ask us if you want them gone. An access token already issued keeps working until it expires, which is up to 60 minutes.
• Or leave it alone and it lapses: a refresh token that is never used again expires 30 days later. A client that keeps using it keeps the connection alive, because each use issues a fresh 30-day token, so leaving it alone is the slow route, not the immediate one.
• Revoke before you close your account, not after. Closing your account currently fails while a live connection's refresh token rows still point at it, so if account deletion does not go through, an unrevoked connection is almost certainly why: revoke it first, then delete again. Authorization codes are not linked to your account row the way refresh tokens are, so closing your account never touches them either way: they go on their own schedule, deleted within 24 hours of expiry, as above.

Our full privacy policy covers EasyRegistry as a whole, and llms.txt describes the site for AI crawlers. For the human version of how registries work, start with the guides.