FIS Code Connect MCP Server & Agent Skill

What is the FIS Code Connect API, and what can an agent read from it?

Catalog of FIS APIs in categories including Banking and Wealth, Payments, Cards, Networks, Intelligence (risk and fraud), Institutional and Wholesale, and Corporate. Each API's reference lives in the Code Connect catalog.

• API: FIS Code Connect APIs (REST)
• Access: Partner or license program
• Base URL: https://api-gw-uat.fisglobal.com (UAT host; production and B2B hosts are listed in the Developer Toolkit)
• Authentication: OAuth 2.0 bearer token from consumer key and secret; mTLS client certificate (api-gw2 endpoints)

Register on Code Connect for Mock Sandbox keys (stubbed responses). Readiness/Test keys with live data need approval from your FIS account manager; production is for FIS clients and approved partners.

Generate an access token from the app's consumer key and secret and send Authorization: Bearer. Each request also needs a uuid header. mTLS endpoints require a client certificate from a trusted CA.

What can an agent read from FIS Code Connect?

• Banking and wealth data — Banking and Wealth category APIs; available resources depend on which FIS core the institution runs. See the catalog reference.
• Loans — Digital banking APIs for personal loans, mortgages and HELOC.
• Payments — Payments category: bill pay, P2P and cross-border.
• Cards — Card creation, management and cardless cash APIs.
• Risk and fraud insights — Intelligence category: consumer insights and real-time risk and fraud.

What can an agent write to FIS Code Connect?

• Payments — Bill pay, P2P and cross-border payment APIs move money. Confirm with the user first.
• Cards — Card creation and management APIs issue or change live cards. Confirm with the user first.
• Loan applications — Digital banking loan APIs; confirm write operations per API in the catalog.

Limits: Clients must cache access tokens for at least 20 minutes and should not set token expiry beyond 24 hours; do not request a token per call. No rate limits published on the public toolkit pages.

Core banking APIs carry GLBA nonpublic personal information (accounts, balances, loans). Card APIs handle PCI cardholder data.

How do I connect FIS Code Connect to an AI agent over MCP?

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

The practical path is to host a small MCP server that wraps the FIS Code Connect 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 FIS Code Connect agent skill do?

The FIS Code Connect skill is one SKILL.md file named iblai-connect-fis. 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 FIS Code Connect SKILL.md

Save it as .claude/skills/iblai-connect-fis/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 FIS' documentation on October 20, 2026. Test it against your own FIS Code Connect setup before you rely on it.

What can I ask an FIS Code Connect agent to do?

• “Pull the current balance and last 10 transactions for this member's checking account”
• “Check the status of yesterday's cross-border payment batch”
• “Block the debit card reported lost by this customer”
• “Summarize the real-time fraud alerts raised on this account this week”

How do I run an FIS Code Connect agent on ibl.ai?

Agentic OS is where the agent runs on ibl.ai: it holds the FIS Code Connect 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 FIS Code Connect data?

• Operations Specialist — Financial Services
• Fraud Investigator — Financial Services

Which ibl.ai platform skills does an FIS Code Connect 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 FIS Code Connect to an AI agent?

Which other data sources can an AI agent connect to alongside FIS Code Connect?

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
• 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
• Temenos Transact — Core banking system

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