How to connect your AI assistant to QSAP

Before you start (admins)

A handful of things need to be true before anyone on the team can connect. Most of this is a one-time setup — see Deployment and Security for the detail.

Access has been granted in SAP for the roles that will use QSAP.
Sign-in is connected: QSAP is wired up to your company's identity provider, so people use their normal work account.
QSAP is deployed somewhere in your landscape (see Deployment) and reachable at your company's QSAP address.
Roles are mapped: each sign-in group is linked to the right SAP tools and plants.
Share the QSAP address with users — for example, https://qsap.yourcompany.com/mcp — along with this page.

Step-by-step, by assistant

Pick the AI assistant your team uses. Exact menu names can change as vendors update their apps — if a step looks different on your screen, look for the nearest equivalent (for example, "Connectors" or "Tools" settings).

Claude (claude.ai and Claude Desktop)

Open Settings, then find Connectors (on individual Pro/Max plans this is under "Customize"; on Team/Enterprise plans it's under "Organization settings").
Choose to add a connector that isn't already listed — usually labelled Add custom connector (Team/Enterprise: add a custom "Web" connector).
Give it a name (e.g. "QSAP") and paste your company's QSAP address, such as https://qsap.yourcompany.com/mcp.
Leave the advanced OAuth fields blank unless your admin has told you otherwise, then save.
When prompted, sign in — you'll be redirected to your company sign-in page, then back to Claude.
Start a new chat and ask: "What can you do with SAP?" If QSAP's tools are listed, you're connected.

On Team and Enterprise plans, an admin may need to add the connector for the organisation before it shows up for everyone else.

Source: Anthropic support docs, "Get started with custom connectors using remote MCP", checked Oct 2026.

Claude Code

Open a terminal in your project.

Run:

claude mcp add --transport http qsap https://qsap.yourcompany.com/mcp

Inside Claude Code, run /mcp to see connected servers and start authentication.
Follow the browser prompt — you'll be redirected to your company sign-in page, then back to the terminal.
Run claude mcp list to confirm QSAP shows as connected.
Ask: "What can you do with SAP?" to check the tools are available.

Use --scope user to make QSAP available in every project, or leave the default to add it just for the current project.

Source: Claude Code docs, "Connect to MCP servers", checked Oct 2026.

ChatGPT

Go to Settings → Apps & Connectors → Advanced settings and turn on Developer mode (on Plus and Pro plans this is available directly; on Business/Enterprise/Edu, an admin may need to allow it first).
If your workspace is Business or Enterprise and the option isn't there, ask your QSAP admin to enable custom MCP connectors in Workspace settings → Permissions & roles → Connected data.
Back in Apps & Connectors, add a custom connector and paste your company's QSAP address, such as https://qsap.yourcompany.com/mcp.
Complete sign-in — you'll be redirected to your company sign-in page, then back to ChatGPT.
Turn the QSAP connector on for your chat.
Ask: "What can you do with SAP?" to check it worked.

Custom MCP connectors require Developer mode, which sits behind a Plus/Pro plan or an Enterprise/Business admin setting. If you don't see Developer mode at all, ask your admin whether it's enabled for your workspace.

Source: OpenAI help centre, "Developer mode and MCP apps in ChatGPT", checked Oct 2026.

Gemini

Gemini CLI

Open (or create) your Gemini CLI settings file: ~/.gemini/settings.json for all projects, or .gemini/settings.json in one project.

Add an mcpServers entry with your company's QSAP address as the httpUrl:

{
  "mcpServers": {
    "qsap": {
      "httpUrl": "https://qsap.yourcompany.com/mcp"
    }
  }
}

Save the file and restart Gemini CLI.
When prompted, sign in — you'll be redirected to your company sign-in page, then back to the CLI.
Ask: "What can you do with SAP?" to check the tools loaded.

If your company uses Gemini Enterprise, a QSAP connection can also be added centrally under Settings & help → Manage team → Connected apps → Add MCP server — ask your admin whether this route is set up for you instead.

Sources: Gemini CLI docs, "MCP servers with the Gemini CLI"; Google support, "Set up your custom MCP server connection" (Gemini Enterprise), checked Oct 2026.

Microsoft Copilot Studio

Open your agent in Copilot Studio and go to Tools.
Select Add a tool → New tool → Model Context Protocol.
Enter a name, a short description, and your company's QSAP address as the server endpoint, e.g. https://qsap.yourcompany.com/mcp.
Choose OAuth 2.0 as the authentication method (ask your admin if a different option is listed for your tenant).
Select Add. Copilot Studio will connect and list the tools QSAP exposes.
In a test chat, ask: "What can you do with SAP?" to confirm the tools are available.

Adding tools in Copilot Studio is typically a maker/admin task, not something every end user does for themselves — check with whoever administers your Copilot Studio agents.

Source: Microsoft Learn, "Connect your agent to an existing Model Context Protocol (MCP) server", checked Oct 2026.

Other MCP-compatible assistants

QSAP speaks the Model Context Protocol (MCP) over standard HTTP, so most MCP-compatible assistants can connect the same general way. Exact menu names vary by product, so we keep this one generic rather than guessing at labels we haven't verified.

Find your assistant's settings for adding a remote MCP server or connector (often under "Tools," "Connectors," "Integrations" or similar).
Add a new server using your company's QSAP address, e.g. https://qsap.yourcompany.com/mcp, over HTTP transport.
Complete sign-in — you'll be redirected to your company sign-in page, then back to the assistant.
Ask: "What can you do with SAP?" to confirm the connection worked.

If your assistant doesn't support remote MCP connectors at all, that's usually a plan limitation or an admin setting rather than something QSAP can change — see the troubleshooting section below.

Try these first

Generic examples for a manufacturing business — swap in your own plant codes, materials and order numbers.

"What's the stock of [material] in plant [plant code]?"
"Which open production orders in [plant code] are short of components?"
"Show me the bill of materials for [material]."
"List this week's sales orders for [customer]."
"What can you do with SAP?" — a good first question on any assistant, to see the tools you have access to.

Troubleshooting

I don't see any SAP data

QSAP only shows what your role allows. If a tool or plant you expect is missing, ask your admin to check that your sign-in group is mapped to the right SAP tools and plants.

Sign-in keeps looping back to the sign-in page

This is usually a configuration issue on QSAP's identity connection rather than something you can fix yourself. Contact your QSAP admin with the time it happened and which assistant you were using.

My assistant doesn't show an option to add a connector

Custom connectors sometimes sit behind a plan tier (for example, a paid individual plan) or an admin setting (for example, a workspace toggle for custom MCP connectors). Check the plan requirements noted under your assistant's tab above, or ask your admin whether the setting is enabled for your account.

My first question is slow

The very first request after QSAP starts, or after a period of inactivity, warms up its cache against SAP. Later questions in the same session are typically much faster.

What this means for your data

Your credentials stay with your company's sign-in — QSAP never sees or stores your password.
QSAP never stores the content of your AI chats; it only sees the specific SAP request your assistant makes.
Every request is written to QSAP's tamper-evident audit trail, so what was asked and answered is always traceable.
Your AI provider's own data-handling terms apply to anything your assistant does with the answer — check those terms for your organisation's requirements.

Connect your AI assistant to SAP in a few minutes.