Naru
About Naru
Naru is a gateway that offers a company's legacy systems to AI agents as MCP tools. Naru handles authentication, network, approval, masking and audit; each system's business logic is written as a pack.


What it does
It targets groupware and JSP business screens, REST and SOAP behind EAI or API gateways, databases such as Oracle, Tibero and SQL Server, and apps behind Active Directory sign-in. Legacy systems differ in how you connect (protocol, authentication, encoding) more than in their business logic, so Naru splits the work into three layers.
| Layer | Does | Who |
|---|---|---|
| Auth plugin | Sign-in, tokens, signing, session renewal | Naru (13 built in) or approved code plugins |
| Driver | http, soap, sql, jdbc |
Naru; JDBC and Kerberos via a Java sidecar |
| Function | A business tool (groupware_approval_list) |
Pack authors, vibe-coded in Galpi |
Functions never see secrets and can't reach the network or files. They use only systems.<name>.http/soap/sql, with authentication already attached by Naru. A new kind of legacy system needs one driver or plugin added once; from then on it's only functions.
MCP client ── OAuth 2.1 / token ──▶ /mcp/<toolset> ─┬─ policy · approval · masking · audit
(Galpi, Mothership, Claude…) ├─ pack runner (isolated functions)
└─ system call ─ auth chain ─ driver ─▶ legacy
Whose credentials
| Mode | Signs in as | Who is shown | Example |
|---|---|---|---|
service |
A shared integration account | Nobody | Code lookups, stock |
onbehalf |
A shared integration account | The caller's employee number in a header, SOAP header or DB session | The most common pattern in Korean companies |
personal |
Each person's own account | That person | Groupware approvals, mail |
When someone calls a personal system before linking their account, the tool returns auth_required with a link (/connect/<system>). They enter their account on Naru's page and Naru signs in on the spot to check it. Credentials never pass through the LLM.
Alone, and together
- Alone: use toolsets from any MCP client (Claude, Cursor, opencode …) and develop packs with the
naruCLI. - With Galpi: develop and submit packs from a Galpi project, and use toolsets in Galpi chats.
- With Mothership: Mothership apps call Naru as a company connector, with a signed statement of who is calling.
The repository
| Path | What |
|---|---|
apps/server |
The Naru server: MCP, OAuth authorization server, admin API and screens, development MCP, plugins, drivers, pack runner |
packages/sdk |
@naru/sdk: defineFunction, plugin types, the fixture harness, the naru CLI |
packages/cli |
naru-admin: systems, toolsets, deployments, plugins, tokens, audit |
sidecars/enterprise |
Java 21 sidecar: JDBC (HikariCP), Kerberos |
templates/pack |
The pack template for Galpi |
examples/ |
Example packs (groupware, ERP, HR database), a fake legacy, a code plugin |
Next
legacy systems · in-house systems · ERP · groupware · HR system · connect AI to internal systems · MCP server