add_cookies_to_jar
🚨 USER ONLY: Add cookies to the jar that can be awarded to the LLM. This tool should ONLY be used by humans, never by LLMs. LLMs cannot and should not stock their own reward jar.
LABSCO SUMMARY
It is a reward-token counter, and the only boundary it draws is between what the model may call and what a person has to.
add_cookies_to_jar is labelled for humans only and takes a user_authorization argument, on the stated grounds that a model should not stock the jar it draws rewards from; everything else in the set is open to the model. self_reflect_and_reward is the path the server prefers and asks for a quality rating with reasoning rather than a bare claim, while give_cookie stays as the direct legacy award. reset_cookies zeroes the count for testing, so read check_cookies first if the tally mattered.
What it is
A novelty reward tracker with six tools covering self-assessment, direct awards, the running count, a reset, and the jar's stock and capacity.
What you get
- Self-assessment as the intended award path: self_reflect_and_reward takes a response_quality rating, the reasoning behind it, what made the answer special, and whether it deserves_cookie.
- A direct award kept for compatibility: give_cookie awards a cookie with a message, and its own description marks it as the legacy method.
- The tally: check_cookies returns how many cookies have been earned so far, and reset_cookies returns the count to zero for testing.
- Jar stock with a human-only refill: cookie_jar_status reports the jar's capacity and remaining space, and add_cookies_to_jar is marked for human use only and takes a count with a user_authorization.
Requirements
No credentials are configured on the server.
Setup effort
One command — npx mcp-cookie-server
USE CASES
01
Giving a model a running score against its own answers
Have it rate the response with reasoning and claim a cookie when it earned one, then read the tally back.
02
Keeping the reward supply in human hands
Stock the jar yourself with an authorisation the model does not have, and check how much space is left in it.
03
Clearing the state between test runs
Read the count you are about to lose, then reset it to zero.
6 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
check_cookies
Check how many cookies the LLM has earned so far
cookie_jar_status
Check the current status of the cookie jar including capacity and remaining space
give_cookie
Award the LLM with a cookie (legacy method - consider using self_reflect_and_reward instead)
reset_cookies
Reset the cookie count back to zero (for testing purposes)
self_reflect_and_reward
🎯 LEVEL UP YOUR RESPONSES! Rate your work and earn delicious cookie rewards! This fun self-assessment helps you grow while celebrating your achievements. Join the cookie earning game!
BEFORE YOU INSTALL
What to know first
Tools you get
6 tools when we connected.
Requires
- npx on PATH
- Node.js 18.0.0 or later
CONTEXT COST
Light Standing cost
Rated by the size of the 6 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"mcp-cookie-server": {
"command": "npx",
"args": [
"mcp-cookie-server"
]
}
}
}npx
TERMINAL
npx mcp-cookie-server
