Integrations

AIMA Labs agents can reach outside the platform through three kinds of integrations:

• Google Calendar — so agents can read availability and book meetings.
• MCP servers — so agents can call your own tools mid-conversation.
• Leadsforce — so you can pipe sourced leads straight into campaigns.

Most integrations live under Integrations in the sidebar. Leadsforce lives under Settings → Organization → Leadsforce because it's account-scoped.

Google Calendar

Used whenever an agent needs to book a meeting.

Connecting:

1. Open Integrations and find the Google Calendar card.
2. Click Connect and sign in with the Google account whose calendar should receive events.
3. Grant the calendar scopes when prompted.

Once connected, any agent that schedules meetings will use this calendar automatically. You can reconnect a different account at any time — the old credential is replaced.

What the agent does with it:

• Reads free/busy windows to quote real availability on the call.
• Creates events for booked meetings with the lead as an attendee.
• Respects the agent's configured availability rules (working hours, time zone, how far out it can schedule).

MCP servers (agent tools)

Model Context Protocol (MCP) tool servers let your agent call your systems during a live conversation — look up an order, check inventory, create a ticket, price a quote, whatever you need.

This is separate from the Aima MCP server at /api/mcp, which lets you operate AIMA from Claude or Cursor. Agent tool servers are what your sales agent calls mid-call.

Registering a server:

1. Open Integrations.
2. Under Your custom servers, click Add MCP Server.
3. Fill in the server's name, URL, and any auth headers the server requires.
4. Save. The server becomes available to bind to campaigns.

Connecting system integrations:

The Available integrations section lists pre-built connectors. Click Connect on a card, enter any required credentials or headers, and the integration is ready to toggle on in campaigns.

Binding a server to a campaign:

Each campaign has an MCP bindings tab (or Integrations step in the create flow). Toggle on the servers this campaign's agent may call. If a server needs per-organization credentials, connect it under Integrations first — blocked bindings show a Set up in Integrations link.

See Campaigns.

Tools exposed by a bound server automatically show up in the agent's toolbox during conversations. You can add prompt instructions about when to use them, but you do not need to name each tool explicitly.

Leadsforce

Leadsforce is a lead-sourcing integration managed under Settings → Organization → Leadsforce. Connect your Leadsforce account once per organization, and you can then pull sourced contacts into any campaign's lead list.

API keys and webhooks

For programmatic access, open Settings → Organization → Developers.

API keys authenticate the Aima CLI and Aima MCP. Keys are organization-scoped (api_… prefix). The Developers page includes copy-paste setup for Claude, Claude Code, Cursor, and Codex.

Webhooks fire on lead and call events. Configure outbound URLs and signing secrets on the same page.