Skip to content

SAP HANA MCP connector

The SAP HANA connector brings SAP HANA user and group administration to Claude, ChatGPT, Cursor and the Elaichi Agent, so your team can list, create, update and remove SAP HANA users and groups with every action logged.

  • How it connects. App credentials. The credential goes into a vault nobody reads back.

  • One address. https://api.elaichi.ai/mcp, the same for every user.

  • Their own access. An agent never gets more than the person it acts for.

How to connect

How to connect SAP HANA to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect SAP HANA once

  1. Open Connections, choose Add connection, and pick SAP HANA.

  2. Optionally set Share with to give a team access, then press Connect.

  3. Paste your SAP HANA app credentials. SAP HANA authenticates the app rather than a person. One person supplies the credentials once, and everyone else works through Share with.

The credential is vaulted. Nobody reads it back, not even the AI.

Add connection

Choose a connector.

sap hana
SAP HANA
Neon
Pinecone
Sequin Stream
Snowflake
The Movie Database (TMDB)
2

In your AI client

Point it at one endpoint

Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.

SAP HANA MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

SAP HANA MCP connector for ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

SAP HANA MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 3

    Reload Cursor, then sign in and approve.

~/.cursor/mcp.json

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

Set up per machine, so repeat it on each computer you work from.

Connect SAP HANA to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 2

    Sign in and approve.

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

The Elaichi Agent already has these tools, with nothing to set up.

Use cases

What teams do with SAP HANA through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

  • IT

    Set up a new hire in SAP HANA

    Create the SAP HANA user on day one and add them to the right groups in a single ask. The account is ready before they open their laptop.

  • Security

    Review who has an SAP HANA account

    Ask for every user in SAP HANA and spot accounts that belong to people who have moved teams or left. Follow up on each one without leaving the conversation.

  • HR

    Remove access on someone's last day

    When a leaver is confirmed, have their SAP HANA user removed and their group memberships cleared. The audit log records who did it and when.

  • Compliance

    Pull a group membership list for an audit

    Get the members of any SAP HANA group when an auditor asks, formatted and ready to hand over. No ticket to IT and no waiting a week.

  • Data and analytics

    Add analysts to the reporting group

    When a new analyst joins, add their SAP HANA user to the reporting group so they can start on the data they need. Update the group again when the project ends.

  • Operations

    Fix a user record that is out of date

    Correct a name, email or attribute on a SAP HANA user when it changes. Only the field you mention is touched, and the rest stays as it was.

Try asking

  • “List every SAP HANA user added in the last 30 days”
  • “Which SAP HANA groups is Priya Nair a member of?”
  • “Create a SAP HANA group called Finance Reporting”

See all 12 SAP HANA tools below

Compare

Elaichi vs Zapier MCP vs Composio for SAP HANA

All three can connect SAP HANA to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

Elaichi compared with Zapier MCP and Composio for SAP HANA, by what to check
What to check Elaichi Zapier MCP Composio
Where the AI connects One address for the whole organization. https://api.elaichi.ai/mcp A server per member, created at sign-in. An MCP endpoint per team, or an SDK.
Control over SAP HANA tools Allow or restrict single SAP HANA tools, per role or user. App and action restrictions on the account. Role permissions, down to the action.
Record of calls One audit entry per SAP HANA call. A History tab of tool calls. A log of every tool call.
Single sign-on SAML or OIDC, plus SCIM, on Gold. SAML on Enterprise. SAML and OIDC on Enterprise.
Price $15 per user per month. 2 tasks per successful call. Billed per tool call.

Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.

Longer take: Zapier MCP alternative and when you don't need an MCP gateway.

AI tools

SAP HANA tools for your AI agents

12 tools are ready to call through Elaichi's MCP endpoint the moment you connect SAP HANA, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

See it in Elaichi

What connecting SAP HANA gets you

6 screens from the product, each doing one job for your SAP HANA account.

The agent

Ask about SAP HANA users in plain language.

Type a question and get the answer from live SAP HANA users and groups.

  • users
  • groups
  • accounts
  • memberships

Ask Elaichi to work across your apps.

List every SAP HANA user added in the last 30 days

Which SAP HANA groups is Priya Nair a member of?

Create a SAP HANA group called Finance Reporting

Also runs in Claude, ChatGPT or Cursor

MCP clients

One endpoint puts SAP HANA in every client.

Claude, ChatGPT and Cursor reach SAP HANA through one org endpoint, no SDK, no shared key.

ElaichiMCP clients
Claude ChatGPT Cursor

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

Tool catalog

12 SAP HANA tools, ready without writing code.

List, create, update and delete SAP HANA users and groups, with no custom code.

  • List all SAP HANA users
  • Get single SAP HANA user by ID
  • Create a SAP HANA user
  • Update a SAP HANA user by ID
ElaichiTools
Tool Action Description
List all SAP HANA users List List users in SAP Cloud Identity Services (Identity Authentication) via the SCIM 2.0 API (GET /service/scim/Users). Returns SCIM user resources with userName, name, emails, active, userType, groups, enterprise and SAP extension attributes and meta timestamps. Supports SCIM filter expressions (e.g. userName eq "x" or meta.lastModified gt "date"), attribute selection, sorting and startIndex/count paging. No parameters are required.
Get single SAP HANA user by ID Get Get a single user from SAP Cloud Identity Services by id via SCIM 2.0 (GET /service/scim/Users/{id}). Returns the full SCIM user resource including name, emails, phone numbers, active flag, userType, group memberships, enterprise attributes (employeeNumber, department, manager) and SAP specific attributes. Required: id (the user UUID).
Create a SAP HANA user Create Create a user in SAP Cloud Identity Services via the Identity Directory SCIM 2.0 API (POST /service/scim/Users). Requires schemas, userName and at least one email; optional name, active, userType, enterprise and SAP extension attributes. Set the SAP extension sendMail to true to send the activation email. Returns the created SCIM user with its generated id.
Update a SAP HANA user by ID Update Replace a user in SAP Cloud Identity Services (PUT /service/scim/Users/{id}, SCIM 2.0). Sends the full user representation; attributes not included are cleared, so read the user first and resend it with your changes. Required: id and a complete user body with schemas and userName. Returns the updated user.
SAP HANA users partial update Update Update selected attributes of a user in SAP Cloud Identity Services without resending the whole record (PATCH /service/scim/Users/{id}, SCIM PatchOp). Use operations such as replace active=false to deactivate, replace name.givenName, or add emails. Required: id (query) and Operations.

