Connect an AI app with MCP

Introwise supports the Model Context Protocol (MCP), which lets compatible AI apps work with your Introwise account after you approve access. You can connect ChatGPT, Claude, Gemini Spark, or another remote MCP client using the Introwise MCP server:

https://mcp.introwise.com

Before you connect

You need:

• An Introwise expert account
• An MCP client that supports remote Streamable HTTP servers and OAuth
• Permission to open the Introwise sign-in and consent screens in a browser

The client discovers Introwise authorization settings automatically. You do not need to create an API key or paste an Introwise password into the client.

Choose the minimum access you need

Introwise shows the permissions requested by the app before you connect it:

• Read access (mcp:read) lets the app view Introwise data such as your account, sessions, clients, services, packages, payments, and activity.
• Write access (mcp:write) lets the app take actions on your behalf, such as changing booking-page settings, creating or updating offerings, creating or removing time off, or rescheduling and canceling sessions.
• Persistent access (offline_access) lets the app refresh its connection without asking you to sign in each time.

Start with read-only access. Approve write access only when you expect the app to take actions, and review any consequential action before confirming it.

Connect ChatGPT

Full custom MCP support, including write actions, is currently available in beta on ChatGPT web for Business, Enterprise, and Edu workspaces. A workspace admin or owner must publish the app before other members can use it. ChatGPT Pro offers narrower read/fetch MCP support, which may not expose the complete Introwise tool set.

1. In ChatGPT on the web, open Workspace settings > Apps > Create.
2. Enable developer mode if prompted.
3. Create a custom app and enter https://mcp.introwise.com as its MCP server URL.
4. Choose OAuth, select Scan Tools, and complete the Introwise sign-in and consent flow.
5. Review the detected tools, select Create, and publish the app from Workspace settings > Apps > Drafts.
6. Start a new chat, select the Introwise app from the tools menu, and try: “Show me my upcoming Introwise sessions.”

If you cannot create or select a custom app, ask your workspace administrator to check your plan, developer-mode access, and app permissions.

Connect Claude

Remote custom connectors are available in Claude on Free, Pro, Max, Team, and Enterprise plans. Free accounts are limited to one custom connector.

1. For an individual account, open Customize > Connectors, select +, and choose Add custom connector.
2. For a Team or Enterprise workspace, an owner must first add it from Organization settings > Connectors > Add > Custom > Web.
3. Enter https://mcp.introwise.com as the remote MCP server URL and select Add.
4. Select Connect, then complete the Introwise sign-in and consent flow.
5. In a conversation, select + > Connectors and enable Introwise for that conversation.
6. Try: “Show me my upcoming Introwise sessions.”

Connect Gemini Spark

Gemini custom apps currently require Gemini Spark access, a personal Google Account in the United States, age 18 or older, English, and Keep Activity turned on. Custom apps work only inside Gemini Spark tasks.

1. On a computer, open the Gemini web app.
2. Open Settings & help > Connected Apps. If that option is not shown, open Personal Intelligence > Connected Apps.
3. Under Custom apps for Spark, select the option to add a custom app.
4. Enter https://mcp.introwise.com as the MCP server URL and select Next.
5. Follow the prompts to sign in to Introwise and review the requested permissions. You do not need to enter OAuth client credentials.
6. Start a Spark task and try: “Show me my upcoming Introwise sessions.”

Connect another compatible client

Enter https://mcp.introwise.com as the remote MCP server URL. The client must support Streamable HTTP, OAuth discovery, Dynamic Client Registration, and the authorization code flow with PKCE. You do not need an Introwise API key.

If you are building a client that makes OAuth requests manually, include prompt=consent when requesting offline_access.

What the connection can do

Depending on the permissions you approve, the Introwise MCP server can:

• View, cancel, and reschedule sessions
• View session bookings
• View, create, and update services, packages, and discount codes
• View series
• View your account, booking page, clients, workflows, and activity
• View recent payments and revenue summaries
• Find available booking times for a known service and date range
• View, create, and remove time off
• Update booking-page settings

The server cannot create bookings or issue standalone refunds. Stripe balance is not exposed through MCP; use Stripe for current balance details.

Use write access safely

Write actions can affect clients and connected services. Canceling or rescheduling a session may lead to notifications, refunds, calendar changes, or workflow activity.

Before rescheduling, ask the app to find available times for the service. Rescheduling does not automatically verify the new time against your availability rules, existing sessions, time off, or connected calendars.

Before approving an action:

• Ask the AI app to summarize exactly what it will change.
• Check session, client, date, time, and timezone details.
• Confirm whether clients will be notified or payments may be affected.
• Avoid combining unrelated changes in one request.

Troubleshooting

The client says unauthorized

• Reconnect the Introwise server and sign in again.
• Confirm the server URL is exactly https://mcp.introwise.com.
• For read tools, approve mcp:read.
• For write tools, approve the additional mcp:write permission.

A write action needs more access

Your connection may be read-only. Approve the additional write permission when the client asks, or reconnect and include mcp:write. Do not grant write access if you only want the app to answer questions.

The connection expired

Introwise access tokens expire after one hour. Reconnect the app if it cannot refresh its connection. If you trust the client to remain connected, approve offline_access during authorization so it can request refreshed access without asking you to sign in each time.

A session cannot be found

Ask the app to list sessions first, then retry using the exact session ID from the result.

Requests are temporarily rate limited

Wait for the delay shown by the client or the server's Retry-After value before retrying. Avoid repeated polling or duplicate requests. The server limits authenticated requests to protect your account and service reliability.

Disconnect an app

Remove or turn off Introwise in the AI app's connector settings. This stops normal use through that app, but it does not guarantee that the server-side Introwise authorization has been revoked.

Contact Introwise support to revoke the server-side authorization, especially if you lost access to a device or account. Revocation prevents the app from refreshing access, but an access token that was already issued may remain valid for up to one hour.

If the problem continues, contact Introwise support and include the client name, tool or action you attempted, and the approximate time of the error. Never send an access token or authorization code to support.