NFC Tap Builder by Tap.Giving
An MCP server for designing and ordering custom NFC tap-to-give discs for churches. Keyless discovery and pricing; order setup by API key; payment handed off by hosted invoice link. Tap.Giving makes custom NFC tap-to-give discs: a member holds a phone against a disc mounted on a pew back or chair back and the church giving page opens, no app to install. Discs work with any giving platform and include a free Redirect Dashboard to change where a disc points in seconds. One-time hardware, no subscription.
Hosted MCP Server
npx add-mcp 'https://tap.giving/mcp'Installs into Claude Code, Codex, Cursor and more
Documentation
NFC Tap Builder by Tap.Giving
A design tool first: this server helps you create print-ready NFC tap artwork proofs. Work from its published spec and design directions, compose the artwork with your own tools, and submit the finished file to see it on the disc as a proof. The artwork is yours: print-ready, vendor-neutral, yours to take to any printer. Ordering discs through Tap.Giving is an optional next step, only if you want it. The discs themselves are custom NFC tap discs and tap tags for organizations of every kind: built for churches, nonprofits, restaurants, coffee shops, and local businesses, designed by your own agent. Ordering is optional and stays behind the human payment and proof gates. This server moves no money itself: when an order is placed, Tap.Giving emails the invoice and the design proof, and a person pays the hosted invoice.
Endpoint: POST https://tap.giving/mcp (MCP over Streamable HTTP, JSON-RPC 2.0, stateless). Repository: https://github.com/Tap-Giving/tap-giving-mcp
Connect
Paste-ready client config:
{ "mcpServers": { "tap-giving": { "type": "http", "url": "https://tap.giving/mcp" } } }
Claude Code: claude mcp add --transport http tap-giving https://tap.giving/mcp No account, key, or login at any point: connect and use every tool as-is. Nothing needs a header, and a header, if a client sends one anyway, is ignored. The design phase states no prices; prices are first stated at the order questions, and exact totals come from get_quote and the recap.
Tools
- get_discovery: Start here, with the design tool.
- get_quote: The binding quote for a prospective order (also known as get_pricing): quantity, tier, list totals as the headline, and one payable first-order total with the first-order discount scope and its 7-day renewing window explained in plain words.
- get_product: The full product facts.
- get_artwork_spec: The production artwork spec for the chosen shape: 106 mm artboard, cut, bleed, and safe-zone geometry as structured millimetre data plus plain guidelines, the format wanted back (vector, SVG preferred), delivered example designs to react to (real organizations' finished discs, indexed in full with a bounded set shown inline), labeled explainer photos of discs in place, and the optional logo ask.
- get_examples: Show the finished discs: the real designs Tap.Giving produced and delivered to organizations, as labeled images, paged nine at a time, round first then square.
- submit_artwork: Send the finished artwork back and see it on the disc as a proof.
- start_order_intent: An optional step on the order path, not the start of the journey: capture a contact email through the same public capture endpoint the website's email-first door uses, so follow-up rides the existing lead machinery.
- get_order_questions: The order questions as structured data, returned in the exact order to ask them: the contact email first (captured through start_order_intent), then the organization name, the shipping address and phone, quantity, shape, the metal count, mounting with the picture assets, the artwork answer (we have artwork, or the team designs it from the organization name), and the link destination as a confirmation of the destination carried from the design.
- get_recap: 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.
- create_order: The final step of the order path, labeled "Email me my invoice and design proof." Set up an order through the same front door a website order takes (an INVREQ record the hourly adoption resolves into the CRM, indistinguishable downstream).
- get_order_status: Where an order stands, read with the order's status reference: the capability create_order returned once at placement (also carried in the customer email).
Explainer
Resources (tapgiving://explainer/) explain how it works and where you are: how-it-works, what-a-tap-disc-does, nfc-vs-qr, the-two-phases, after-you-order, materials-and-care. The prompt explain_where_i_am answers a stuck user with the step they are on.
Access
There are no credentials on this server. Submitted artwork is fetchable at its capability URL (/mcp/artwork/, and the same address with .png on the end for the print render): the artwork reference itself is the capability, within 30 days of submission. Order status is read with get_order_status and the order's status reference, shown at placement and carried in the invoice email; if it cannot be found, email hello@tap.giving from the order email and the team re-sends it.
Human gates
- Design approval stays human: a person approves the final proof by email before production. No tool on this server records or implies an approval.
- Payment stays human: This server moves no money itself: when an order is placed, Tap.Giving emails the invoice and the design proof, and a person pays the hosted invoice. A person pays the invoice when it arrives.
- Production release and the supplier handoff stay human: no tool on this server releases an order to production or touches fulfillment state.
This server moves no money itself: when an order is placed, Tap.Giving emails the invoice and the design proof, and a person pays the hosted invoice.