Use tools exposed by an MCP server.
An agent can call the tools configured for its work. The available tools and their permissions depend on the server and the task configuration.
Connectors
Corin scaffolds a team from SOPs, onboarding knowledge and operating data. MCP and APIs reach hundreds of systems. Corin agents can also work with agents you already use.
Scaffolded from procedures and operating history
Connection paths
MCP and APIs give agents a way to reach tools and data. The interface is only the starting point: Corin uses the permitted information in the context of roles, procedures and the task at hand.
An agent can call the tools configured for its work. The available tools and their permissions depend on the server and the task configuration.
Configured endpoints can supply records or permitted actions. Exact authentication, endpoints and write scope depend on the integration.
Why the connection matters
Corin digests SOPs, onboarding material and large volumes of operating records to scaffold agents around the work. Each agent can have its own model and memory.
Through MCP and APIs, those agents can use data and tools across hundreds of systems. They can also work with agents already running in another solution, such as an SAP agent.
Built-in Langfuse retains detailed telemetry across tasks: model choices, tool calls, handoffs, tokens, latency, cost and outcomes. Temporal keeps a task open through waits that can span weeks or months.
Use the permitted records and procedures for this work item.
A connected task
Suppose a customer asks for a revised quote. A Corin agent can consult the account in Salesforce and order history in SAP, then exchange a focused check with an existing SAP agent. The pricing agent applies the SOP and prepares a recommendation for a person to review.
Read the permitted account details and terms relevant to the quote.
Build with Corin
Try Corin free and inspect a team and its traces. Discuss the MCP, API and agent handoffs your environment needs.