Temenos Transact MCP Server & Agent Skill

What is the Temenos Transact API, and what can an agent read from it?

REST/JSON APIs grouped into Holdings, Order, Party, Product, Reference, Enterprise, Meta, Settings and System domains, with paths such as api/v1.0.0/holdings/... A Postman collection is published.

• API: Temenos Core Banking (Transact) APIs (REST)
• Access: Issued by your administrator
• Authentication: API key (sandbox)

Free sandbox after registering with the Temenos Basecamp community; customers and partners use Temenos credentials. Production APIs run on the bank's own Transact deployment (SaaS, cloud or on-premise).

Sandbox calls use a key from the portal's My API Key page, valid 30 days and regenerable at any time. Production authentication is set by the bank's deployment and is not described on public pages.

What can an agent read from Temenos Transact?

• Customers — Party domain: customers, beneficiaries, contact details and KYC data.
• Accounts and arrangements — Holdings domain: accounts, deposits, loans and other arrangements.
• Orders — Order domain: payments, transfers, standing instructions and other order instructions.
• Products and pricing — Product domain: product catalog, pricing and interest conditions.
• Reference data — Reference domain: currencies, countries, bank codes and transaction codes.

What can an agent write to Temenos Transact?

• Create customer — Party APIs create a customer record (shown in the sandbox guide).
• Open account or loan — Holdings APIs create current, deposit and loan accounts. Confirm with the user first.
• Payment orders — Order APIs submit payments and fund transfers. Confirm with the user first.

Customer, KYC and account data are GLBA nonpublic personal information for U.S. banks (personal data under local law elsewhere). Card APIs, where used, carry PCI cardholder data.

How do I connect Temenos Transact to an AI agent over MCP?

As of October 2026 we found no MCP server published by Temenos itself.

The practical path is to host a small MCP server that wraps the Temenos Core Banking (Transact) APIs, or to give the agent the calls directly with the SKILL.md below.

On ibl.ai an MCP connection is three records, and a working integration always needs all three:

1. Register the server — POST …/mcp-servers/ with its URL, a transport (sse, websocket or streamable_http) and an auth_type of none, token or oauth2.
2. Create a connection that holds the credential, scoped to the whole organization (platform), to a single agent, or to each user (user).
3. Enable it on the agent — mcp-tool in tool_slugs and the server id in mcp_servers. Both lists are replaced, not merged, so read the settings first.

For an API key or a service credential, one token connection at platform scope serves the whole organization; scope a connection to a single agent when that agent needs narrower access than the rest.

The field reference is in MCP server connections, and the /iblai-api-agent-mcp skill runs all three steps from a coding agent.

What does the Temenos Transact agent skill do?

The Temenos Transact skill is one SKILL.md file named iblai-connect-temenos. It gives an agent the auth conventions, what to read, which writes need a person's confirmation, the ibl.ai MCP wiring, example prompts and guardrails.

Download the Temenos Transact SKILL.md

Save it as .claude/skills/iblai-connect-temenos/SKILL.md, or in your agent's skills folder. The ibl.ai platform skills it calls come from one install:

This connector skill is a starting point maintained on ibl.ai, not part of the iblai/vibe repository.

It was checked against Temenos' documentation on October 20, 2026. Test it against your own Temenos Transact setup before you rely on it.

What can I ask a Temenos Transact agent to do?

• “Fetch the customer record and KYC status for customer 100345”
• “List all loan arrangements for this customer with outstanding balances”
• “Show the interest conditions on our standard savings product”
• “Create a current account for this new customer in the sandbox”

How do I run a Temenos Transact agent on ibl.ai?

Agentic OS is where the agent runs on ibl.ai: it holds the Temenos Transact MCP connection, the model the agent uses, its instructions and its conversation history.

On ibl.ai you own all the code and the data, run it model-agnostic across any LLM, and pay with no per-seat pricing — so you can deploy anywhere, from your own cloud to a fully air-gapped network.

• AI agents for Financial Services — what ibl.ai deploys in this sector

Which ibl.ai agents work with Temenos Transact data?

• Operations Specialist — Financial Services
• Regulatory Reporter — Financial Services

Which ibl.ai platform skills does a Temenos Transact agent use?

• /iblai-api-agent-mcp — MCP connectors for ibl.ai agents, end to end
• /iblai-vibe-agent-mcp — Add the agent MCP tab (Model Context Protocol connector management with featured connectors, custom connectors, OAuth,…
• /iblai-api-agent-tool — Enable or disable an ibl.ai agent's tools via the platform API

What else should I know before connecting Temenos Transact to an AI agent?

Which other data sources can an AI agent connect to alongside Temenos Transact?

Which other Financial Services systems have a connector?

• Bloomberg Terminal & B-PIPE — Market data and analytics
• Docusign eSignature — Electronic signature platform
• FactSet — Financial data and analytics
• FIS Code Connect — Core banking and payments API marketplace
• Fiserv Banking Hub — Core banking API platform
• Jack Henry — Core and digital banking platform
• nCino — Bank lending and account opening platform
• Plaid — Financial data and account-linking API
• Salesforce Financial Services Cloud — Financial services CRM

Every connector, grouped by sector, is on the connectors hub.