Answers for What Comes Next

Use a specific Workspace and target record. Example requests:

• “Use Giftpack to show my Workspaces, then list campaigns in [Workspace].”
• “Find [order] in [Workspace] and check tracking for its recipients.”
• “Summarize [Storefront] sales from October 1–21, 2026, in Asia/Taipei time and USD. Include data limitations.”
• “Export the supported product report for [Storefront] for October 1–21, 2026, as Excel.”

Replace bracketed text with your own record names or identifiers. First confirm the correct account and Workspace; available results and exports depend on permissions and deployment. Ask for metric definitions, smaller pages, or narrower dates when needed.

For support, include the assistant name, time and timezone, exact error message, and affected feature. For missing tools, include the visible tool list if it contains no sensitive data. Omit passwords, tokens, client secrets, and private recipient details.

Depending on the deployed version and your permissions, User MCP can read Storefront sales, audience, funnel, operations, product, and category metrics, plus metric definitions. It can also review permitted Contribution amounts, Workspace pooled funds, transfer histories, and allocation summaries.

For comparisons, ask for separate queries for the selected stores or periods and use consistent dates, timezone, currency, and metric definitions. Results reflect available source data; ask about coverage and limitations before drawing conclusions.

Supported Storefront reports and product data can be exported as Excel workbooks. File delivery depends on whether your assistant can decode the returned file content. Do not assume every report type or file-delivery method is supported; narrow oversized requests.

This service does not provide automatic monitoring, scheduled notifications, forecasting, attribution, or profit analysis. It reads financial records but does not execute transfers or other financial changes.

Check the symptom before retrying:

• OAuth registration or sign-in fails: verify the exact HTTPS server URL, restart connection setup, use CIMD without manual credentials, and leave OpenID options off. In Claude, choose its published identity. Send persistent registration or callback errors to Giftpack support.
• Sign-in is requested again: reconnect and approve access. A tool refresh cannot repair expired or revoked authorization.
• Server unreachable: verify that the URL ends in /mcp/user. Opening it in a browser is not a complete MCP test. Persistent failures need a service and network-access check.
• Access denied: confirm the connected account and Workspace. Ask its administrator to check membership and operation permissions; OAuth consent does not override them.
• Feature missing: enable Giftpack in the chat, refresh tools, review tool permissions and organization restrictions, then retry with the Workspace and feature named. The deployed version may differ.
• Empty or oversized result: verify dates, filters, and records; request smaller pages or narrower reports. An error does not prove records are absent, and missing tracking does not prove delivery.

These actions solve different problems:

• Refresh tools when available actions or their inputs appear outdated after a service update.
• Reconnect when authorization has expired or been revoked, or sign-in is required again.
• Rerun the query to obtain newer business data. Refreshing tools does not update earlier answers.

In ChatGPT, open Giftpack in ChatGPT Plugins, select Refresh, review the tool list, then retry in a new chat with Giftpack selected. This applies to a directly connected custom MCP server. For managed connections, ask the administrator to review and make updated tools available. See OpenAI’s metadata refresh instructions.

In Claude, open Customize → Connectors or Settings → Connectors, select Giftpack, and look for ⋮ → Refresh tools list, if available. Review Tool permissions and retry in a new chat. If tools remain missing, reconnect; consult your administrator before removing a shared connector.

Use these settings for Giftpack User MCP:

• Server URL: https://client.giftpack.ai/mcp/user
• Authentication: OAuth
• Client identity: CIMD (Client ID Metadata Documents) for ChatGPT and Claude
• Read scope: mcp:read
• Manual client ID and secret: leave empty when using CIMD
• OpenID Connect: leave off; do not request openid or an ID token

Giftpack does not provide Dynamic Client Registration (DCR) for this flow. In Claude, use its published identity rather than Register automatically when that choice requests DCR.

Sign in with your own Giftpack account and review consent. Permissions are checked when each tool runs. Broader scopes advertised by an authorization server do not make this User MCP resource a write or administration service.

Never put passwords, access tokens, or client secrets in prompts, support messages, or the server URL. See the User MCP resource metadata.

These steps cover Claude’s hosted connector flow on the web and in Claude Desktop. They do not cover Claude Code’s separate client identity or local callback flow.

1. Open Customize → Connectors → + Add → Add custom connector.
2. Enter Giftpack AI and https://client.giftpack.ai/mcp/user, then continue.
3. Review authentication and choose Sign in now. If an OAuth client choice appears, select Use Claude’s published identity. Leave manually supplied client credentials empty, including in Advanced settings in older interfaces.
4. Add the connector, sign in to Giftpack, and approve access.
5. In a new chat, use + → Connectors to enable Giftpack, then ask for your accessible Workspaces.

For Team or Enterprise, an authorized owner or administrator first adds the connector through Organization settings → Connectors → Add → Custom → Web. Members then connect individually. Organization policies and interface labels can vary.

