03 · BUSINESS TOOLS
AI SaaS MCP integration
Finance ERP exposes its authorized business capabilities through standard MCP JSON-RPC. The recommended public path uses the signed-in ERP user token, allowing the server to restore the tenant, user, store, role, and permission boundary instead of trusting client-supplied identity headers.
Connection
- Endpoint
- https://fin.eelml.com/api/mcp
- Protocol
- MCP 2025-03-26 over HTTP JSON-RPC
- Authentication
- Authorization: Bearer <ERP_USER_TOKEN>
- Supported methods
- initialize, ping, tools/list, tools/call
1 · Sign in to the AI SaaS workspace
Obtain the user JWT through the Finance ERP sign-in flow. The account must belong to an active tenant.
2 · Initialize MCP
POST a JSON-RPC initialize request and then send notifications/initialized.
3 · Discover capabilities
Call tools/list. Tool schemas, titles, descriptions, and annotations are the authoritative capability contract.
4 · Call one authorized tool
Use tools/call with the selected tool name and schema-valid arguments. Read both content and structuredContent in the result.
Surface
- POST
- /api/mcp
- JSON-RPC
- initialize
- JSON-RPC
- tools/list
- JSON-RPC
- tools/call
List available SaaS tools
curl https://fin.eelml.com/api/mcp \ -H "Authorization: Bearer $ERP_USER_TOKEN" \ -H "Content-Type: application/json" \ -d '{ "jsonrpc": "2.0", "id": 1, "method": "tools/list", "params": {} }'
Security and product boundaries
- Do not send X-Agent-Tenant-Id, X-Agent-User-Id, role, permission, or store identity headers. The authenticated server session supplies those values.
- The service-token /mcp and /api/v1/mcp paths are managed machine interfaces, not public self-service credentials.
- MCP transport does not bypass business approvals, tenant isolation, store scope, or capability-level authorization.