Connect ChatGPT, Claude and Antigravity with MCP

What you can do with an AI assistant

Panther Hook supports direct remote Model Context Protocol (MCP) connections from ChatGPT, Claude and Google Antigravity. You do not need a marketplace plugin to connect a compatible MCP client. Once authorized, the assistant can use the Panther Hook tools that your Workspace, role and granted permissions allow.

For example, an assistant can list forms, inspect delivery statuses, summarize permitted lead activity, and help set up a lead pipeline. Allowed write tools can modify resources when you expressly request the operation. A connected assistant never gets blanket account access.

• Read: list available workspaces and forms, inspect sanitized submission summaries and delivery errors.
• Write: create or update supported resources only when OAuth scopes and Workspace roles permit it.
• Protected actions: destructive or sensitive operations may require a separate approval in the Panther Hook interface.

Your remote MCP endpoint

In Panther Hook, open Account → External AI access → Connect another AI application. Copy the Remote MCP server URL from the setup panel. The same HTTPS endpoint works with compatible clients; the OAuth grant is specific to the application and selected Workspace.

This is a remote, authenticated MCP service. Do not enter an API token into an AI chat, install a local backend, or expose your Panther Hook session cookies. The MCP client should open the Panther Hook authorization page in your browser.

https://ph-mcp-gw-9qryt8yw.ew.gateway.dev/mcp

Connect ChatGPT

Custom MCP app creation and READ/WRITE tool use can depend on your ChatGPT account, settings and product rollout. A successful OAuth screen alone does not prove tool discovery succeeded: make one authorized read tool call to confirm the connection. No marketplace listing is required for a custom connection when that feature is available.

• In ChatGPT, open the area for Apps or Connectors. Where your account supports custom MCP apps, choose the option to create or add a custom MCP connection.
• Use Panther Hook as the name and paste the remote MCP server URL shown above. Start the connection and follow the browser-based OAuth flow.
• Sign in to Panther Hook, choose the Workspace you want the assistant to access, inspect the permissions, then authorize.
• Return to ChatGPT, refresh the app/tool list if necessary, and request a harmless read such as “Show the Panther Hook Workspace I connected” using get_user_info or list_workspaces.

Connect Claude

If Claude reports an OAuth error, do not assume that a tool action completed or that the connection has permissions. Recheck the connector status and confirm the result with a fresh read from Panther Hook.

• In Claude, go to Customize → Connectors → Add custom connector (the label may vary by version).
• Enter Panther Hook as the connector name, paste the remote MCP server URL, and begin the connection.
• Complete Panther Hook OAuth in the browser: sign in, select your Workspace, and consent only to the scopes you need.
• Return to Claude and verify that Panther Hook tools are available. Start with get_user_info, list_workspaces or list_forms before requesting any write.

Connect Google Antigravity

An optional Antigravity plugin also exists, but installing it is not required for a direct MCP connection. Antigravity client menus and authentication flows can differ across releases.

• In Google Antigravity, open the MCP manager or Settings → Customizations and add a remote HTTP MCP server. Depending on your installed version, this may appear under custom MCP connections.
• Name it Panther Hook and use the remote MCP endpoint above; the transport is HTTPS Streamable HTTP, not a local stdio server.
• Use the client’s Authenticate or OAuth action. Sign in to Panther Hook, select the intended Workspace and approve the requested scopes.
• If your Antigravity version asks you to copy an authorization code from its callback page back into the app, treat that code as secret and complete the flow only in the official interface.
• Test the connection with get_user_info and list_workspaces. Do not treat server registration or an OAuth confirmation alone as proof that tools can execute.

Verify access and manage permissions

Workspace access is isolated per authorization. Access in one Workspace does not imply access to other Workspaces. Read-only connections do not silently become write-enabled.

• Ask your assistant to run get_user_info and list_workspaces. Confirm the Workspace name rather than relying on a guessed Workspace ID.
• Try a read-only request such as “List my forms in this Workspace.” This tests native tool discovery and account authorization without modifying customer data.
• Only request a write when you intend to change something. The client must have the correct write scopes, and the Panther Hook role/plan rules still apply.
• For operations that require Human Approval, open the first-party approval link, review the proposed change and verify completion. A proposal is not a completed action.
• To inspect or revoke access, go to Account → External AI access. Connections are shown with their Workspace, granted permissions and last-used time. Disconnect any authorization you no longer recognize or need.

Troubleshooting and availability

• Connection or authentication fails: confirm that you are using the exact remote /mcp URL, your client supports remote MCP and its OAuth flow is enabled.
• OAuth succeeds but tools are missing: refresh the custom connector and confirm tools/list works in that client. Account/client support may differ.
• Permission denied: verify the authorized Workspace, requested read/write scopes, Workspace role and plan allowances.
• A tool reports waiting for approval: complete the Panther Hook approval step before interpreting it as an executed operation.
• For troubleshooting, provide the client name, approximate time, error category and sanitized status. Never share OAuth codes, bearer tokens or lead personal information in support messages.