Connect data & tools
Give agents tools through MCP servers, connect ticketing and chat systems, and keep every credential in the secrets store.
Agents are only as useful as what they can reach. Liyagent connects in three ways: MCP servers give managed agents tools, connections and connectors bring in tickets and let agents act in systems such as Jira, ServiceNow, Salesforce, Teams and email, and the secrets store holds every credential those need, referenced by label rather than pasted into settings.
The catalogue of ready-made servers and connectors is a starting set, not the limit. Any MCP server you can reach can be added by URL, and OpenAPI operations or your organisation's own code can be brought in as tools beside it, so an agent can be built for any system. Whether Liyagent is hosted by us or by you, it reaches those systems through their own APIs from your environment.
For SAP, see Connect SAP: Liya calls SAP S/4HANA's own APIs, with a person confirming each agent call, or connects to the MCP Gateway in your SAP Integration Suite. For Salesforce, see Connect Salesforce. For Microsoft Dynamics 365 (Sales, Customer Service, Field Service, Finance, Supply Chain Management, Business Central and the rest), see Connect Dynamics 365.
In this section
- MCP servers
Register MCP servers, pin and pause their tools, and put data policies on what flows through them.
- Connections
Per-user OAuth connections that let agents act as the signed-in person, and the connector sources that pull tickets in.
- Secrets store
Store each credential once, reference it everywhere as secret://ID, and optionally keep it in AWS Secrets Manager or HashiCorp Vault.
- Microsoft Teams app
Register an Azure bot, create a Teams trigger, build the app package from the console and upload it to Teams.
- Google Chat app
Create a Chat app in your Google Cloud project, point its HTTP endpoint at Liyagent, and paste the project number, service account key and domains into a Google Chat trigger.
- One Liya app for every agent
Add one Liya app to Microsoft Teams or Google Chat for the whole organisation. Each person sees the agents they may use, picks one, and talks to it with buttons, steps and approvals in the chat.
- Jira
Pull issues from Jira Cloud or Data Center into TicketIQ for triage, and give agents Jira tools through the managed Jira MCP server.
- ServiceNow
Pull incidents from a ServiceNow table into TicketIQ for triage, correlation and knowledge.
- Connect Salesforce
Give agents Salesforce tools as the signed-in person, through the managed Salesforce connector on Salesforce's REST APIs or through Salesforce's own hosted MCP servers.
- Connect Microsoft Dynamics 365
Reach every Dynamics 365 product, either through Liyagent's managed connectors on Microsoft's own APIs or through Microsoft's hosted MCP servers, as the signed-in person.
- Email and SMTP
Receive mail as tickets or as agent conversations, reply in thread, and relay outbound notices through your SMTP server.
- ERP, SQL and file sources
Pull records from a REST API, a SQL database, SQLite or a CSV export, and give each citation a link back to the record in your own system.
- Connect SAP
Connect Liya to SAP S/4HANA's and SAP SuccessFactors' own APIs, with a person confirming each agent call, or through the MCP Gateway in your SAP Integration Suite.
- Connect SAP Field Service Management
Connect Liya to SAP Field Service Management to read service calls and, if you switch it on, plan and release activities, with a person confirming each agent call.
- Act as each person in SAP Field Service Management
Choose whose FSM rights Liya's calls run under, either the connection's OAuth client or each person's own FSM user and permission group, and what your FSM administrator sets up for each.
- How Liya confirms SAP calls
Which SAP calls show a Confirm card in Teams, which run straight away, and why each stays inside SAP's API Policy.
Product names and logos are trademarks of their respective owners, shown only to identify the systems Liyagent connects to. No endorsement is implied.