# NFC Tap Builder by Tap.Giving MCP server

> Design print-ready NFC tap disc artwork, get quotes, and optionally order custom discs for churches, nonprofits and businesses.

- Listing: https://mcp.tc/i/nfc-tap-builder-by-tap-giving
- Connect: use the server's own URL `https://tap.giving/mcp` (no sign-in); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: none
- Category: [E-commerce](https://mcp.tc/c/ecommerce)
- Vendor: Tap.Giving
- Homepage: <https://tap.giving/>
- Repository: <https://github.com/Tap-Giving/tap-giving-mcp>

## About

Connects to Tap.Giving's custom NFC tap disc service. An assistant can read the artwork spec and example designs, submit finished artwork to see it as a proof on the disc, get a binding quote, and optionally place an order and check its status.

The server is hosted at https://tap.giving/mcp over Streamable HTTP. No sign-in or API key is needed, including for ordering. Orders end with an emailed invoice and design proof, and a person pays the hosted invoice. The server itself moves no money.

## What it can do

- Read the production artwork spec for round or square discs
- Browse finished example designs delivered to organizations
- Submit artwork and see it on the disc as a proof
- Get a binding quote by quantity
- Capture a contact email as an order intent
- Create an order that emails the invoice and design proof
- Check order status with a status reference

## Tools (11)

- `get_discovery`: Orients the agent: what the builder does, product basics, first choice of shape, spec summary and… (read-only)
- `get_quote`: Binding quote for a quantity with totals, add-ons, free shipping and turnaround. (read-only)
- `get_product`: Product facts by topic: discs, mounting, stands, shipping, samples and ordering. (read-only)
- `get_artwork_spec`: Production artwork spec for the chosen shape, with geometry, format and example designs. (read-only)
- `get_examples`: Shows finished disc designs delivered to organizations, paged by shape. (read-only)
- `submit_artwork`: Submits finished artwork and shows it on the disc as a proof.
- `start_order_intent`: Captures a contact email as an optional order lead; creates no invoice.
- `get_order_questions`: Returns the order questions as structured data in the order to ask them. (read-only)
- `get_recap`: Validates order inputs and returns a full recap with exact cost and a recapRef. (read-only)
- `create_order`: Places the order; Tap.Giving emails the invoice and design proof.
- `get_order_status`: Reads order stage, fulfillment, invoice state and artwork preview using a status reference. (read-only)

## Example prompts

- "Show me example round NFC disc designs from Tap.Giving."
- "Get a quote for 300 NFC tap discs."
- "Design artwork for our church's square tap disc and submit it as a proof."
- "Check the status of my order with this status reference."

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

```bash
claude mcp add --transport http nfc-tap-builder-by-tap-giving https://tap.giving/mcp
```

2. Start Claude Code and type `/mcp`. **nfc-tap-builder-by-tap-giving** should show as connected.

Add `--scope user` to make it available in every project, not just this one.

### Claude Desktop

1. Open **Customize → Connectors**, click **+ Add**, then **Add custom connector**.

2. Name it **NFC Tap Builder by Tap.Giving** and paste this URL:

```url
https://tap.giving/mcp
```

3. Click **Add**. Its tools appear in the chat’s tools menu.

Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

### claude.ai

1. Open the connector form on claude.ai. This button fills in the name and URL for you:

[Add to claude.ai](<https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=NFC%20Tap%20Builder%20by%20Tap.Giving&connectorUrl=https%3A%2F%2Ftap.giving%2Fmcp>) (opens connector settings)

2. Check that the URL reads `https://tap.giving/mcp` and click **Add**.

3. Turn it on in a chat from the tools menu.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**.

### ChatGPT

1. On chatgpt.com, go to **Plugins**, select **+**, then **Add custom MCP server**.

2. Enter a name for the server.

3. Under **Connection**, paste `https://tap.giving/mcp` as the server URL, then for authentication choose **No authentication**.

4. Check **I understand and want to continue**, then select **Create as a plugin**.

Whether you can add a custom MCP server depends on your ChatGPT plan and your workspace permissions (in Business workspaces, admins and owners can).

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=nfc-tap-builder-by-tap-giving&config=eyJ1cmwiOiJodHRwczovL3RhcC5naXZpbmcvbWNwIn0%3D>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

```json
{
  "mcpServers": {
    "nfc-tap-builder-by-tap-giving": {
      "url": "https://tap.giving/mcp"
    }
  }
}
```

### VS Code

[Install in VS Code](<https://vscode.dev/redirect/mcp/install?name=nfc-tap-builder-by-tap-giving&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Ftap.giving%2Fmcp%22%7D>) (opens VS Code)

Or from a terminal:

```bash
code --add-mcp '{"name":"nfc-tap-builder-by-tap-giving","type":"http","url":"https://tap.giving/mcp"}'
```

Or commit it to the repo in `.vscode/mcp.json`:

`.vscode/mcp.json`:

```json
{
  "servers": {
    "nfc-tap-builder-by-tap-giving": {
      "type": "http",
      "url": "https://tap.giving/mcp"
    }
  }
}
```

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

```json
{
  "mcpServers": {
    "nfc-tap-builder-by-tap-giving": {
      "serverUrl": "https://tap.giving/mcp"
    }
  }
}
```

2. Refresh the MCP server list in Cascade.

Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.

### Codex

```bash
codex mcp add nfc-tap-builder-by-tap-giving --url https://tap.giving/mcp
```

Or edit `~/.codex/config.toml` directly:

`config.toml`:

```toml
[mcp_servers.nfc-tap-builder-by-tap-giving]
url = "https://tap.giving/mcp"
```

### Gemini CLI

```bash
gemini mcp add --transport http nfc-tap-builder-by-tap-giving https://tap.giving/mcp
```

This adds it to the current project. Add `-s user` to use it everywhere.

### Any client

Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.

```json
{
  "mcpServers": {
    "nfc-tap-builder-by-tap-giving": {
      "type": "http",
      "url": "https://tap.giving/mcp"
    }
  }
}
```

Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.

Client only starts local servers? Bridge it with `npx -y mcp-remote https://tap.giving/mcp`.

## Recent changes

- 2026-11-15 05:55 UTC: 1 tool changed. Source: automatic check. Changed: get\_recap.
- 2026-11-13 08:24 UTC: Tracking started: 11 tools read. Source: automatic check.

More on the History tab, with descriptions before and after for the newest entries: https://mcp.tc/i/nfc-tap-builder-by-tap-giving#history (Atom feed: https://mcp.tc/i/nfc-tap-builder-by-tap-giving/history.xml). It records what mcp.tc's anonymous checks saw, every 3 hours where the tool list can be read without sign-in; it is not a security review.

## Details

- Server version: 1.0.0
- MCP protocol version: 2025-11-25
- Last checked: 2026-11-18 (reachable)
- Listed: 2026-11-13
- Updated: 2026-11-15

---
Source: https://mcp.tc/i/nfc-tap-builder-by-tap-giving (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report
