> For the complete documentation index, see [llms.txt](https://docs.rillet.com/EjmEP4KZ9BVp9j2ho4Mh/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rillet.com/EjmEP4KZ9BVp9j2ho4Mh/settings-and-config/api-and-developer-access/mcp-integration-with-rillet.md).

# MCP Integration with Rillet

The **Rillet** **Model Context Protocol (MCP)** server enables AI assistants like **Claude Desktop**, **Claude Code**, and AI-powered code editors like **Cursor** to interact directly with your **Rillet** account and documentation. This lets you query financial data, search documentation, and generate integration code without leaving your AI assistant.

### Understand the Rillet MCP Server

Model Context Protocol (**MCP**) is an open standard that allows AI applications to securely access external data sources and tools. Review the capabilities the **Rillet MCP server** provides to AI agents:

| Capability           | Description                                      |
| -------------------- | ------------------------------------------------ |
| Direct API access    | Access to Rillet functionality.                  |
| Documentation search | Search capabilities across Rillet documentation. |
| Real-time data       | Live data from your Rillet account.              |
| Code generation      | Assistance building Rillet integrations.         |

Together, these capabilities let your AI assistant work with live Rillet data and documentation without leaving your development environment.

### Rillet MCP Server Setup

With a valid **Rillet** account, you can connect to the remote **MCP** server **Rillet** hosts at `https://api.rillet.com/mcp`, authenticated through OAuth2. Select your AI development tool below and follow its connection steps.

{% tabs %}
{% tab title="Claude Desktop / Web" %}
Connect through the **Connectors** directory built into **Claude Desktop** and **Claude Web**, which adds **Rillet** as a connector available in any chat once you authorize your organization through OAuth2.

1. Click your profile icon in the bottom-left corner and select **Settings**.

   <figure><img src="https://612265232-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNpXFVFZpTQck3vIrjmHB%2Fuploads%2FwZBDbcED8PFtIQlrvxok%2Fimage.png?alt=media&amp;token=16e0182b-3a86-4797-8586-9d59ddc1004e" alt=""><figcaption></figcaption></figure>
2. Go to the **Connectors** tab and click **Browse**.

   <figure><img src="https://612265232-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNpXFVFZpTQck3vIrjmHB%2Fuploads%2FBl88nptB0N8H0uZIixwK%2Fimage.png?alt=media&amp;token=a24f44d7-a329-4898-98fc-82f597d34009" alt=""><figcaption></figcaption></figure>
3. Search for **Rillet** in the **Directory** and click the **+** button.

   <figure><img src="https://612265232-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNpXFVFZpTQck3vIrjmHB%2Fuploads%2FJq7cx4OrjF4lCQCAQxst%2Fimage.png?alt=media&amp;token=899bd0f2-efe8-403d-ad9c-13b2c534ea72" alt=""><figcaption></figcaption></figure>
4. Select your organization (if you have multiple) once redirected to **Rillet** in your browser, and click **Allow access**.

   <figure><img src="https://612265232-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNpXFVFZpTQck3vIrjmHB%2Fuploads%2FuI0BClzy5fijRMTzzUUI%2Fimage.png?alt=media&amp;token=28a50b9e-cab3-4e13-8442-08f03f725fff" alt=""><figcaption></figcaption></figure>

Once connected, **Rillet** appears in your connectors list. Start a new chat and ask something like `What customers do I have in Rillet?` to confirm the connection is working.
{% endtab %}

{% tab title="Claude Code" %}
Run the following commands in your terminal to add and authenticate the server. The first command registers the **Rillet MCP server** as a named connection called `rillet-mcp` over HTTP. The second command opens **Claude Code** and its `/mcp` menu, where you select `rillet-mcp` and choose **Authenticate**, which redirects you to your browser to authorize your organization through OAuth2.&#x20;

```bash
# Add server
$ claude mcp add --transport http rillet-mcp https://api.rillet.com/mcp

$ claude
❯ /mcp

Local MCPs
❯ rillet-mcp · △ needs authentication
# select ' rillet-mcp' and 'Authenticate'
# you'll be redirected to a page where you can authorize your organization

rillet-mcp: https://api.rillet.com/mcp (HTTP) - ✓ connected
```

Once authorized, the terminal shows the connection as `connected`.
{% endtab %}

{% tab title="Cursor" %}
Add the following to `~/.cursor/mcp.json`. This registers a server named `rillet-mcp` that runs through the `mcp-remote` package, which proxies the connection between **Cursor** and the remote **Rillet MCP server** at the URL provided, and handles the OAuth2 authentication the first time you connect.

```json
{
  "mcpServers": {
    "rillet-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://api.rillet.com/mcp"
      ]
    }
  }
}
```

{% endtab %}

{% tab title="Other" %}
Use the following settings to connect any **MCP**-compatible client not listed above. **Transport** specifies that the connection runs over HTTP rather than a local process, and **Auth** specifies OAuth2 as the default authentication method.

| Setting   | Value                        |
| --------- | ---------------------------- |
| Transport | HTTP                         |
| URL       | `https://api.rillet.com/mcp` |
| Auth      | OAuth2                       |

If your client does not support OAuth2, pass an API key as a Bearer token in the `Authorization` header instead. Generate a key from [**API Access**](/EjmEP4KZ9BVp9j2ho4Mh/settings-and-config/api-and-developer-access/api-access.md) if you do not already have one.

```
Authorization: Bearer <your-api-key>
```

{% endtab %}
{% endtabs %}

### Frequently Asked Questions (FAQ)

<details>

<summary>How do I test my connection?</summary>

Open your AI assistant, start a new chat, and ask something about your **Rillet** data, such as "What customers do I have in Rillet?" or "Do I have any overdue invoices?" The AI assistant should now have access to your **Rillet** account data and documentation through the **MCP** server.

</details>

<details>

<summary>Which tools are available to my AI agent?</summary>

The **Rillet MCP server** offers tools that implement the same features exposed by the [**Rillet Public API**](https://docs.api.rillet.com/reference/). Refer to it for an accurate list of all tools available to your agent. Your agent only has access to the tools that your **Rillet** user has access to.

</details>

<details>

<summary>What should I do if I have connection issues?</summary>

Contact the **Rillet** Support Team at <mcp-support@rillet.com>.

</details>

### See Also

To learn more about system configuration and access management in **Rillet**, review these articles:

* [**API Access**](/EjmEP4KZ9BVp9j2ho4Mh/settings-and-config/api-and-developer-access/api-access.md)
* [**Single Sign-On (SSO) and Authentication Options**](/EjmEP4KZ9BVp9j2ho4Mh/settings-and-config/single-sign-on-sso-and-authentication-options.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.rillet.com/EjmEP4KZ9BVp9j2ho4Mh/settings-and-config/api-and-developer-access/mcp-integration-with-rillet.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.