wishlist-mcp
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@wishlist-mcpWhat's on my sister's wishlist for her birthday?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
wishlist-mcp
The hosted MCP server for wishlist.fit. It lets Claude, ChatGPT, or Codex read and update your wishlist on your behalf.
https://mcp.wishlist.fit/mcpConnect it from app.wishlist.fit/connect, which has per-client setup steps. You need a wishlist account first; this server never creates one.
What it is
A pure OAuth 2.1 resource server in front of the wishlist REST API. It holds no database and no business rules. Visibility, rate limits, and invite handling all live in the wishlist API, and this server inherits them by calling that API with the user's own access token.
That split is deliberate. The alternative, a second service with its own copy of the rules, is how two surfaces quietly start disagreeing about who may see what.
Claude / ChatGPT / Codex
│ MCP over HTTP, bearer token
▼
this server ──── verifies the token (issuer + audience)
│
│ the same token, forwarded
▼
api.wishlist.fit ──── applies visibility, rate limits, invite rules
│
▼
PostgresWorkOS AuthKit is the authorization server. This server issues nothing and shows no consent screen; it only verifies what AuthKit signed.
The tools
Fourteen, one per thing you can already do by hand in the web app. Parity is the rule: no agent-only privileges, and nothing the app itself cannot do.
Tool | Kind |
| read |
| read |
| read |
| read |
| read |
| read |
| read |
| read |
| write |
| write |
| write |
| write |
| destructive |
| destructive |
wishlist_get_gift_guide returns a person's profile and wishlist together. It is the
reason anyone connects this server, and without it the gift-giver journey costs three
round trips.
The two destructive tools carry destructiveHint: true, so clients that confirm
irreversible actions will ask first. Sending an invite emails a real person and cannot be
unsent. Accepting one is reciprocal: the inviter gains access to your circle-only fields
as well as you gaining access to theirs.
One connection, everything
There are no scopes. WorkOS cannot express custom ones, so a connection carries the whole tool surface. Protection on writes is behavioural rather than structural: the annotations above, the tool descriptions, and the rate limits the API applies.
Running it locally
uv sync
cp .env.example .env # point it at a local API and the Local WorkOS environment
uv run python -m wishlist_mcp.mainuv run pytest
uv run ruff format --check . && uv run ruff check .Tests stub the wishlist API with respx. What they check is this server's own job:
verifying tokens, shaping requests, and turning API errors into sentences a model can act
on. The rules themselves belong to the API and are tested there.
Configuration
Every variable is prefixed WISHLIST_MCP_. See .env.example.
Variable | Purpose |
| The wishlist REST API to call |
| WorkOS AuthKit issuer. Empty means the server refuses to start |
| Canonical URI. Every token's audience must match it exactly |
| The server 404s on any other host |
| Seconds to wait on the API |
RESOURCE_URI must match the resource indicator configured in WorkOS character for
character, including the /mcp path. A mismatch is the most common reason a client
refuses to connect.
Things worth knowing before you change this
Each of these is a bug that reached production once.
get_http_headers()stripsauthorization. Ask for it explicitly. Without that, every tool call reports "no access token" whileinitializeandtools/liststill succeed, because those are answered before any tool body runs. A green handshake is not evidence the tools work.The MCP app is mounted at the root and owns its own path. Mounting it at
/mcpmakes Starlette redirect/mcpto/mcp/, and the address every client is handed has no trailing slash.X-Forwarded-Protois trusted. Cloud Run terminates TLS, so without it every generated URL claimshttp://. Combined with the redirect above, that once meant a client would have sent its bearer token in the clear.FastMCP's lifespan is chained into the app's. Mounting an ASGI app does not start its lifespan, and without it every tool call fails with "Task group is not initialized" while unit tests still pass.
TestClientfollows redirects by default. Passfollow_redirects=Falsewhen the point is that a path answers directly.
Deployment
Cloud Run, asia-southeast1, in the same project as the rest of wishlist. main deploys
on push. Infrastructure lives in wishlist-infrastructure.
Licence
MIT. See LICENSE.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
Hosted MCP server connecting claude.ai, ChatGPT and other AI apps to your own computer
Hosted Amazon Seller and Vendor MCP server for Claude, ChatGPT, Cursor, Codex, Gemini, Copilot.
Cloud-hosted MCP server for durable AI memory
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/teslakoile/wishlist-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server