Works with the AI Agents you already use
Claude Code
Cursor
Codex CLI
Muse
Dots+22 moreClaude CodeCursorCodex CLIMuseDots
OpenClaw
Manus
Grok
Grok Bot+18 agentsb1-mcp-server: SAP Business One context for AI agents
Connect AI agents to SAP Business One HANA/SQL databases and Service Layer with built-in read-only guardrails.
Free
b1-mcp-server: SAP Business One context for AI agents
Example session with this skill installed
Create an inventory count for item ITEM-1001 in warehouse 01, counting the same quantity that is on hand, then close it.
- Read your context and instructions
- Compiled the b1-mcp-server
Summary
I created the inventory count through the Service Layer and closed it, with your approval for each write. The counted quantity matches the quantity on hand, so the count has no variance.
What happened
| Step | Call | Result |
|---|---|---|
| 1. Check the connection | connect_database | ServiceLayer write approval: client (the MCP client's permission prompt; no approval form) |
| 2. Read the stock | SELECT OITW."ItemCode", OITW."WhsCode", OITW."OnHand" FROM OITW WHERE OITW."ItemCode" = 'ITEM-1001' AND OITW."WhsCode" = '01' | On hand: 120 |
| 3. Create the count | POST InventoryCountings | You approved the prompt. Created DocEntry 6, DocNum 4 |
| 4. Close the count | POST InventoryCountings(6)/Close | You approved the prompt |
| 5. Confirm | GET InventoryCountings(6)?$select=DocumentStatus | cdsClosed |
The body sent in step 3
{
"BranchID": 1,
"CountDate": "2026-09-28",
"Remarks": "Inventory count created by the agent",
"InventoryCountingLines": [
{
"ItemCode": "ITEM-1001",
"WarehouseCode": "01",
"CountedQuantity": 120,
"Counted": "tYES"
}
]
}
Each write named its target database and showed the exact endpoint and body before you approved it. Nothing was written through SQL: the database side stays read-only.
Next steps
- Open the count in SAP Business One (Inventory › Inventory Transactions › Inventory Counting) to review it.
- To record a real difference, send the counted quantity instead of the on-hand value; posting the difference is a separate document (
InventoryPostings). - For many items, send one count with several lines instead of one write per item.
Connects securely to your tools. The creator never sees your data.
About this skill
Querying SAP Business One directly through AI agents often hits a wall due to database engine differences and strict read-only requirements. This skill teaches your agent to use b1-mcp-server (github.com/bersimao/b1-mcp-server), an open-source MCP server that bridges AI agents and SAP B1 on HANA or MS SQL, plus the Service Layer, behind production-safe guardrails.
What it does
- Database Connection guides the agent through your connection profiles for HANA and MS SQL, including the Service Layer OData API, and stops it after failed logins instead of locking the account.
- Read-Only SQL keeps the agent on SELECT queries and read-only blocks, and has it hand any data change back to you instead of trying to work around the server.
- Schema Discovery points the agent to the server's metadata tool for tables, columns, and procedures, instead of hand-written catalog queries.
- Service Layer Access covers OData GET, plus POST, PATCH, and DELETE when your profile allows them, with the server's approval workflow for each write.
- Guardrail Handling explains every refusal, engine-specific timeout, query length limit, and truncated result, so the agent fixes the query instead of retrying blindly.
How it works
- Use
connect_databasewith "list" to view available B1 profiles and their connection capabilities. - Select a profile ID to establish a connection to the database, Service Layer, or both.
- Run
execute_sqlfor data retrieval orexecute_service_layer_writefor approved record updates. - Watch tool output for
TRUNCATEDnotes or engine-specific timeouts, and refine the query.
Frameworks & tools
Built for the Model Context Protocol (MCP) and b1-mcp-server. Compatible with SAP Business One Service Layer (OData v3/v4), SAP HANA, and Microsoft SQL Server.
Why this beats prompting it yourself
Generic prompts don't know that a HANA timeout shows up as Socket recv timeout while MS SQL reports a plain request timeout, or which refusals can be fixed and which must go to a human. This skill gives the agent exact error meanings, readable SAP B1 SQL conventions (full table names instead of T0/T1 aliases), and the write rules that keep ERP data safe.
Use cases
- Fetching real-time stock levels or Business Partner balances for analysis.
- Auditing user-defined tables (UDT) and system tables like OINV or OCRD.
- Updating documents via the Service Layer, with your approval for each write.
- Debugging SAP B1 stored procedure logic by rewriting it as a SELECT.
What you get
One SKILL.md file. Copy it into your agent's skills folder, for example ~/.claude/skills/b1-mcp-server/ for Claude Code. Requires b1-mcp-server (npx b1-mcp-server). Open source (MIT); the same skill lives in the GitHub repository.
Known limitations
No PUT, no $batch, and no SQL writes. Queries are capped at 8000 characters, and results at 500 rows and 100,000 characters by default. Service Layer writes are off unless your profile enables them.
How to use
Skills on Agensi run inside your AI agent. Copy the prompt, paste it into your agent, and it connects to Agensi and installs this skill for you. If a payment is needed, your agent shows it to you first.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill passes our trust checks below.
Security scanned
Passed our 8-point scan before listing
Fresh listing
Recently published to Agensi
Free forever
No account required to browse
Trust & safety
Security scanned
Verified clean 1 day ago
- Free to download with an account
Requires