See Claude’s custom connector instructions and CIMD authentication documentation.

You need a ChatGPT account or workspace that permits custom MCP connections. You do not need to install a local server or obtain separate OAuth client credentials from Giftpack.

1. Open ChatGPT Plugins, select +, then Add custom MCP server.
2. Enter a name such as Giftpack AI, a description, and https://client.giftpack.ai/mcp/user.
3. Choose OAuth and CIMD discovery. Leave manually supplied client ID and secret fields empty; leave OpenID options off.
4. Review the connection notice, continue, and select Create as a plugin. Complete Giftpack sign-in and consent when prompted.
5. Review the discovered tools and install the plugin.
6. Start a new chat, type @, select Giftpack, and ask it to list your accessible Workspaces.

Menu labels can vary by account and version. If creation is unavailable, ask your ChatGPT administrator about custom-connection policies. See OpenAI’s connection instructions.

Giftpack User MCP connects a compatible AI assistant to your Giftpack account through the Model Context Protocol (MCP). Ask in natural language to read existing records and generate supported exports.

Depending on the deployed version and your permissions, you can explore:

• Your account, Workspaces, collaborators, roles, and permitted profile, company, settings, and credit information.
• Members, groups, teams, departments, and offices.
• Campaigns, gifts, recipients, gift choices, reviews, statistics, Marketplace orders, and available shipment tracking.
• Wallets, credit histories, transfers, transactions, support tickets, and ticket messages.
• Storefronts, categories, products, associated orders, permitted manager and Contribution settings, analytics, pooled funds, and allocation histories.
• Supported Storefront reports and product-data exports.

The service does not create campaigns, place orders, transfer funds, edit records, or reply to tickets. Use the Giftpack application for those actions. Access follows your current Workspace membership and operation permissions; connecting an assistant grants no additional access.

Giftpack can support SSO and enterprise identity-management requirements for applicable enterprise deployments. The exact method, such as SAML or another supported configuration, depends on the customer environment and current platform capabilities. Security and IT teams should confirm identity-provider compatibility, user provisioning, access-control requirements, and rollout scope during implementation. SSO should not be assumed to be enabled on every plan or workspace by default.

Administrators can review program and operational metrics relevant to the modules in use. Examples include invitations, claims or redemptions, spend and budget utilization, order status, delivery exceptions, inventory, participation, and recipient feedback where collected. Reporting is most useful when the organization defines its success metrics at implementation. Giftpack can then structure views or exports around the business question, such as participation, fulfillment performance, merchandise movement, or program efficiency.

Giftpack can support bulk recipient imports and large campaign creation so teams do not need to enter people one at a time. Depending on the workflow, data may be uploaded from a structured file, synced from another system, or provided through an integration. Before launch, validate required fields, duplicates, country information, eligibility, budget, and any personalization or delivery rules. For very large programs, Giftpack may stage the launch or validate a test batch first to reduce operational errors.

Yes. Giftpack can automate recurring gifting or recognition moments such as employee onboarding, birthdays, work anniversaries, customer milestones, closed-won opportunities, renewals, or other lifecycle events when the necessary source data and trigger are available. Automation can come from an integration, scheduled rule, imported data, or another approved workflow. Companies still control eligibility, budget, gift rules, timing, and exceptions so an automated trigger does not bypass internal policy.

Yes. Giftpack provides APIs and developer documentation for integrating gifting, rewards, recipients, orders, and related workflows with enterprise systems.

Developer resources

• Giftpack API
• API Reference Available endpoints, authentication methods, webhooks, and enterprise integration scope depend on the product and account configuration. For a production integration, share the systems, events, data flows, and security requirements so Giftpack can confirm the recommended architecture.

Giftpack can integrate with HR, CRM, marketing, collaboration, identity, and workflow systems depending on the use case. Integrations may be used to sync people data, trigger gifting or recognition events, automate lifecycle moments, or return status information to another system. Giftpack also supports a broad integration ecosystem, but the exact connector, authentication method, data fields, and automation behavior should be confirmed for the specific platform. Custom API-based integration may be appropriate when a native connector does not cover the required workflow.

Yes. Giftpack can support role-based permissions, approval workflows, and budget controls so different teams can operate within defined governance rules. Examples include separating administrators from campaign managers, requiring approval above a spending threshold, assigning budgets by team, restricting eligible products, or limiting who can view recipient data. The exact permission model depends on the enterprise configuration and integrations in use.

Giftpack’s platform can combine several operating modules depending on the program: corporate gifting, employee recognition and rewards, points or budget management, the global Marketplace, branded merchandise and custom production, Storefronts, warehousing and fulfillment, integrations, and reporting. Organizations do not need to use every module at once. A company may start with one use case, such as gifting or merchandise, and add recognition, Storefront, automation, or additional countries as the program grows.