Skip to main content
You can connect Goody to Claude — or any MCP-compatible client — by adding it as a custom connector with the server URL.
The Claude Connectors Directory listing is rolling out — for now, add Goody as a custom connector below.

​
Add Goody as a custom connector

Any MCP client that supports remote OAuth servers can add Goody by URL — Claude (web, desktop, and mobile) and others. Point the client at the server URL and complete OAuth sign-in. In Claude specifically, use the steps below; in another client, add a custom/remote MCP server with the same URL.
1

Add a custom connector

In claude.ai, go to Settings → Connectors → Add custom connector. In another MCP client, open its custom or remote MCP server settings.
2

Enter the server URL

https://api.ongoody.com/mcp/v1
3

Sign in to Goody

You’ll be redirected to Goody to sign in — or to create a Goody for Business account if you don’t have one.
4

Authorize

Review the permissions Goody requests and click Authorize. Goody now appears as a connected tool — start a new chat and try an example prompt.
The Goody MCP server publishes the standard OAuth authorization-server and protected-resource metadata, so any compliant client discovers the authorization, token, and registration endpoints from the URL alone — there’s nothing to configure by hand.
A Goody for Business account is required. The Goody MCP server acts only within the Goody workspaces you’re a member of, and gifts you send appear in your Goody dashboard exactly like gifts sent from the website.

​
Connect a script or automation

For scripts, n8n / Zapier / Make workflows, cron jobs, or headless agent frameworks — anywhere a browser-based OAuth sign-in isn’t an option — connect with a personal MCP token instead.
1

Create a personal MCP token

In Goody for Business, go to account settings → Personal MCP token. Give it a name, choose its scopes (Read / Write / Send gifts), and pick an expiry. The token is shown once — copy it now.
2

Configure your client

Point your MCP client at the server URL and pass the token in an Authorization: Bearer header. Both are required.
{
  "mcpServers": {
    "goody": {
      "url": "https://api.ongoody.com/mcp/v1",
      "headers": {
        "Authorization": "Bearer YOUR_PERSONAL_MCP_TOKEN"
      }
    }
  }
}
Use the direct Streamable HTTP form when your client supports remote MCP servers with custom headers. Use the mcp-remote bridge for clients that only speak stdio.
A personal MCP token is a credential — anyone with it can act with the scopes you granted, including spending money if you selected Send gifts. Store it like a password, scope it to only what the automation needs, and revoke it from the same page if it’s exposed.
See Authentication & permissions for how the two methods compare and what each permission allows.

​
Supported clients

Any MCP client that supports remote servers works. Interactive clients (Claude on web, desktop, and mobile; Cursor; ChatGPT’s MCP support) connect over OAuth with no setup beyond the server URL. Scripts and automations connect with a personal MCP token. The server uses the standard Streamable HTTP transport, so no local proxy or command-line setup is required.