We and selected third parties use cookies or similar technologies for technical purposes and, with your consent, to analyze how the site is used.

You can freely give, refuse or withdraw your consent at any time.

NFC Tap Builder by Tap.Giving

MCP server by Tap.Giving

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

No sign-in (No account or key needed)Streamable HTTP

Connect to NFC Tap Builder by Tap.Giving

No sign-in needed. Connect with NFC Tap Builder by Tap.Giving’s own URL:

https://tap.giving/mcp

Paste it into any client that supports remote MCP servers. Your client talks to Tap.Giving directly, not through mcp.tc.

Share this server

Opens this page, with the URL and setup steps.

mcp.tc/i/nfc-tap-builder-by-tap-giving

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 you 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_discoveryRead-only

    Orients the agent: what the builder does, product basics, first choice of shape, spec summary and…

  • get_quoteRead-only

    Binding quote for a quantity with totals, add-ons, free shipping and turnaround.

  • get_productRead-only

    Product facts by topic: discs, mounting, stands, shipping, samples and ordering.

  • get_artwork_specRead-only

    Production artwork spec for the chosen shape, with geometry, format and example designs.

  • get_examplesRead-only

    Shows finished disc designs delivered to organizations, paged by shape.

  • submit_artworkWrites

    Submits finished artwork and shows it on the disc as a proof.

  • start_order_intentWrites

    Captures a contact email as an optional order lead; creates no invoice.

  • get_order_questionsRead-only

    Returns the order questions as structured data in the order to ask them.

  • get_recapRead-only

    Validates order inputs and returns a full recap with exact cost and a recapRef.

  • create_orderWrites

    Places the order; Tap.Giving emails the invoice and design proof.

  • get_order_statusRead-only

    Reads order stage, fulfillment, invoice state and artwork preview using a status reference.

Read from the live server on 18 Nov 2026. Read-only, Writes and Can delete are hints the server declares; your client decides whether to ask before running a tool.

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.

Set up

Every client connects to tap.giving. Pick yours; the page remembers your choice.

Claude Code

  1. Run this in a terminal, in your project folder:
claude mcp add --transport http nfc-tap-builder-by-tap-giving https://tap.giving/mcp
  1. 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:
https://tap.giving/mcp
  1. 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:
  1. Check that the URL reads https://tap.giving/mcp and click Add.
  2. 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

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

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

VS Code

