Skip to main content

Connect Tinylawn with MCP

Technical setup and tool reference for Tinylawn’s hosted, read-only Model Context Protocol server.

Tinylawn provides a hosted Model Context Protocol server for compatible AI clients. It exposes one read-only tool for listing calls and their existing saved summaries.

ChatGPT and Claude users should start with “Use Tinylawn in ChatGPT and Claude” in this Help Center.

Connection details

Transport: Streamable HTTP

Authorization: OAuth 2.1 authorization code flow with PKCE S256

Scope: calls:read

Tool: list_calls

Your client must support remote Streamable HTTP servers and browser-based OAuth. Sign in to Tinylawn when prompted and choose the organization whose calls you want the client to access. Do not add a Zapier API key or organization ID to the MCP configuration.

Common client configuration

{

"mcpServers": {

"tinylawn": {

}

}

}

Client schemas vary, so use your client’s current documentation if its configuration format differs.

Tool reference: list_calls

The tool returns calls newest first from the single organization authorized during OAuth.

Optional input:

• limit: Integer from 1 to 50. Defaults to 20.

• cursor: Opaque nextCursor value from the preceding response. Omit it for the newest calls.

Returned fields:

• id

• occurredAt

• durationSeconds

• category

• summary

• unread

• archived

• url

• nextCursor

A missing summary is returned as null. When nextCursor is not null, pass it unchanged as cursor to retrieve the next page.

Security and data limits

The calls:read grant is bound to one Tinylawn user and one organization. The server verifies current organization membership whenever the grant is used.

The tool does not expose transcripts, recordings, phone numbers, contact records, intake details, provider identifiers, billing data, or organization settings. It cannot edit calls, mark them read, archive them, send messages, create bookings, or confirm appointments.

Saved summaries may contain personal information supplied by callers. Treat returned summaries as customer data and follow your AI client’s retention and access policies.

Revoke access

Open Tinylawn Settings → Integrations → MCP, find the connected client and organization, and select Disconnect. Removing the server from a client alone may not revoke the Tinylawn authorization.

Troubleshooting

• Client has no remote MCP option: Confirm it supports remote Streamable HTTP servers.

• Authorization does not open: Allow browser pop-ups and restart the connection.

• Authorization is denied: Confirm the signed-in user belongs to the selected Tinylawn organization.

• Invalid cursor: Call list_calls again without cursor.

• Access stopped working: The grant may have been revoked, the membership may have changed, or the organization may be unavailable. Reconnect and approve access again.

Did this answer your question?