Integrations
Aila MCP

Aila Model Context Protocol (MCP)

Connect Claude, ChatGPT, Codex, Cursor, and other MCP clients to Aila. The remote server uses streamable HTTP and OAuth 2.1 (PKCE and Dynamic Client Registration).

Remote URL (POST only):

https://app.aila.fyi/api/mcp

Do not open this URL in a browser as a page. A GET request returns HTTP 405. That response is expected. The server accepts streamable HTTP POST. There is no SSE route. https://app.aila.fyi/api/mcp/sse returns HTTP 404.


Server capabilities

The remote MCP server covers calls plus loan-file / LOA workflows. After you connect, the client lists the live tools. The in-app connector card in Aila (Settings → Connections) shows the same URL and OAuth steps that Aila displays in product.

Typical remote work includes:

  • Search and read call records, transcripts, and related contact context.
  • Inspect and propose account configuration (datasets, scorecards, routing, task triggers) with explicit user approval.
  • Run loan-file / LOA workflows (documents, application fields, drafts, and LOS actions) under the same approval rules.

Do not treat a static tool table as the source of truth. Tool names and parameters come from the connected server.

OAuth discovery (for store reviewers and client implementers):

  • Protected resource: https://app.aila.fyi/.well-known/oauth-protected-resource
  • Authorization server: https://app.aila.fyi/.well-known/oauth-authorization-server

Installation and client setup

Claude Desktop

Add Aila as a custom connector. Use streamable HTTP. Then complete OAuth in the browser.

This matches the in-app connector card in Aila:

  1. Open Claude Desktop. Go to Settings > Connectors.
  2. Click Add custom connector.
  3. Set Name to Aila.
  4. Set URL to https://app.aila.fyi/api/mcp.
  5. Save the connector. Click Connect.
  6. Sign in to Aila in the browser popup and approve access.

Do not select SSE. Do not use /api/mcp/sse.


Recommended first prompt (remote)

After the remote connector is authorized:

Use the Aila MCP. First follow the in-app connector guidance and any skill/setup tools the server exposes.
Inspect current call and loan-file context, then propose configuration or workflow actions.
Wait for my explicit approval before any write, send, or LOS action.

Related documentation