Skip to main content

Connect an AI app

Use this server URL in your AI app's remote MCP or custom connector settings:

https://v3.holyshift.ai/mcp

You need a HolyShift account and an app that supports remote MCP over HTTP with OAuth. The availability of custom connectors depends on the app and your plan.

Preview

Client compatibility is still being verified. The server URL and authorization flow below describe the current interface; they are not a guarantee that every client supports it.

Connect your account​

  1. Open your AI app's connector or remote MCP settings.
  2. Add a server named HolyShift with the URL above. Choose OAuth if the app asks how to authenticate.
  3. Follow the sign-in link to HolyShift and sign in to the account whose projects you want to use.
  4. On the consent page, check the app name and the destination receiving the connection, then allow access.
  5. Return to your AI app and ask: “List my HolyShift projects.”

If the app requests a manually supplied API key, see whether it has a separate OAuth or remote connector option. Your HolyShift password and console session are not MCP API keys.

Choose a project​

Tell the app which business you mean. If you have several projects with similar names, ask it to show the project links first.

For example:

Use my HolyShift project for our subscription meal service. Ask what we know about the customer and the strongest objections to buying.

HolyShift usually takes one to several minutes to answer. Your app should check for the result about every 30 seconds. If it tells you that HolyShift needs your input, open the conversation link and answer or approve there.

Disconnect an app​

Open Settings → Connected apps in HolyShift and disconnect it. Its access and refresh tokens stop working immediately.

Disconnecting prevents further access. Work already submitted may continue, and it does not remove information the other app has already received.

For a custom integration, continue with the developer docs.