Your connected MCP client can now read call logs, call summaries and individual call life logs, plus inbound and outbound RTB requests, summaries and request details.

Inspect webhook delivery history and account change history alongside the configuration behind a call. Additional reads cover Voice Agent prompts, settings, knowledge-base documents and conversations, IVRs, QAI results, call tags and profiles, and RevedUp reports.

Date-ranged reporting requests default to the last 30 days. You can request up to 366 days; longer ranges are returned in separate, non-overlapping 30-day windows, newest first.

Access remains read-only and scoped to the connected organization. Credential values are removed from returned configuration and report data.

Open Integrations → MCP → Setup, then click Copy endpoint and add that endpoint to a compatible MCP client with OAuth support.

Sign in to Moja, check the organization shown on the consent screen, and click Approve read-only access. For an existing connection, refresh your client’s available tools if the new reads do not appear.

Ask for a specific report, such as “Summarize call revenue, payout and profit by campaign for the last 30 days,” or “Show inbound RTB requests for this campaign, then inspect one request’s life log and allocations.”

For a longer date range, ask your client to follow every next_cursor until has_more is false. Cursors expire after one hour; restart the request if a cursor expires.

Open Integrations → MCP → Connections to review connections or revoke access.

Investigate call outcomes, bidding activity and webhook deliveries from one connected client, with account configuration available for context.

Review Voice Agent setup and call analysis without giving the client permission to edit settings or pause traffic.

When combining summary windows, add counts and money totals, then recompute rates from those totals. Do not add unique-caller counts across windows: the same caller may appear in more than one window.