Connect Wrenbase to Claude and other AI assistants with MCP

The Model Context Protocol (MCP) is the standard way to give an AI assistant a set of tools it can call. Wrenbase exposes its own tools over MCP. So instead of clicking through the dashboard, you say what you want: "send the invoice to Acme," "what's overdue," "mark INV-042 paid." It works with any MCP-capable client, Claude included. Nothing to install, and every action runs as you, with your account's permissions and a full audit trail behind it.

What you need to connect Wrenbase over MCP

Two things, and you get both from the same place in Wrenbase:

• •The Wrenbase MCP server URL: https://developers.wrenbase.com/mcp. It is remote, so there is nothing to install locally.
• •A Wrenbase API key, used as a bearer token. The same key works for the REST API too.

Step 1: Create a Wrenbase API key

An MCP client connects to Wrenbase with an API key. You create and manage keys in the workspace, on the Developer → API Keys page.

1. 1

   Open the Developer area

   In the workspace sidebar, go to Developer → API Keys.
2. 2

   Create a key

   Create a new key and give it a label you'll recognize later, like "Claude Desktop" or "billing agent."
3. 3

   Link it to you or an agent

   Choose who the key acts as. Link it to yourself to act on your own behalf, or to one of your AI agents so the calls run under that agent's limits. A key is always tied to exactly one of the two.
4. 4

   Set an expiration

   Pick how long the key should last, a fixed window or no expiry. You can change your mind later by revoking and reissuing.
5. 5

   Copy it once

   Wrenbase shows the full key a single time, right after you create it. Copy it then and store it somewhere safe, you won't be able to see it again. If you lose it, revoke it and create a new one.

Step 2: Connect your MCP client to Wrenbase

Most MCP clients ask for a remote server's URL and a header or token. Put the Wrenbase server URL and your key (as a bearer token) wherever your client keeps its MCP server settings:

Server URL:  https://developers.wrenbase.com/mcp
Header:      Authorization: Bearer wb_live_...

Once connected, the client discovers the Wrenbase tools automatically and you can start asking it to do things in plain language.

The exact steps vary a little by client. Here's how to connect the common ones.

Name:    Wrenbase
URL:     https://developers.wrenbase.com/mcp
Header:  Authorization: Bearer wb_live_...

{
  "mcpServers": {
    "wrenbase": {
      "url": "https://developers.wrenbase.com/mcp",
      "headers": { "Authorization": "Bearer wb_live_..." }
    }
  }
}

URL:     https://developers.wrenbase.com/mcp
Header:  Authorization: Bearer wb_live_...

Step 3: Ask in plain language

You never type tool names yourself. You say something like "send Acme's invoice" or "what's overdue," and your client works out which Wrenbase tool to call and with what.

The Wrenbase MCP tools (full reference)

Once your client is connected, it can see and call these tools. You never call them by name yourself, you ask in plain language ("send Acme's invoice," "what's overdue") and the client picks the right tool with the right fields. Here's every tool and its parameters.

Account tools

Contact tools

Invoice tools

How Wrenbase MCP stays secure

MCP gives an AI client real access to your account, so it's built to stay under your control.

Availability

MCP is included on the higher Wrenbase plans. See wrenbase.com/pricing for what's included where.