Install the Innguma connector

Connect Innguma to your AI assistant by hand, with the server address below. You need an Innguma account; see what the connector does first.

The server address is:

https://mcp.innguma.com/mcp

Claude

For yourself (claude.ai or the Claude desktop app):

1. Open Settings → Connectors and select Add custom connector.
2. Name it Innguma and paste the server address. Leave the advanced settings as they are.
3. Select Add, then Connect, and sign in to Innguma (see Signing in).

In a chat, turn on Innguma in the tools menu and ask, for example, "What are my unread Innguma alerts this week?".

For your whole organization (Claude Team or Enterprise): an Owner adds the connector once in Admin settings → Connectors → Add custom connector, with the same name and address. Each member then finds it in Settings → Connectors and selects Connect to sign in with their own Innguma account.

Claude Code

claude mcp add --transport http innguma https://mcp.innguma.com/mcp

Then run /mcp in Claude Code, choose innguma and authenticate to sign in.

ChatGPT

Custom connectors use ChatGPT's developer mode, if your plan and workspace allow it:

1. Open Settings → Apps & Connectors → Advanced settings and turn on Developer mode.
2. Back in Apps & Connectors, select Create. Name it Innguma, paste the server address and choose OAuth authentication. Leave the client ID empty: it registers itself.
3. Create it and sign in to Innguma (see Signing in).
4. In each chat where you want to use it, open the + menu, then More → Developer mode, and turn on Innguma. Mentioning @Innguma in the chat does not turn it on.

In a ChatGPT Business or Enterprise workspace, an admin may have to allow custom connectors first.

Microsoft Copilot Studio

For organizations that build their own agents in Copilot Studio:

1. In the agent, open Tools → Add a tool → New tool → Model Context Protocol.
2. Enter a name and description, paste the server address and choose OAuth 2.0 authentication, type Dynamic discovery. Select Add.
3. Create the connection and sign in to Innguma (see Signing in).

Microsoft 365 Copilot (admin center)

For organizations that add MCP servers to Microsoft 365 Copilot from the Microsoft 365 admin center (Copilot → Connectors → Connect to MCP server) rather than from Copilot Studio. We have not run this form ourselves yet: the values below are Innguma's side of it; the OAuth registration is done in your Microsoft 365 tenant by your administrator. If something does not match what you see, contact us with a screenshot.

1. Fill in the connector form:

1. The Reference ID is not an Innguma value. Microsoft generates it when your administrator registers Innguma's sign-in as an OAuth client in your tenant (Teams Developer Portal → Tools → OAuth client registration), once for the whole organization, with these values:

Paste the Reference ID that Microsoft returns into the connector form.

1. Select Authorize and sign in to Innguma (see Signing in). Each user signs in with their own Innguma account the first time Copilot uses Innguma.

Your organization's name on Innguma is entered on the Innguma sign-in page, not in any Microsoft field.

Gemini Enterprise

A Google Cloud administrator of your Gemini Enterprise app adds Innguma once, as a custom MCP server:

1. In the Google Cloud console, open Gemini Enterprise, your app, then Connected data stores → Add data store → Custom MCP Server.
2. Fill in:

1. Select Login and sign in to Innguma (see Signing in), then save the data store and add it to the app or agents that will use it.

Each user then signs in with their own Innguma account the first time Gemini uses Innguma. Gemini asks before running any tool that changes data; tools that only read run without asking.

Signing in

When you connect, your assistant opens the Innguma sign-in page:

1. Enter your organization: the first part of your Innguma web address (mycompany for mycompany.innguma.com).
2. Sign in with your usual Innguma credentials, or with your company's single sign-on if your organization uses it.
3. You go back to your assistant, connected.

If it fails:

• Unknown organization or wrong credentials: check the organization name against your Innguma web address and sign in on the Innguma website to confirm your credentials.
• Your organization has not enabled the connector: the assistant tells you so when you use it. Ask your Innguma administrator.
• ChatGPT says the Innguma connector has no available actions, or is mentioned but not exposing usable tools in this conversation: you are signed in, but the connector is not turned on in that chat. Open the + menu, then More → Developer mode, and turn on Innguma (see ChatGPT). Mentioning @Innguma does not turn it on.
• The tools do not reflect a change in your permissions or a new tool: ask the assistant to sign you out of Innguma, then disconnect and connect again.
• Anything else: contact us.

More

• What the connector does and its tools
• Privacy policy
• Terms of use