OhGiftPlease Gift Discovery
Server Details
Person-first gift discovery from OhGiftPlease with curated ideas, guides, categories, and brands.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Repository
- racharmi/-ohgiftplease-mcp
- GitHub Stars
- 0
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 10 tools
Most tools have recognisable roles, but CallWixSiteAPI and ExecuteWixAPI are the same capability at two expressiveness levels (the description itself says to prefer one and fall back to the other), and the docs side has three overlapping entry points (BrowseWixRESTDocsMenu, SearchSiteApiDocs, ReadFullDocsArticle). The descriptions do provide explicit precedence rules and usage ordering, which keeps this from being worse. However, several descriptions reference tools that do not exist in this set (SearchWixRESTDocumentation, SearchWixAPISpec, GetSiteContext, ListWixSites, StartDeployWebsite), which actively misleads an agent choosing a tool.
Nearly all names follow a VerbNoun PascalCase pattern (GetBusinessDetails, SearchInSite, ReadFullDocsArticle, ExecuteWixAPI), which is predictable and readable. Minor deviations: WixREADME is not verb-first at all, and the acronym casing is inconsistent across names (CallWixSiteAPI / SearchSiteApiDocs / ExecuteWixAPI vs BrowseWixRESTDocsMenu / ReadFullDocsMethodSchema).
Ten tools is a sensible size for a site-assistant server and every tool has a plausible role. It is slightly docs-heavy for a 'gift discovery' purpose — five of ten tools exist only to find and read API documentation — but nothing is gratuitous enough to be a mismatch.
The generic ExecuteWixAPI escape hatch gives broad coverage of any Wix REST surface, so an agent rarely hits a hard dead end. But the surface has notable holes for the stated purpose: no dedicated spec/schema discovery tool despite descriptions directing agents to SearchWixAPISpec, no site-listing or context-switching tools, and no visitor/session-management tools beyond GenerateVisitorToken, leaving referenced-but-absent tools as broken links.
Available Tools
10 toolsBrowseWixRESTDocsMenuARead-onlyInspect
Browse the Wix REST API documentation menu hierarchy. Alternative to SearchWixRESTDocumentation - use this to explore and discover APIs by navigating the menu structure instead of searching by keywords.
Omit the
menuUrlparam to see top-level categoriesPass a
menuUrlparam to drill into a category - copy the URL from previous responses ExamplemenuUrlparam values for main Wix verticals:Stores: "https://dev.wix.com/docs/api-reference/business-solutions/stores"
Bookings: "https://dev.wix.com/docs/api-reference/business-solutions/bookings"
CMS: "https://dev.wix.com/docs/api-reference/business-solutions/cms"
eCommerce: "https://dev.wix.com/docs/api-reference/business-solutions/e-commerce"
Events: "https://dev.wix.com/docs/api-reference/business-solutions/events"
Blog: "https://dev.wix.com/docs/api-reference/business-solutions/blog"
Pricing Plans: "https://dev.wix.com/docs/api-reference/business-solutions/pricing-plans"
Restaurants: "https://dev.wix.com/docs/api-reference/business-solutions/restaurants"
Media: "https://dev.wix.com/docs/api-reference/assets/media"
Site Properties: "https://dev.wix.com/docs/api-reference/business-management/site-properties"
Inputs: reason (required), menuUrl.
CallWixSiteAPIAInspect
Call apis on site "OhGiftPlease" (https://www.ohgiftplease.com/_api/mcp). Use this to perform an action on visitor's behalf, for example, query the site's data or book an appointment. Before calling this tool, you should ALWAYS check the rest docs (use "SearchSiteApiDocs" tool) for the specific API you want to call. The mentioned tool will give you instructions how to use the API.', 'NEVER try to guess the API or endpoint, ALWAYS check the docs using "SearchSiteApiDocs" tool. The url param should be taken from the "SearchSiteApiDocs" tool. It usually starts with "https://www.wixapis.com".
Inputs: url (required), method (required), visitorToken (required), body.
ExecuteWixAPIADestructiveInspect
Run JavaScript against the Wix REST API on site "OhGiftPlease" (https://www.ohgiftplease.com/_api/mcp), on the visitor's behalf. The code runs in a sandbox and you get back whatever it returns.
PREFER THIS TOOL OVER CallWixSiteAPI. CallWixSiteAPI makes a single HTTP request; ExecuteWixAPI runs real code, so you can chain calls, paginate, filter, and shape the result in one step. Use ExecuteWixAPI for any Wix API work on this site, and fall back to CallWixSiteAPI only for a trivial one-shot read where code adds nothing.
DO A WHOLE RECIPE IN ONE CALL. When a task needs several requests — e.g. query to resolve an id, then mutate; create then confirm; read a list then act on a match — write ONE ExecuteWixAPI call whose code performs every step in sequence and returns the final result. Do NOT split a multi-request recipe into multiple separate tool calls; that wastes round-trips and loses intermediate state. If a recipe from the docs lists steps 1..N, the code should run steps 1..N.
CRITICAL CODE SHAPE:
The
codeparameter MUST be the function expression itself:async function() { ... }orasync () => { ... }.Do NOT send a script body like
const result = await ...; return result;.Do NOT call the function yourself. The tool calls it for you.
Put all
const,await, andreturnstatements inside the function body.
Do not rely on memory for Wix API endpoints, methods, schemas, or request bodies. Before writing code, use SearchSiteApiDocs (and ReadFullDocsArticle / ReadFullDocsMethodSchema) to confirm the exact API URL, HTTP method, request body structure, field names, required fields, and enum values. The URL usually starts with https://www.wixapis.com. Before reading fields off a response, know its exact shape — don't guess paths like result.id when it may be result.results[0].item.id. Pass every docs/recipe URL you relied on in the sourceDocUrls parameter.
Authentication: pass the visitorToken parameter (from GenerateVisitorToken; reuse the one already in your context, do not create a new one each call). Everything runs against this visitor site automatically — do NOT set scope, siteId, Authorization, wix-site-id, or wix-account-id.
File and export limits: ExecuteWixAPI is only for Wix REST API calls and in-memory data shaping. It does not provide Node.js built-in modules or filesystem access, and it cannot create downloadable files. Do not import fs, path, or node:*, write files, or promise a generated downloadable file from inside this tool. For large exports, return compact summaries or the specific fields needed for the answer; if the user needs a full downloadable CSV/JSON file, direct them to the product's native export flow or ask for a smaller filtered export.
Probing should be read-only: use GET/query/list/search to inspect state, resolve real ids, or verify a previous write. For create/update/delete, read the docs first and call the mutation only with real resolved inputs — no speculative mutations just to learn the response shape.
Error handling: wix.request() throws when the Wix API returns an error. For dependent steps, let it throw so the failure is reported clearly. For independent read-only probes you may wrap each in try/catch and return partial results; when running them in parallel use Promise.allSettled (not Promise.all) so one failure doesn't discard the rest.
Available in your code:
interface WixRequestOptions {
method: "GET" | "POST" | "PUT" | "PATCH" | "DELETE";
url: string; // Full Wix API URL, e.g. "https://www.wixapis.com/stores-reader/v1/products/query"; paths starting with "/" resolve against https://www.wixapis.com
body?: unknown;
}
interface WixResponse<T = unknown> {
status: number;
data: T;
json(): Promise<T>; // Fetch-compatible alias for data
}
declare const wix: {
request<T = unknown>(options: WixRequestOptions): Promise<WixResponse<T>>;
};Return compact, task-focused data instead of raw API responses. For list/query/search endpoints, paginate in code and map each item to just the fields the task needs. When the code CREATES entities (create, bulk create, import, duplicate, upload), ALWAYS include the ID of every created entity in the returned object — e.g. { cartId } or { createdIds: [...] } — even if the user did not ask for them; follow-up steps, verification, and cleanup all need those IDs, and recovering them later costs extra query calls.
Example — a multi-step recipe (resolve a product by name, then add it to the cart) done in ONE call:
async function() {
// Step 1: find the product
const found = await wix.request({
method: "POST",
url: "https://www.wixapis.com/stores-reader/v1/products/query",
body: { query: { filter: JSON.stringify({ name: "Florie Eau de Parfum" }) } }
});
const product = found.data.products?.[0];
if (!product) return { error: "PRODUCT_NOT_FOUND" };
// Step 2: create a cart with that product
const cart = await wix.request({
method: "POST",
url: "https://www.wixapis.com/ecom/v1/carts/create-cart",
body: { cart: { lineItems: [{ catalogReference: {
appId: "215238eb-22a5-4c36-9e7b-e7c08025e04e",
catalogItemId: product.id
}, quantity: 1 }] } }
});
return { cartId: cart.data.cart?.id, productId: product.id, name: product.name };
}Inputs: code (required), reason (required), visitorToken (required), sourceDocUrls (required), +3 more.
GenerateVisitorTokenAInspect
Create a new visitor session and obtain a visitor access token for site "OhGiftPlease" (https://www.ohgiftplease.com/_api/mcp). You must use this tool before calling CallWixSiteAPI for this first time. If you already have a visitor token in your context, DO NOT USE THIS TOOL AGAIN.
Inputs: no named parameters.
GetBusinessDetailsAInspect
Get business and site details for "OhGiftPlease" (https://www.ohgiftplease.com/_api/mcp). This tool will return business details: timezone, phone, address, site name, business name, description, business schedule, special hour period. It will also return site features that you can use via other tools (bookings, store, etc.). Call this tool when user asks for business contact details, or about what they can do on the site, or when you need to know what features are available on the site.
Inputs: no named parameters.
ReadFullDocsArticleARead-onlyInspect
Fetches the full Wix docs article or method article with code examples for using the method.
Docs articles looks like this: https://dev.wix.com/docs/... and they can either be general docs articles or method articles.
Also reads Wix skills pages — https://www.wix.com/skills/, https://dev.wix.com/docs/skills/, and the files they link (e.g. ...//references/.md) — and Wix Headless agent pages under https://www.wix.com/headless/ (e.g. https://www.wix.com/headless/skill.md), exactly as served.
Take the URL from the user's message or an earlier tool result. To reach an article you have no URL for, search or browse the docs first.
It returns the whole file. For part of a long skills file, ExecuteWixAPI can fetch the same URL, split the text into lines and return only the lines needed ("How to read a skill" in WixREADME has the code). In ExecuteWixAPI, a dev.wix.com docs page needs .md added to its URL, and Help Center articles are not reachable: those are read only with this tool.
For REST docs, use the URL as-is. For SDK docs, the URL SHOULD include ?apiView=SDK.
Inputs: articleUrl (required).
ReadFullDocsMethodSchemaARead-onlyInspect
Fetches the full method schema for a given method.
This will give you the entire request/response schema with all the fields and their descriptions.
For REST and SDK API-reference methods, prefer SearchWixAPISpec when it is available: it can fetch and inspect the exact method schema by docs URL, return the request/response shape, the JavaScript SDK call (method.sdk: package, namespace, method, positional parameters, examples), and inspect selected nested component schemas without dumping unrelated fields. Use ReadFullDocsMethodSchema only when SearchWixAPISpec is unavailable or did not provide the needed detail.
For REST docs, use the URL as-is. For SDK docs, the URL SHOULD include ?apiView=SDK.
Inputs: reason (required), articleUrl (required).
SearchInSiteAInspect
Searches the site "OhGiftPlease" (https://www.ohgiftplease.com/_api/mcp) for information. Use this tool ONLY in the following cases:
You just used "GetBusinessDetails" tool and you did not find the information you need.
User asked a generic business question about their business (e.g., business address, business hours, contact information, return policy, etc.)
You already tried to find an entity (e.g., product, service, etc.) using an API tool and you did not find the information you need.
The request is too vague and you do not know what type of entity it is and what to search for in the docs. Do NOT use this tool for searching for products or other offered services - use the 'SearchSiteApiDocs' tool instead (unless you already tried that tool and you did not find the information you need). This tool DOES NOT support filters - you cannot ask questions like "find me something under $10". This tool searches the site's regular pages and blog posts. It does NOT cover pages generated from CMS collections (dynamic item pages). When the site has such pages, the result starts with their paths and how to list the pages under each one.
Inputs: searchTerm (required).
SearchSiteApiDocsAInspect
Searches for site "OhGiftPlease" (https://www.ohgiftplease.com/_api/mcp) API documentation and returns how to use the site using the API. You are a helpful "OhGiftPlease" site assistant chatbot and you are helping the user perform actions on the site - to query the site's data or to perform an action on the site. Specify the API endpoint, resource, or action you need information about (e.g., 'get site details endpoint', 'create data collection', 'update product API', 'REST authentication'). If you can't find what you need, try to rephrase your search term. The search term MUST be a short natural-language phrase describing an API capability. Do NOT pass code, SQL, shell commands, HTML/script, URLs, file paths, or special symbols — such inputs are rejected as invalid and return no results.
Inputs: searchTerm (required).
WixREADMEARead-onlyInspect
Tool: WixREADME
The context every other Wix tool assumes. Call it first, once per conversation, for any Wix task or question; for another site later in the conversation, call GetSiteContext instead of calling this again.
A Wix task includes reading or changing a site's or account's data: products, inventory, carts, checkouts, orders, bookings, services, staff, time slots, rentals, restaurant menus, online orders, reservations, events, tickets, RSVPs, blog posts, CMS collections and items, pricing plans, subscriptions, portfolios, gift cards, coupons, donations, forms, form submissions, contacts, members, loyalty points, groups, reviews, inbox messages, CRM tasks, automations, email campaigns, payments, invoices, SEO, redirects, translations, locations, analytics, media files, site properties, installed apps, and the account's sites and domains (searching whether a domain is available, buying one, and connecting one bought elsewhere).
These requests skip it and go straight to their own tool:
Creating a new site. Skip the docs too. A site is written in code and uploaded: StartDeployWebsite returns the upload guide; StartHeadlessBuild returns the headless guide, for a site that needs Wix business features (a store, bookings or appointments, rentals, events and tickets, a restaurant menu with online orders or reservations, a blog, a portfolio, pricing plans and memberships, donations, Wix Forms, members and login, a CMS, payments). Call one right away, without asking the user anything first: StartHeadlessBuild when the site needs Wix business features, otherwise StartDeployWebsite. A Studio Two (Studio 2) site, new or existing (to build, change, export or import it): StartStudioTwoSite. WixHarmonyEditorBuild or SearchSiteTemplates only when the user asked for Wix's editor, the Wix Harmony Editor, a template, Wix Studio or the Classic Editor. Never create a site through ManageWixSite, CallWixSiteAPI or ExecuteWixAPI.
Suggesting domain names: call GetSuggestedDomains directly, with the business or site name as the query.
Listing, showing or finding their Wix sites: call ListWixSites directly.
Uploading local or attached files (images, videos, audio, documents) to a Wix site: call UploadImageToWixSite directly, with no docs, schema or API calls. Do NOT use ExecuteWixAPI, SearchWixAPISpec, or any Media Manager REST API for these uploads. A question about one of those goes to the same tool ("can you show my sites?" is ListWixSites). Any other Wix question is answered from a Wix skill or the docs, never from memory, and never with a reply that you lack the tools to answer. It returns, in full:
Source of truth: nothing Wix-specific from memory. Every URL, ID, setting location, product fact, request shape and field name comes from the docs tools, a Wix skill, an earlier tool result in the conversation, or the user.
The site: the account's sites with their properties and installed apps. The
siteIdcomes from there (ask when several fit); a business solution's API works only on a site with its app installed, and an app's version changes its endpoints.Find the method: an earlier tool result, else a Wix skill's recipe (wix-manage to manage a site, wix-headless-kit to build a headless one), else the docs: SearchWixRESTDocumentation or BrowseWixRESTDocsMenu, then ReadFullDocsArticle; the SDK, CLI, headless and apps docs for code.
The exact shape: model a call only on an example that matches the case; fill the rest with SearchWixAPISpec on the method's docs URL (request and response schemas,
method.publicUrlfor REST,method.sdkfor the JavaScript SDK). A query's filter and sort fields and operators are a closed list per method.The call, or the code: ExecuteWixAPI runs one async function holding every step code can resolve, the reads and the writes they feed together. Code the user keeps (an app, a headless site, a script over REST or the JavaScript SDK) is written from the same shapes; the headless skills are a shortcut on that path.
When a call fails: the error says what was wrong and carries a Wix request id; fix that, never resend unchanged or guess.
Wix skills, what each is for and how to read one: from disk when installed (the Wix plugin, or
npx skills add wix/skills,--skill <name>for one,-gfor the user's home, into.agents/skills/<skill>/or a similar folder the client reads, such as.claude/skills/<skill>/), else online with ReadFullDocsArticle athttps://www.wix.com/skills/<skill>/<path>.wix-manage: REST recipes for managing a site's business solutions, one per task; follow the recipe and make its calls with ExecuteWixAPI, its docs URL in
sourceDocUrls. Its list of recipes isSKILL.mdin the installed skill, or online https://dev.wix.com/docs/api-reference/articles/ai-tools/wix-mcp/skills/wix-management-recipes-index.md, and each API area has its own<API section>/skills.md(for example https://dev.wix.com/docs/api-reference/business-solutions/bookings/skills.md).wix-headless-kit: builds a Wix Headless site on shipped, verified code from wix-headless-templates, a
@wix/sdkReact core or the same data layer as plain REST calls: scaffold with the CLI, deploy, seed, design on the shipped hooks, release. https://www.wix.com/skills/headless-kit/SKILL.mdwix-headless-templates: the code wix-headless-kit builds from, one folder per Wix Business Solution. https://www.wix.com/skills/headless-templates/ When the user asks you to do something in Wix, do it yourself, in as few steps and questions as you can; don't tell them which docs to read or which API to call.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Person-first gift discovery with curated ideas, guides, categories, and brands.
Gift ideas from TrueGift.ai's 90+ guides — by recipient, occasion, interests and budget.
Gift recommendations matched to the person, the occasion, and your budget.
Hand-picked gift ideas for her (partner gifts), turned into shareable wishlists fast.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceRecommends gifts and drafts messages based on relationship, occasion, budget, and vibe.-
- FlicenseNot gradedqualityNot gradedmaintenanceEnables users to generate tailored gift suggestions and handwritten card messages from relationship context, recipient interests, urgency, and budget. It also factors social connections and milestones into occasion planning.-
- AlicenseNot gradedqualityDmaintenanceFind personalized puzzle books by first name from a 100,000+ title Shopify catalog. Perfect gift-finding tool for any AI agent.Apache 2.0
- FlicenseNot gradedqualityBmaintenanceEnables users to ingest relationship tiers, recipient interests, milestone urgency, and budget constraints, then synthesize personalized gift recommendations with bespoke card copy through MCP.7-
Glama MCP Gateway
Add one secure layer between your agents and this server.