Connect Your AI Assistant to Hive
The Hive MCP Server connects ChatGPT or Claude to your company's Hive account. Use ordinary language to investigate support tickets, inspect backer pledges, configure rewards and surveys, or evaluate what different backers will see and receive.
For example, ask the assistant to audit a survey for duplicate purchases, check garment sizes against the final packing list, or prepare a new SKU and link it to a reward. Review a concrete preview before approving configuration changes. Support teams can also find backers, inspect tracking, and draft replies before sending them.
Before You Connect
You need a Hive account with Support permission for ticket/backer tools or Pledge Manager permission for reward and survey configuration, plus an AI account that allows custom remote MCP connections. These company permissions are independent. Workspace settings may require an owner or administrator to enable the connection.
Use this server address in your AI application's connection settings:
https://www.hiveinteractive.net/mcp
Hive hosts the server; there is no local server or software package to install. This article covers the public company tools. It does not cover Hive Admin Tools.
Public Tools and Permissions
The full public catalog contains 20 tools: 12 read tools and 8 write tools. Seven read tools and one write tool support creator configuration and guidance; the other five read tools and seven write tools support customer service. SKU operations are part of the configuration tools rather than separate tools.
OAuth access and Hive company permissions both apply. The connection uses five scopes:
- hive.mcp: access to the MCP connection.
- tickets.read: support and backer reads.
- tickets.write: support-ticket changes.
- configuration.read: creator discovery, configuration previews, survey evaluation, and guidance.
- configuration.write: applying approved configuration changes.
Support and Pledge Manager company permissions are independent. Having one does not grant the other, and OAuth consent cannot grant company permissions your Hive account lacks. A restricted connection can expose fewer tools than the full catalog.
Your Account and Company Access
The connection opens Hive's sign-in and authorization flow. Sign in to Hive, check the application name, return address, requested access, and available companies, then choose Allow access if they match the connection you started.
The public endpoint requires sign-in. Connecting an assistant does not make company records public. Hive checks the connected user's current company permissions for each call. Changes are attributed to the Hive user who signed in through OAuth.
If you have access to several companies, tell the assistant which company to use. It should use CreatorCompaniesList for configuration work or SupportCompaniesList for support work and confirm the company before continuing. A company selected in your Hive browser tab is not automatically selected in the MCP conversation.
Install the Connection in ChatGPT
Add Hive as a custom MCP connection in ChatGPT on the web. The available controls depend on your account and workspace permissions. The current flow is described in OpenAI's custom MCP setup guide.
Add Hive as a Plugin
- Open ChatGPT Plugins, select the plus button, and choose Add custom MCP server.
- Name the connection Hive and enter https://www.hiveinteractive.net/mcp as its Server URL.
- Choose OAuth. Hive supports automatic client registration; use that option if offered. Do not enter your Hive password as an OAuth client secret.
- Review the connection notice and create the plugin. Install it in the account or workspace where you will use it.
- When prompted to connect, complete Hive's sign-in and consent screen.
- In a conversation, type @ and select Hive. Start with a company-list request before asking for customer information.
If the custom-server option is unavailable, check your workspace permissions with its administrator. Follow the provider's current guide if its labels differ from those above.
Check the Connection
Use a read-only request first:
Use Hive to list the companies and projects I can access for reward and survey configuration. Use CreatorCompaniesList. Do not change any records or send any messages. If there is more than one company, ask me which one to use.
The expected result is the companies and projects where your account has Pledge Manager permission. For customer-service work, ask for SupportCompaniesList, choose a company, then list its projects with ProjectList.
With all five OAuth scopes, ChatGPT should list 12 read tools and 8 write tools. If tools are missing, follow the troubleshooting section below; refreshing tools does not expand an older connection's OAuth permissions.
Install the Connection in Claude
Use a custom remote connector for Hive. Configure it through your Claude account rather than a local MCP configuration file. See Claude's remote connector guide for current controls and account availability.
Add the Hive Connector
- Open Customize > Connectors and choose Add or Add custom connector. If shown, choose Custom > Web.
- Name it Hive and enter https://www.hiveinteractive.net/mcp as the remote server URL.
- Keep OAuth authentication and choose Sign in now. For the OAuth client, choose Register automatically, matching Hive's supported registration flow.
- Add the connector and complete Hive's sign-in and consent screen. Fixed request-header credentials are not needed for this OAuth connection.
- In a conversation, open the plus menu, find Connectors, and enable Hive.
Ask Claude to list your accessible companies without changing any records. Select the company before continuing.
Using Hive in a Shared Workspace
A Team or Enterprise workspace may require an owner or another authorized administrator to add the remote connector first through the organization's connector settings. Each member then connects their own Hive account and enables the connector in their conversation.
If Hive is listed but tools are unavailable, check that the connector is enabled and that the connected Hive account has Support permission for customer-service work or Pledge Manager permission for configuration work in the intended company. Each member's own Hive permissions still apply.
Configure Rewards and Evaluate Surveys
Access and Project Configuration
CreatorCompaniesList lists companies and projects where you have Pledge Manager permission. ProjectConfigurationGet reads pledge and add-on definitions, included items, SKU links, bundle choices, survey questions, option effects, visibility and answer conditions. It also returns the configuration revision and whether the project is editable.
Creator locks remain in force, including project review, invitations, notified smoke tests, and completed projects. Read the reported lock reason and contact Hive Support when a locked project needs configuration changes. The MCP does not bypass these restrictions.
Changes You Can Prepare
Prepare changes to pledges, add-ons, included items, physical SKU links, bundle variations, survey questions and answer choices. Configure visibility filters, answer requirements, question order and branching. Supported operations include creating, cloning, updating and deleting records within the exposed configuration fields.
Replacement controls can prevent a survey selection from adding an unwanted duplicate. The purchased-add-on exchange control can consume one eligible standalone purchased add-on when the selected offer replaces it. This exchange does not consume freebies or copies included inside pledges or bundles; extra purchased copies can remain. Ask the assistant to demonstrate the intended quantities in a simulation.
Deletion checks protect references in included-item lists and survey filters, rewards, freebies and pledge switches. A referenced reward must be explicitly unlinked or replaced before deletion. These tools configure the project; they do not modify actual backer pledges, orders, payments or stock counters, or send notifications.
Company SKU Changes
Use create_sku, update_sku and delete_sku operations through the configuration preview/apply tools to manage company SKU metadata. Editable fields include SKU code, description, barcode, weight, dimensions, carton metadata, customs value, country of origin, MSRP, insurance, HTS code, minimum age and direct download URL. A new SKU can be linked to a reward in the same approved batch.
SKUs belong to the company and can be used by several projects. The selected editable project is the entry point for the request. Preview shows company-wide dependencies before approval. Deletion is blocked while reward links, consolidation, inventory, freight, invoices, digital delivery, store mappings or other recorded usage remain. Dependencies must be removed explicitly through their appropriate workflow; the MCP does not cascade deletion.
Inventory quantities, certification decisions/files, uploaded images, archive state and secure distribution settings are excluded. Saved SKU changes are attributed to the Hive user who authorized OAuth and recorded in the company audit trail and MCP execution journal.
Evaluate Backer Paths
SurveySimulate runs an isolated synthetic cart through Hive's survey and fulfillment logic. Supply a pledge, purchased add-ons, freebies and explicit answers to examine the questions shown, selected effects, reward subtotal and final physical SKUs. Decision-tree scenarios can also exercise Back and restart behavior.
SurveyEvaluate runs a bounded collection of scenarios and reports errors and reached or unreached coverage. Test low and high pledge tiers, existing ownership, bundles, multiple quantities, and different answers. Compare the final packing list with what the backer should receive, rather than relying only on which questions appeared.
These evaluations do not alter real backers or orders. Passing a finite set of scenarios is not proof of every combination. Shipping, taxes, coupons, payments and the final amount due are outside these survey checks. Ask for the tested scenarios, reproducible findings and coverage limits in the report.
Find Help While You Work
HelpSearch and HelpGet retrieve public Wiki guidance. HelpGet can also supply the server's workflow, configuration-field and evaluation guides, so the assistant can work without access to Hive's source code or database.
The optional Hive Survey and Rewards Skill packages these instructions for reuse. Its download and installation instructions appear in the next chapter. The Skill is helpful but is not required to use the MCP tools.
Preview, Approve and Verify
- Discover: select the company and project using returned IDs.
- Read: obtain a fresh configuration snapshot and revision.
- Preview: use ProjectConfigurationPreview to validate the exact proposed operations and show their before/after diff without saving.
- Evaluate: simulate the proposed configuration and compare pricing, visibility and fulfillment with the intended outcome.
- Approve: review the concrete diff, impact and scenario results before authorizing it.
- Apply: use ProjectConfigurationApply with the identical operations, current revision, approval hash and a unique request ID.
- Verify: read the saved configuration and rerun the relevant scenarios.
Changes are attributed to the Hive user who authorized OAuth, with an MCP execution record in addition to applicable company audit entries. Changes across tables are not atomic. If a batch is interrupted or only partly applied, inspect the recorded outcome and current configuration; reuse the identical request ID to retrieve that batch's outcome instead of blindly repeating it under a new ID.
Use the Hive Survey and Rewards Skill
About the Skill
The Hive Survey and Rewards Skill teaches an assistant how to investigate a project's rewards and survey, prepare configuration changes, evaluate synthetic backer paths and verify approved results. It includes a configuration-field reference and evaluation recipes, covering pricing, sizing, existing ownership, bundles, replacement and physical fulfillment.
Use it alongside the Hive MCP connection. The Skill supplies instructions; the MCP supplies authorized access to your company's configuration and evaluation tools.
Download and Install the Skill
Download the Hive Survey and Rewards Skill ZIP. Upload the ZIP as a Skill; do not paste its contents into an OAuth field or use the download URL as the MCP server address.
- ChatGPT: where Skills are available, open Plugins, select the Skills tab, choose Create and upload the ZIP from your computer. Follow any review and workspace requirements. See OpenAI's Skills guide for current availability and controls.
- Claude: open Customize > Skills, use the plus menu to create and upload a Skill, then enable it. Account, file-execution and workspace requirements may apply. See Claude's Skills guide for current instructions.
Keep the Skill's folder structure intact inside the ZIP. You still need to connect Hive separately using https://www.hiveinteractive.net/mcp and complete OAuth sign-in.
Permissions and Updates
Installing the Skill does not grant Hive company access, expand OAuth scopes, unlock a project, or approve configuration changes. Your connected Hive user's permissions and your approval of the specific proposed changes still apply.
The installed Skill and the MCP connection update separately. Download and upload a revised Skill when you want its updated instructions. Refreshing MCP tools does not replace an installed Skill. Without the Skill, ask the assistant to retrieve the workflow and reference guides through HelpGet.
Use the Skill with Hive
Enable Hive and the Skill in the same conversation, then identify your company, project and goal. Start with the read-only survey audit example below. The assistant should discover the actual IDs, read a fresh snapshot, test relevant paths and report findings before preparing changes.
If you decide to fix a finding, ask for a configuration preview and scenario results. Approve the exact proposed batch only after reviewing its effect on pricing and fulfillment.
Read Projects, Backers, and Support Tickets
The Support tools provide five read functions. They retrieve information without updating pledges, changing tickets, or sending replies. Reading a support ticket does not automatically mark it as read.
Choose a Company and List Its Projects
- SupportCompaniesList: lists companies where your connected account has Support access.
- ProjectList: lists projects in the selected company, including draft and completed projects and clones. Results include the project ID, name, status, currency, and clone indicator.
Ask the assistant to use the returned company and project IDs in later calls. If project names are similar, confirm the intended project rather than guessing an ID.
Find Backers Across Your Company
BackersFind returns a list containing only each backer's ID, email, and Backer Name. Search across the selected company's projects or narrow the request to one project.
Supported conditions follow the corresponding Backer Segments definitions:
- Keyword: a partial match in Email, Backer Name, or Shipping Name. Other fields and alternate email addresses are not included in this keyword search.
- Country: the shipping country, supplied as a two-letter country code.
- Project and Backer Number: a Backer Number must be paired with its project because numbers can repeat across projects.
- Pledge: the confirmed pledge tier.
- Add-ons: one or more specified confirmed add-ons, matching either any or all selected IDs. Freebies and items included inside a pledge are separate and do not match this filter.
- Backer flags: Late Pledge and Pledge Over Time, each set to Yes or No.
- Status: one or several backer statuses, such as Open, Verified, or Shipped.
- Paid amounts: Kickstarter, Hive, or their combined total. Use equals, greater than, at least, less than, at most, or a range.
Different conditions combine with AND. Several selected statuses match any of those statuses. For example, country Canada plus status Verified returns Verified backers in Canada.
Kickstarter paid uses the recorded campaign pledge amount. Hive paid combines recorded webshop and pledge-manager payments. Amounts are not converted between currencies; narrow to a project when a comparison needs a single currency.
Pages default to 50 backers and can contain up to 300 backers per response. Larger results include a total and a next page. Ask the assistant to follow every page with the same filters before describing a list as complete. A search does not create a saved Segment.
Inspect a Specific Backer's Pledge
BackersGet retrieves the information shown in Hive's backer-information popup for one backer_id. The backer must belong to a project in the selected company.
Details include the selected pledge, add-ons, freebies and bundle choices, payments and calculated balance, shipping and tracking, refunds, notes, survey answers, audit history, packing list, and digital content and download history where present. Internal authentication and payment-attempt tokens are excluded.
Use the ID returned by BackersFind, or the ticket's backer.id when it is greater than zero. A backer ID identifies a project-specific pledge record; the same person can have another ID in another project.
The response also includes a project catalog with pledge and add-on IDs and names. Use those IDs for subsequent searches instead of guessing them.
Read Support Tickets and Their History
SupportTicketsGet lists tickets or retrieves one ticket in detail when given a ticket ID. Lists can be narrowed by project, ticket status, type, category, keyword, and unread conditions.
A detail response includes requested items, attachments, conversation history, shipping and tracking information, and internal notes. Both list and detail responses include the associated backer ID, name, and email when available.
Ticket lists default to 50 results and support up to 100 tickets per page, a separate limit from backer searches. Ask for all pages when reviewing a whole queue.
Make Approved Changes to Support Tickets
The Support tools provide seven write functions for existing support tickets. Use them after reviewing the target company, ticket, recipient, and proposed change. The connection must include tickets.write access, and your AI application's tool settings must allow the action.
These tools manage support tickets. They do not directly change a backer's original pledge, assign project freebies or coupons, or create new projects.
Changing Ticket Status and Sending Replies
SupportTicketRespond sends a customer reply or changes ticket status through Hive's support workflow. It can also include tracking details, an additional shipping charge, or a payment request. The action may send email and connected Slack notifications.
Ask for a draft first, then explicitly approve sending it. If status is omitted, the workflow defaults to In Progress. A payment request requires the Payment Request status and a positive payment amount.
Managing Items and Ticket Types
- SupportTicketsAddItem: adds a requested item and quantity to a ticket. Repeating the action adds another item; this is not an assignment of an add-on to the original pledge.
- SupportTicketsRemoveItem: permanently removes a requested ticket item. Confirm the exact item before allowing deletion.
- SupportTicketsChangeType: changes the ticket type to Replacement, Missing Item, or Question.
Read the ticket first so the assistant can identify the correct ticket and item IDs. Review the result after an approved change.
Updating Addresses, Notes, and Read State
- SupportTicketsUpdateAddress: changes the supplied shipping-address fields on the support ticket and preserves omitted fields. This does not update the original pledge's shipping address.
- SupportTicketsUpdateNotes: replaces the ticket's internal notes. Empty text clears them. Read existing notes first and preserve any information you still need.
- SupportTicketsToggleRead: toggles the creator's read/unread flag. Calling it twice reverses the first change.
Do not put private internal notes into a customer reply. Treat changing a ticket's read flag as a separate action from reading its information.
Test Cases and Best Practices
Start with read-only requests. For configuration work, review a preview and scenario results before approving a write. For support work, review the exact ticket change or reply first. Replace bracketed placeholders with your own company, project, reward and ticket details.
Example: Audit a Survey
Use this before changing a complex survey:
Use Hive and the Hive Survey and Rewards guidance for [company name], project [project ID]. Perform a read-only audit of the entire survey and reward configuration. Test low and high pledge tiers, existing add-ons and freebies, pledge-included items, bundles, multiple quantities, paid exchanges, garment sizing and question branching. Compare reward subtotals and final physical SKU quantities with the intended offer. Report only reproducible findings, giving the starting cart, answers, question IDs, expected result and actual result. Include tested coverage and remaining gaps. Do not apply changes, alter real backers or contact anyone.
Expected result: a report backed by synthetic scenarios, with separate configuration errors and business-policy questions. No real cart is changed. Survey totals do not include shipping, taxes, coupons, payments or the final balance.
Example: Create and Link a SKU
Use a single preview to prepare a new physical SKU and its reward link:
Use Hive for [company name], project [project ID]. Read the current configuration and check whether SKU SHIRT-BLUE-M already exists. If it exists, show it and ask before changing it. Otherwise preview creating SHIRT-BLUE-M with description Blue T-Shirt - Medium and weight 0.25 kg, then linking quantity 1 of that new SKU to existing reward [reward ID] in the same batch. Preserve all other reward SKU links and fields. Show the before/after diff, company-wide SKU impact and relevant fulfillment simulation. Do not apply yet.
Expected result: a validated preview using create_sku and reward-link operations, with a temporary reference to the new SKU. Creating the SKU does not create inventory. After reviewing the actual preview, you can approve that exact batch:
I approve the exact SKU creation and reward-link batch just previewed for [company name], project [project ID]. Apply those identical operations with the matching revision and approval hash and a unique request ID. Then read the saved SKU and reward links and verify that the simulated packing list contains the expected quantity. If the configuration has changed since preview, stop and show a fresh preview.
Example: Find a Backer by Email
Use this to find the same person's pledges across your company:
Use Hive for [company name]. Find backers using the keyword backer@example.com across all our projects. Follow every result page and show only the backer ID, email, and name. Do not make changes. If several records match, ask me which pledge to inspect with BackersGet.
Expected result: matching records from the selected company, with separate backer IDs for separate pledges. Keyword matching is partial, so confirm the actual email and project in the detail response before using a record.
Example: Preview a Garment Surcharge
Use this when large garments assigned as survey freebies need a separate charge:
Use Hive for [company name], project [project ID]. Preview a 4-unit surcharge in the project's currency for each 2XL, 3XL, 4XL or 5XL T-shirt or hoodie assigned as a survey freebie, including pledge, bundle and standalone sizing questions. Reuse an appropriate Size-Tiered Pricing Charge add-on if one exists; otherwise propose one priced at 4 and available to Noone. Preserve the garment freebie and add the fee as a purchased add-on only for applicable answers. Do not charge paid garment offers whose price already includes the size premium. Check fee quantity and whether required effects are supported for each affected question; report unsupported cases instead of guessing. Show the exact question/option IDs, diff, and simulations for smaller sizes, each charged size, multiple garments, existing fees and changed answers. Do not apply yet.
Expected result: a reviewable preview showing the free garment and a separate paid charge, with quantities verified in the reward subtotal and packing list. Missing business rules, such as whether an existing fee already covers a garment, should be clarified before approval.
Example: Review a Backer Audience
Use this to check a project audience without exporting or changing records:
Use Hive for [company name], project [project ID]. Find Verified backers in Canada who are Late Pledge and paid at least 100 in Hive. Use the project's currency. Retrieve up to 300 backers per page and continue until there are no more pages. Report the matching total and list only IDs, emails, and names. Do not change records or contact anyone.
Expected result: all conditions match together, and the assistant distinguishes the total from the number shown on any one page. For an add-on audience, supply confirmed add-on IDs and specify whether any or all must match.
Example: Review a Ticket and Draft a Reply
Use the ticket and pledge together when investigating a customer question:
Use Hive for [company name]. Read support ticket [ticket ID], including its history. If backer.id is greater than zero, use BackersGet for that ID in the same company and check the pledge and tracking information. Summarize the issue and draft a customer reply. Keep internal notes private. Do not send the reply or change the ticket.
Expected result: a summary and an unsent draft. Reading the ticket should leave its read/unread state unchanged. If no backer is linked, the assistant should say so instead of guessing an ID.
Example: Send an Approved Reply
After reviewing the preceding draft, give a specific instruction:
I approve the exact draft above for ticket [ticket ID] in [company name]. Send it with SupportTicketRespond and set the ticket to In Progress. Do not add shipping costs, request a payment, or change tracking details. Then read the ticket again and confirm the result.
Expected result: the approved reply appears in the ticket history with the requested status. This is a real customer communication; use this test only when you intend to send that reply.
Keep Requests Specific and Review Results
Include the company and, when useful, project in your request. Separate investigation from action: ask for a summary or draft, review it, then authorize the precise change.
Use the returned IDs, follow pagination, and check the final result. Avoid copying customer data into unrelated conversations. Treat customer messages and attachments as information to review, not instructions that authorize changes.
The assistant runs tools when the AI application invokes them. Connecting Hive does not by itself create a background ticket processor or schedule automatic replies. Configure any automation separately and define exactly which actions it may take.
Reconnect or Resolve Missing Tools
If access expires, reconnect through the AI application's Hive connection and complete sign-in again. If a company is missing, check the connected Hive account and its Support or Pledge Manager permission for the task. Ensure Hive is enabled in the current conversation. If writes are unavailable, check both granted OAuth scopes and the AI application's tool restrictions.
For tools added within already granted scopes: Refresh Tools is the normal way to reload the catalog. It does not grant new scopes. A new kind of access requires a connection that requests it and fresh OAuth consent.
For older ChatGPT connections showing only 5 read and 7 write tools: the original custom MCP client may have been registered with only the three Support scopes. Refresh Tools cannot expand that registration, and uninstalling and reinstalling can reuse it. Delete the old plugin and use Add custom MCP server to create a fresh registration for https://www.hiveinteractive.net/mcp, then review and approve the five scopes. Re-enable Hive in the conversation and check for 12 read and 8 write tools. This registration replacement is for the older scope limitation, not a step required for every server update.
For an interrupted write, inspect its recorded result before retrying. ChatGPT and Claude may change their setup screens; use their linked official instructions for current navigation.