Toolboxes

Every team gets its own SAP HANA toolbox.

IT, security and compliance each work from a toolbox scoped to their own job.

  • IT
  • Security
  • Compliance
  • HR
ElaichiToolboxes
Name Source template Tools Created

IT toolbox

SAP HANA · users and groups

SAP HANA starter 18 Mar 4, 2026

Security toolbox

SAP HANA · access reviews

— 9 Mar 2, 2026

Compliance toolbox

SAP HANA · group memberships

— 24 Feb 27, 2026

HR toolbox

SAP HANA · joiners and leavers

SAP HANA starter 6 Feb 19, 2026

Data and analytics toolbox

SAP HANA · reporting groups

— 31 Jan 30, 2026

Finance toolbox

SAP HANA · close team access

— 12 Jan 22, 2026

Shared connections

Share SAP HANA access, never the credential.

One admin connects SAP HANA and teammates work through it without seeing a password.

  • Production
  • Development
  • Finance
  • EMEA
ElaichiConnections
Connection Scope Status Access
SA

SAP HANA (Production)

Connected by Emily Carter

Personal • Active 1 team · 6 members
SA

SAP HANA (Development)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
SA

SAP HANA (Finance)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
SA

SAP HANA (EMEA)

Connected by Tyler Reed

Personal • Needs re-auth 1 team · 3 members
SA

SAP HANA (APAC)

Connected by Ryan Hayes

Personal • Active Not shared
SA

SAP HANA (Analytics)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Audit log

Every SAP HANA change is on the record.

See when, who, what happened and which SAP HANA user or group was touched.

  • When
  • Who
  • What happened
  • Type
ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

[email protected]

SAP HANA Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

[email protected]

SAP HANA Users Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

[email protected]

SAP HANA Users List Toolbox

Launching soon

From answering questions to doing the work

A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.

Automations

A schedule starts SAP HANA access reviews itself.

Users are fetched, grouped, drafted into a digest, approved by a person, then posted back.

SAP HANA digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch users

    SAP HANA

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Michael Brennan

    Approve
  6. Post the digest

    SAP HANA

    Queued

Collections and dashboards

SAP HANA account health, computed on a schedule.

Four metrics, 14 days of users created and a team breakdown, no model involved.

SAP HANA health

Refreshed 4 minutes ago · every 15 minutes · from the users collection

Live

Users

1,284 ↓ 12%

Groups

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Users created

Last 14 days

By team

Share of activity

Production 34%

Development 27%

Finance 21%

EMEA 18%

FAQ

Frequently asked questions

How do I connect SAP HANA to Claude?

Two steps. In Elaichi, choose SAP HANA and enter the app credentials your SAP HANA administrator gives you, then in Claude go to Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. There is no OAuth application to register and no client ID or secret to generate, and the whole thing takes a few minutes.

Does SAP HANA work with ChatGPT and Cursor as well as Claude?

Yes. Once SAP HANA is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect SAP HANA once and every client picks it up.

What can an AI agent actually do with my SAP HANA data?

Through this connector an agent can list the users and groups in SAP HANA, look one up, create new ones, update details and remove them. That covers the everyday administration work: setting up a new hire, adding someone to a group, correcting a record, or removing a leaver. Short concrete asks, like "add Priya to the reporting group in SAP HANA", work better than long paragraphs.

Does connecting SAP HANA give the AI full administrator rights?

No. Every call to SAP HANA runs inside the access of the person who signed in, so an agent can only see and change what that person's SAP HANA credentials already allow. Elaichi can narrow that access further with roles and restrictions, and it can never widen it.

Can my team share one SAP HANA connection?

Yes. One administrator connects SAP HANA in Elaichi and shares it with a team, and nobody else ever handles the app credentials. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person behind every SAP HANA change.

Can I stop an agent from deleting or changing users in SAP HANA?

Yes. Restrictions in Elaichi work per action, so you can allow listing and looking up SAP HANA users and groups while blocking create, update or delete. A restricted action is never advertised to Claude, ChatGPT or any other client, so no prompt can reach it.

What happens to a SAP HANA connection when someone leaves?

Offboarding that person in Elaichi ends their access to SAP HANA through every client at once. A shared SAP HANA connection keeps working for everyone else on the team. If you ever want to remove SAP HANA entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client.

Does the SAP HANA MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. SAP HANA is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

Is Elaichi an alternative to Zapier MCP for SAP HANA?

Yes. Both let Claude, ChatGPT or Cursor use SAP HANA. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every SAP HANA call.

How is Elaichi different from Composio for SAP HANA?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to SAP HANA: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

Put SAP HANA in front of your team

14 days on Gold, no credit card. Connect it once and pick what each team can call.

Works with
Claude ChatGPT Cursor and any other MCP client, or the Elaichi Agent.
When the trial ends
Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.