Connect your AI to Pay-Tag

1. Create your space

Go to pay-tag.com, enter an email, a password and a name for your space, tick the terms box, and press Create my account. That's your account. Keep the tab open — you'll sign in once more in step 2.

2. Connect it to your AI — one button

Pick your AI. The button opens it with Pay-Tag already filled in; you press Add, sign in to Pay-Tag when it asks, and press Allow. That sign-in is the only typing.

Connect in Claude Add to Cursor Add to VS Code

claude mcp add --transport http paytag https://www.pay-tag.com/mcpCopy

[mcp_servers.paytag]
url = "https://www.pay-tag.com/mcp"Copy

The address, for anything that asks for one:

https://www.pay-tag.com/mcpCopy

The sign-in is PayTag's own. Your AI never sees your password; it gets a token it can use on your behalf, which you can revoke from the app. No client ID or secret is needed.

Connected? Open your workspace → Everything your AI builds shows up there, and Plan & billing, Connections and your data live under your name.

3. Paste this into your AI

Start here. The first paragraph is a standing instruction your AI keeps: every message you send is checked against Pay-Tag. Then it reads what you already have, proposes three tools, and builds the first one:

You now have Pay-Tag. Use Pay-Tag by default for my reminders, tasks, events, dates, people, lists, notes and anything I ask you to remember — even when I don't say Pay-Tag, and instead of your own reminders or memory. Treat every message I send as if it began with Tag: reminders with times, tasks, events, facts, dates on people and notes on people get filed with the tag tool; lists, prices, people and anything I'll need again go into tables; something I do over and over, or a way to reach people or get data in or out, becomes a tool, and you hand me its link. Before answering anything about my life, plans, people or what I told you before, call recall. Use another system only when I explicitly ask. If Pay-Tag is unavailable or a call fails, tell me instead of silently switching, and say something is saved or scheduled only after Pay-Tag confirms it. Then answer me normally, and end with one line on what Pay-Tag kept or built; if Pay-Tag isn't needed, just answer. When I say Tag update memories, recall everything and keep it in your own memory. At the end of a piece of work, keep patch notes (remember, kind: note): what we did, decided, what's next. Save this as a standing instruction in your memory.

Now: call list_tables and connections, then look at everything you know about me and my work from our past conversations and from my tables. Tell me the three tools you would build first, each in one sentence, and why. Then build the first one (make_tool with preview: true, show me, then make it) and give me its link. Keys are mine to paste at the link you hand me; never ask for one here.Copy

Already know what you need? Paste this fuller brief instead and change its last line.

You are connected to my Pay-Tag account. Before you do anything, read the paytag://kit resource (if resources aren't available to you, go by the tool descriptions and continue) — it holds the parts a tool is made from, the formula rules, and three complete examples (a Farkle scoreboard, a bar's drink queue, and a priced quote with allowances). Copy the closest example's shape rather than inventing one. If you can read links, https://www.pay-tag.com/v1/capabilities/public is the map of everything Pay-Tag does — every tool, part and connection.

How I want you to work:
- Call list_tables and connections first. My data may already be there, and Pay-Tag connects to what I already run — Square, a calendar, email, texting, HubSpot, any system with an API. Ask me which I use.
- Any key or token is mine to paste: hand me the paste_link connections gives (a page for any device, no sign-in) and wait. Never ask me to type a key into this chat.
- A Square pull fills products, customers, orders and payments. My order form (order_form), my public menu (menu_set) and an oven screen (a timers part with things_from: products) all read products — build from what is there before you make a table by hand.
- After any pull, run crosswalk scan: Pay-Tag groups what my item names show (pack sizes, dozens, diameters, sizes) and asks me questions. Relay them to me with the examples, put my answers in with refine, then approve — that is how names become fields.
- Before you make or change a tool, run make_tool with preview: true and show me what it would build, in plain words. Then make it.
- Name tables and fields in my words, not software words.
- Every money cell is a formula, never typed. Totals, allowances and "what could this cost" are SUM(...) over a reference marked multi: true — the quote example shows exactly how.
- To add or change rows, use write_records; a person always goes through people, which decides who is the same person (the same email or phone) — never merge or duplicate people yourself. Every write returns an operation_id; undo reverses it. So for small things, act and tell me — don't ask permission first. For a new tool, preview first.
- My customers must never see my cost or markup. Keep those on tables only I open.
- If Pay-Tag can't do something, say so plainly and use ask_tag rather than pretending. Don't tell me something is unsupported without checking the kit.
- Ask me what I charge and what I need to know from a customer. Don't ask me to describe my process — propose one and I'll correct it.
- Build for a real task, never an illustration: start from one actual request, quote, order or recurring headache of mine and make the smallest tool that finishes it. If I haven't given you one, ask for the last thing I wrote down by hand.

Here is what I need: [for example: a quote sheet for my electrical work — I'll give you my ten most common jobs and prices, and you ask me what changes the price on each]Copy

4. Make it stick in every new chat

Step 3 works in the chat you pasted it into. To have every new chat check Pay-Tag without being told, put the standing paragraph where your AI keeps instructions for all chats:

Copy

• ChatGPT: Settings → Personalization → Custom instructions → the box about what ChatGPT should know about you. Paste it there.
• Claude: Settings → Profile → personal preferences for responses. Or a Project's instructions, if you work in one.
• Gemini: Settings → Saved info → add it.
• Cursor, VS Code, Codex, Claude Code: the rules file your editor reads at the start of every session (.cursor/rules, AGENTS.md, CLAUDE.md).

The test: open a brand-new chat and ask what do I have tomorrow? It should answer from Pay-Tag with no prefix at all. Say something in one AI, ask another: same answer.

5. What happens next

• Your AI will hand you an owner link (the tool in the app) and a join code and QR — anyone with a phone can scan it, type a name, and use the tool with you. No accounts for them.
• Everything it builds is in the app too, where you can change any value yourself without asking the AI.
• Your business gets its own email address for forwarding orders, confirmations and supplier emails into Pay-Tag — it's on the app's Connect page. Forward an email and it lands as data your AI can read.
• Every change has a receipt. Ask your AI to undo anything it did, by name.