One connection. Your own receipts, in your own account.
The short version
Connect once. Then just ask.
ChatGPT and Claude use their directories. Grok takes a custom connector. Muse can follow a setup prompt.
Choose your assistant below and follow its connection route.
Sign in with your Den account and review the access you approve.
Ask “Show me my saved receipts.” to check the connection. An empty receipt list is a valid answer too.
Pick your assistant
Four assistants. One Den account.
Every path ends the same way: you sign in with your Den account and Receipt Weasel shows up in your chats. Weasel Estates works inside its own organizer.
ChatGPT
One tap
One tap from the Weasel Den plugin page, then sign in with your Den account.
A ChatGPT account, signed in in the browser you are using.
A Den account, or a minute to create one during sign-in. The trial starts on first use, with no card up front.
Connect, in order
01Open the Weasel Den plugin page in ChatGPT.
02Choose Connect. ChatGPT sends you to Weasel Den to sign in.
03Sign in or create your Den account, then approve the access. You land back in ChatGPT.
04Start a new chat with Weasel Den turned on and ask it something.
What sign-in looks like
ChatGPT opens the Weasel Den sign-in page. You sign in with your Den account, the same one Receipt Weasel uses, approve what Weasel Den may do for you, and return to ChatGPT. Weasel Den never sees your ChatGPT password, and ChatGPT never sees your Den password.
Then try asking
Tap one to copy it, then paste it into your assistant.
Check it worked
Ask this once you are signed in. It only reads. It never uploads a receipt or starts tracking.
What success looks like
Weasel Den answers with the receipts saved to your Den account, as a card or as text.
No receipts yet? Then it says so. An empty list still proves the connection and the sign-in worked, because that answer came from your account.
You can also ask what is in Weasel Den. That lists the den apps and your membership state, and reads nothing else.
If something is off
The plugin page opens, but there is nothing to connect.
Sign in to ChatGPT in this browser first, then open the plugin page again.
Sign-in never finishes, or ends on an error.
Finish the sign-in in the tab ChatGPT opened, without closing it. If it fails again, disconnect Weasel Den in ChatGPT and connect once more from the plugin page.
Weasel Den says you are not signed in when you ask.
Connections are per account. Reconnect from the plugin page, complete the sign-in step, then ask again in a new chat.
Still stuck? Email hello@weaselden.ai with the assistant name and what you saw.
A personal Claude account, signed in on claude.ai. On a work account, an administrator may control which connectors can be added.
A Den account, or a minute to create one during sign-in. The trial starts on first use, with no card up front.
Connect, in order
01Open the Weasel Den listing in the Claude connector directory.
02Choose Connect. Claude sends you to Weasel Den to sign in.
03Sign in or create your Den account, then approve the access. You land back in Claude.
04In a new chat, make sure Weasel Den is turned on in the tools menu, then ask.
What sign-in looks like
Claude opens the Weasel Den sign-in page. You sign in with your Den account, the same one Receipt Weasel uses, approve what Weasel Den may do for you, and return to Claude. Weasel Den never sees your Claude password, and Claude never sees your Den password.
Then try asking
Tap one to copy it, then paste it into your assistant.
Check it worked
Ask this once you are signed in. It only reads. It never uploads a receipt or starts tracking.
What success looks like
Weasel Den answers with the receipts saved to your Den account, as a card or as text.
No receipts yet? Then it says so. An empty list still proves the connection and the sign-in worked, because that answer came from your account.
You can also ask what is in Weasel Den. That lists the den apps and your membership state, and reads nothing else.
If something is off
The listing shows no Connect button.
Sign in to claude.ai first. On a work account, ask your administrator to allow the Weasel Den connector.
Weasel Den is connected, but Claude does not use it.
Open the tools menu in the chat and turn Weasel Den on for that conversation, then ask again.
Weasel Den says you are not signed in.
In Claude’s connector settings, disconnect Weasel Den, then connect again from the directory listing and complete the sign-in step.
Still stuck? Email hello@weaselden.ai with the assistant name and what you saw.
Grok
Custom connector · Full setup guide
Grok
Custom connectorFounder-verified 2026-09-11
Before you start
Grok on grok.com, signed in on a computer.
A Den account, or a minute to create one during sign-in. The trial starts on first use, with no card up front.
Connect, in order
01On grok.com, open Connectors and choose New connector, then Custom.
02Paste the Weasel Den address: https://mcp.weaselden.ai/mcp. There is no API key or client id to enter.
03Sign in with your Den account when Grok sends you to Weasel Den, then approve the access.
04Back in Grok, start a chat with the Weasel Den connector enabled and ask it something.
What sign-in looks like
Grok sends you to the Weasel Den sign-in page. You sign in with your Den account and approve the access. Grok discovers the sign-in on its own from the connector address, so nothing else needs to be typed.
Then try asking
Tap one to copy it, then paste it into your assistant.
Check it worked
Ask this once you are signed in. It only reads. It never uploads a receipt or starts tracking.
What success looks like
Weasel Den answers with the receipts saved to your Den account, as a card or as text.
No receipts yet? Then it says so. An empty list still proves the connection and the sign-in worked, because that answer came from your account.
You can also ask what is in Weasel Den. That lists the den apps and your membership state, and reads nothing else.
If something is off
Grok asks for an API key or a client id.
Leave them blank. Weasel Den uses sign-in with your Den account, discovered automatically from the address.
Sign-in does not come back to Grok.
Complete the sign-in in the tab Grok opened, on a computer rather than a phone. If Grok still shows the connector as disconnected, remove it and add it again.
Still stuck? Email hello@weaselden.ai with the assistant name and what you saw.
Muse
Ask it · Full setup guide
Muse
Ask itFounder-verified 2026-09-30
Setup prompt
Paste this into a new chat. It tells the assistant where Weasel Den is and how to sign you in.
Connect Weasel Den as an MCP server: https://mcp.weaselden.ai/mcp, Streamable HTTP. Register yourself with its authorization server automatically (it supports dynamic client registration and PKCE; there is no API key or client id), then open the sign-in so I can log in with my Den account. If you need me to paste back the address I land on after sign-in, tell me. When you are connected, show me my saved receipts.
Tested 2026-09-30
Before you start
Muse on a computer, not a phone. The sign-in asks you to paste an address back.
A Den account, or a minute to create one during sign-in. The trial starts on first use, with no card up front.
The connector path, if you would rather add it by hand
01Where Muse accepts an MCP server, add the Weasel Den address: https://mcp.weaselden.ai/mcp. Muse can also find it on its own from weaselden.app/llms.txt.
02Sign in with your Den account when Muse opens the Weasel Den sign-in page, then approve the access.
03When Muse asks, paste the address of the page you landed on after sign-in back into Muse. That completes the connection.
04Ask Muse something Receipt Weasel can do.
What sign-in looks like
Muse registers itself with Weasel Den automatically and opens the sign-in page. After you sign in and approve, Muse needs the address you landed on pasted back to finish. No API key or client id is involved.
Then try asking
Tap one to copy it, then paste it into your assistant.
Check it worked
Ask this once you are signed in. It only reads. It never uploads a receipt or starts tracking.
What success looks like
Weasel Den answers with the receipts saved to your Den account, as a card or as text.
No receipts yet? Then it says so. An empty list still proves the connection and the sign-in worked, because that answer came from your account.
You can also ask what is in Weasel Den. That lists the den apps and your membership state, and reads nothing else.
If something is off
Muse never asks for the address, or the sign-in stalls.
Use a computer. Copy the full address of the page you land on after signing in and paste it into Muse when it asks.
Muse cannot find the server.
Give it the exact address https://mcp.weaselden.ai/mcp, not the website address.
Still stuck? Email hello@weaselden.ai with the assistant name and what you saw.
Using Weasel Estates? Its Den AI assistant works inside the organizer. AI use is included with Den; the organizer is sold separately. See what’s included.
Your account. Your choice.
Know what you’re connecting.
Every connection to the den is bound to a specific person, with permissions that person explicitly granted. Tools act with delegated, time-bound, revocable authority. Never as you, always for you.
Every tool call through the gateway is logged: which tool ran, how long it took, and whether it succeeded, tied to a one-way hash instead of your identity. Disconnect the den any time and it stops acting for you.
Delegated access
The den acts only with the access you granted at sign-in, never as you.
Card details never touch the den
Our payment processor handles payment details end to end. We never store card numbers.
Pseudonymous logging
Every tool call is logged against a one-way hash, not your name.
One-switch revocation
Disconnect the den in your assistant’s settings and access ends at once.
For custom clients and curious people
The connection details.
The same guide as plain Markdown: the endpoint, how sign-in is discovered, the steps for every assistant, and the read-only check. Point your agent at it, or read it yourself.
The connector speaks Streamable HTTP and uses OAuth discovered automatically. An unauthenticated request is answered with a pointer to the sign-in metadata, the authorization server supports automatic client registration and PKCE, and no API key or client id is issued. These are endpoint details for MCP clients, not a desktop configuration file.