Or from a terminal:

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
{
  "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
{
  "mcpServers": {
    "nfc-tap-builder-by-tap-giving": {
      "serverUrl": "https://tap.giving/mcp"
    }
  }
}
  1. Refresh the MCP server list in Cascade.

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

Codex

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

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

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

Gemini CLI

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.

{
  "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.

Embed

Show NFC Tap Builder by Tap.Giving in a README or on your site. Each embed links to this page, uses the server’s own URL, and sets no cookies. How embeds work

The card, the iframe and the JSON are in English. Add ?lang=it, fr, de or es to their address for another language.

README badge

Badge preview, lightBadge preview, dark
Markdown
[![NFC Tap Builder by Tap.Giving on mcp.tc](https://mcp.tc/i/nfc-tap-builder-by-tap-giving/badge.svg)](https://mcp.tc/i/nfc-tap-builder-by-tap-giving)
HTML
<a href="https://mcp.tc/i/nfc-tap-builder-by-tap-giving"><img src="https://mcp.tc/i/nfc-tap-builder-by-tap-giving/badge.svg" alt="NFC Tap Builder by Tap.Giving on mcp.tc" height="20"></a>

It follows the reader’s light or dark mode. Add ?theme=light or ?theme=dark to fix it, or ?style=compact to show the mark without the word.

Website card

HTML
<script src="https://mcp.tc/w/nfc-tap-builder-by-tap-giving.js" async></script>

The card appears where the tag is. Add data-theme="dark" or data-size="compact" to the tag to change it. The file holds everything it needs, so it makes no other requests and sets no cookies.

iframe

HTML
<iframe src="https://mcp.tc/embed/nfc-tap-builder-by-tap-giving" title="NFC Tap Builder by Tap.Giving on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>

Use it on pages that don’t allow scripts. Add ?theme=light or ?theme=dark to the address to fix the colors.

JSON

The listing as data for your own pages and tools: name, tagline, the server’s own URL, tools and the “Add to” links. Any site can read it (CORS is open).

https://mcp.tc/i/nfc-tap-builder-by-tap-giving.json

What each field means

AI prompt

Paste this into an AI coding assistant, such as Claude Code or Cursor, and it adds the NFC Tap Builder by Tap.Giving card to your site.

Markdown
Add the mcp.tc card for NFC Tap Builder by Tap.Giving, an MCP server, to my website. It is one static script: no build step, no package to install, no cookies.

Put this tag where the card should appear. The card renders right before it:

```html
<script src="https://mcp.tc/w/nfc-tap-builder-by-tap-giving.js" async></script>
```

To show the card somewhere else, put this placeholder there and load the same script once, for example before `</body>`. Keep the link inside: visitors without JavaScript see it.

```html
<div data-mcptc="nfc-tap-builder-by-tap-giving"><a href="https://mcp.tc/i/nfc-tap-builder-by-tap-giving">NFC Tap Builder by Tap.Giving on mcp.tc</a></div>
```

Options:
- `data-theme="light"` or `"dark"` on the tag or the placeholder fixes the colors. Without it, the card follows the visitor’s light or dark mode.
- `data-size="compact"` gives a smaller card without the tagline.
- The CSS variable `--mcptc-max-width` on the placeholder or a parent sets the width (default `520px`).
- `?lang=` on the script URL sets the card’s language: `en`, `it`, `fr`, `de` or `es`.

If the site has a Content Security Policy, allow `script-src https://mcp.tc` and `img-src data:` (the icon is inline).

For a README or other Markdown docs, use the badge instead:

```markdown
[![NFC Tap Builder by Tap.Giving on mcp.tc](https://mcp.tc/i/nfc-tap-builder-by-tap-giving/badge.svg)](https://mcp.tc/i/nfc-tap-builder-by-tap-giving)
```

Reference: https://mcp.tc/embed

Change history

We read this server’s tool list every 3 hours and record what changes. Last read 18 Nov 2026, 02:49 UTC.

Follow NFC Tap Builder by Tap.Giving and we’ll email you when something changes.

  1. , Automatic check

    1 tool changed.

    Details, 15 Nov 2026, 05:55 UTC

    Changed 1

    • get_recapdescription and input schema
      Before

      The full recap, the last thing before the exits: it validates the same order inputs create_order will carry (quantity from 100 to 7000, one of the two built-in sizes, adhesive or screws mounting, a complete shipping address) and returns the submitted artwork (displayUrl plus image content where renderable), the quantity, the shipping address as entered, the exact cost from get_quote, and both required notes. Returns a recapRef; create_order carries it, and an order whose inputs differ from the recap is refused as a conflict. Without a contactEmail the same complete summary returns as an unbound summary, marked not placeable until a contact email is captured; create_order refuses an unbound recap. No key needed.

      After

      The full recap, the last thing before the exits: it validates the same order inputs create_order will carry (quantity from 100 to 7000, one of the two built-in sizes, adhesive or screws mounting, a complete shipping address) and returns the submitted artwork (displayUrl plus image content where renderable), the quantity, the shipping address as entered, the exact cost from get_quote, and both required notes. Returns a recapRef; create_order carries it, and an order whose inputs differ from the recap is refused as a conflict. Pass contactEmail (the email captured with start_order_intent) and artworkRef (the reference submit_artwork returned, when a design was submitted) to bind the recap to the flow. Without a contactEmail the same complete summary returns as an unbound summary, marked not placeable; an unbound recap asserts nothing about what the flow captured elsewhere, and create_order refuses it. No key needed.

      • Description of artworkRef
        Before

        Optional: the artwork reference submit_artwork returned, shown on the disc in the recap.

        After

        Optional: the artwork reference submit_artwork returned; pass it so the submitted design shows on the disc in the recap. Without it, the recap cannot show a design the flow submitted.

      • Description of contactEmail
        Before

        The order contact email; the final proof is emailed there, so it must be an address the organization owns.

        After

        The order contact email: pass the email captured with start_order_intent; it binds the recap for placement. The final proof is emailed there, so it must be an address the organization owns.

  2. , Automatic check

    Tracking started: 11 tools.

FAQ

Can I paste mcp.tc/i/nfc-tap-builder-by-tap-giving into my MCP client?

No. mcp.tc links are pages, not server addresses. Connect with https://tap.giving/mcp, so your client talks to NFC Tap Builder by Tap.Giving directly. The quick link is for sharing: it opens this page, with setup steps for every client.

Does NFC Tap Builder by Tap.Giving need an API key or a sign-in?

No. NFC Tap Builder by Tap.Giving doesn’t ask for an account or key.

Is NFC Tap Builder by Tap.Giving a remote or a local server?

Remote. Tap.Giving hosts it at https://tap.giving/mcp, and it speaks Streamable HTTP. There’s nothing to install.

What can NFC Tap Builder by Tap.Giving do?

It has 11 tools, including get_discovery, get_quote and get_product. You can read the production artwork spec for round or square discs, browse finished example designs delivered to organizations and submit artwork and see it on the disc as a proof.

Which clients can use it?

Any client that supports remote MCP servers: Claude Code, Claude Desktop, claude.ai, ChatGPT, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. The setup steps cover each one.

Does mcp.tc track changes to NFC Tap Builder by Tap.Giving?

Yes. NFC Tap Builder by Tap.Giving’s History tab shows each change we find to its tools, down to descriptions and parameters, plus new versions and edits by its owner. Follow the listing to get an email when it changes.

Who wrote this page?

mcp.tc’s robot read NFC Tap Builder by Tap.Giving’s own metadata (its MCP handshake, tool list and public pages), and an AI model drafted the text from it. A person reviews anything the checks can’t confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.

mcp.tc isn’t affiliated with Tap.Giving. This page was built from NFC Tap Builder by Tap.Giving’s public metadata, last checked on 18 Nov 2026, and an AI model wrote the description, so it can be wrong. Names and marks belong to their owners. Something off? Report this listing.