Requiply 1.2.3: MCP for Reporting

Q: Do I need a new type of token for the MCP server?

No. The MCP server authenticates with the same secret API tokens (rq_sk_live_…) introduced in 1.2.2. Create one under Settings → Organization Settings → API Keys and use it as the bearer token for the MCP connection. A dedicated key per integration is recommended so you can rotate one without affecting the others.

Q: Can the MCP server create or change bookings?

No, by design. The Reporting MCP is read-only — it answers questions and helps you plan, but it cannot create, change, or cancel anything in your Requiply account. Write capabilities are available directly through the public API for integrations that need them.

Q: How do I revoke an agent if something goes wrong?

Open Settings → Organization Settings → API Keys and revoke the token the agent is using. The MCP connection stops working immediately — no support ticket needed.

Requiply 1.2.3 ships the official Reporting MCP server: a read-only Model Context Protocol surface that lets Claude, ChatGPT, and other AI assistants answer natural-language questions about your revenue, bookings, utilization, and clients.

What's New in Requiply 1.2.3?

A short release with one headline change: Requiply now has an official Reporting MCP server. Connect Claude, ChatGPT, or any MCP-compatible client to your account and get plain-language answers about your rental business — revenue, bookings, utilization, top clients — straight from live data, with no SQL, exports, or dashboard-building required.

Official Reporting MCP Server

The Model Context Protocol is the open standard for connecting AI assistants to live business data. With 1.2.3 we ship a turnkey, read-only MCP server — point your agent at a URL, authenticate with a secret token, and it can answer questions about your rental business in seconds.

What it gives your AI agent

Live read access to revenue, bookings, utilization, top clients, overdue balances, pipeline, availability, and pricing — no stale exports

Read-only by design — agents can answer and help you plan, but cannot create, change, or cancel anything in your account

Authentication tied to a secret API token you control — revoke a key and the agent stops, instantly

Works with any MCP-compatible client: Claude Desktop, Cursor, ChatGPT, and custom assistants

How to connect

Open Settings → Integrations → AI and pick the Requiply MCP card. You'll need a secret API token to authenticate — generate one in Settings → Organization Settings → API Keys if you don't have one yet. Paste the generated MCP URL into Claude, Cursor, or any MCP client, and the agent is live against your data. For a full walkthrough, see the Reporting MCP tutorial.

FAQ

Do I need a new type of token for the MCP server?

Can the MCP server create or change bookings?

How do I revoke an agent if something goes wrong?

What's Next?

1.2.3 closes the loop opened in 1.2.2: public API, managed tokens, and AI agents that can act through them. Up next:

Official SDKs — typed TypeScript clients for the public API, so anyone who wants a rental business website can spin one up in Lovable, v0, Cursor, or any custom stack and get a working booking experience in hours, not weeks.

Have questions or building something on the MCP server? Write to us at info@requiply.com — we'd love to feature the integrations our customers ship first.