AI Agents (MCP)

Clorvia has a built-in MCP server (Model Context Protocol), so you can connect an AI agent — Claude, Cursor, Cline, or your own — and run your account in plain language: “create a GST invoice for Acme for ₹50,000”, “list unpaid invoices”, “add a new customer”.

The agent talks to the same secure API as everything else — so it only ever sees your workspace, respects your API key’s role, and stops working if your subscription or trial has lapsed.

Endpoint: https://api.clorvia.com/mcp
Transport: Streamable HTTP (JSON-RPC 2.0)
Auth: your Clorvia API key in the Authorization: Bearer <key> header

1. Create an API key

In Clorvia, go to Settings → APIs & Webhooks, create a key, and copy its token. Give the key the least-privileged role it needs (read-only is fine if the agent should only read).

2. Connect your agent

Clients that support remote MCP servers

Point the client at the URL and add your key as a header:


URL:    https://api.clorvia.com/mcp
Header: Authorization: Bearer YOUR_API_KEY_TOKEN

Clients that only support local (stdio) servers — e.g. Claude Desktop

Use the mcp-remote bridge. Add this to your client’s MCP config:


{
  "mcpServers": {
    "clorvia": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote",
        "https://api.clorvia.com/mcp",
        "--header", "Authorization: Bearer YOUR_API_KEY_TOKEN"
      ]
    }
  }
}

Restart the client and Clorvia’s tools will appear.

3. What the agent can do

Tool	What it does
`whoami`	Show the connected workspace and whether the subscription/trial is active
`list_objects`	Discover your record types (invoices, customers, items, payments…)
`describe_object`	List an object’s fields so the agent knows what to send
`list_records`	List records, with optional filters and a limit
`get_record`	Fetch one record by id
`create_record`	Create a record (customer, item, invoice…)
`update_record`	Update fields of a record
`delete_record`	Delete a record (soft by default)

With these, an agent can read and write anything in your account — for example create customers and items, raise invoices, look up dues, and update records.

Subscription required

MCP uses the same gate as the REST API. If your trial or plan has expired, tool calls return Subscription Not active until you renew.

Security

The agent authenticates with your API key — it can never reach another customer’s data, and it’s confined to your workspace.
The key respects its role: give the agent a read-only key if it should only read.
Revoke the key anytime in Settings → APIs & Webhooks to instantly cut off access.
Treat the API key like a password — don’t paste it into untrusted tools.

→ See the REST API reference for the underlying operations.