> ## Documentation Index
> Fetch the complete documentation index at: https://manual.risegroup.eu/llms.txt
> Use this file to discover all available pages before exploring further.

# MCP Server: Connect Rise to Your AI Assistant

> The MCP server gives the AI assistant you already use a direct line to the figures in your Rise account. How it works, what it sees and what it is allowed to do.

The MCP server connects the AI assistant you already use to your Rise account. You ask a question in your own words, and the assistant fetches the answer straight from your books — as the figures stand at that moment, from the right company.

Nothing is handed to the assistant in advance. The figures are within its reach when you ask, and only as far as answering your question requires.

## What it's used for

<CardGroup cols={2}>
  <Card title="Budgets and comparisons" icon="chart-column">
    Build a budget from historical data and compare actuals against it. Rise produces the statutory reports; budgeting happens this way.
  </Card>

  <Card title="Longer forecasts" icon="chart-line">
    Rise's own cash forecast covers two weeks from open invoices. Longer cash flow forecasts are built with the assistant.
  </Card>

  <Card title="Board and management reports" icon="file-chart-column">
    A report in the shape your company actually uses, rather than a standard template.
  </Card>

  <Card title="Open questions" icon="comments-question">
    "What did we spend on software last quarter?" — answered without anyone building a report.
  </Card>
</CardGroup>

Financial data can also be combined with other data the assistant can reach — your CRM, for instance, putting the sales pipeline and the cash position in one view.

## What MCP is not

<AccordionGroup>
  <Accordion title="It is not the Rise chat">
    The chat inside the Rise app is your line to your accountant team, with Rise's AI accountant answering in the same conversation. That is a different thing in a different place. MCP is about the AI assistant you use anyway.

    → [Talking to Your Accountant](/account/communication)
  </Accordion>

  <Accordion title="It is not a new place your data is stored">
    Rise doesn't move your books anywhere. The assistant asks a question, Rise answers it, and the answer appears in the conversation. No copy lives outside Rise except in the conversation you opened yourself.
  </Accordion>

  <Accordion title="It is not a way around permissions">
    The assistant acts with your permissions. It sees nothing you wouldn't see by logging into Rise yourself.
  </Accordion>
</AccordionGroup>

## What it sees and what it may do

**The permissions are the ones you already have.** MCP neither adds nor removes any: if you see two companies in Rise, the assistant sees the same two. If you can't reach payroll data, neither can it.

**Writing is possible too** — the assistant can create and change things in Rise, not only read them. That also runs on your permissions: it can do only what you would be allowed to do yourself.

<Warning>
  **Payments cannot be released by an AI assistant.** A payment leaves only when it is approved in the app, with your phone's biometric authentication. The boundary is deliberate: the assistant can prepare, a person releases the money.

  → [Purchase Invoices](/features/purchase-invoices)
</Warning>

<Note>
  **The assistant may list capabilities you cannot use.** MCP tells the assistant about the whole set of functions regardless of what you have rights to. Ask for something outside your permissions and the request will not go through — though the assistant may offer it first. This is neither a fault nor a security hole: the restriction holds even though the menu shows the full list.
</Note>

## Setting it up

MCP is an open standard, so it works with any AI assistant that supports it. You are not tied to one tool.

<Steps>
  <Step title="Check that your assistant supports MCP">
    Support is usually found in settings under **Connectors**, **MCP** or **Integrations**. Some services require a paid tier or a developer setting to be switched on.
  </Step>

  <Step title="Ask Rise for the connection address">
    Ask your accountant team in the in-app chat. You'll get the server address and instructions for your particular assistant.
  </Step>

  <Step title="Add the server and sign in">
    Add the address to your assistant and authenticate with your Rise credentials. Signing in is the moment your permissions are decided — the assistant gets exactly the visibility you have.
  </Step>

  <Step title="Ask your first question">
    Start with something you already know the answer to and check that the figure matches. It's the quickest way to confirm the connection points at the right company.
  </Step>
</Steps>

## If you want the detail

<AccordionGroup>
  <Accordion title="What MCP actually is">
    Model Context Protocol is an open standard for how an AI assistant talks to an external system. It is not a Rise invention and not Rise property: the same protocol connects assistants to calendars, ticketing systems and databases.

    For Rise it means one server serves every assistant, instead of building a separate connector for each.
  </Accordion>

  <Accordion title="How this differs from an API">
    An API is called by a program along a workflow somebody built in advance: when a deal closes in the CRM, create an invoice. The route is decided before anything happens.

    With MCP there is no route. The assistant is handed a list of things it can do and picks from it based on your question. That's why it answers questions nobody thought to anticipate.

    → [Integrations](/features/integrations)
  </Accordion>

  <Accordion title="What exactly the assistant may call">
    The functions are typed and scoped per company: every call targets one company, and that company comes from your authentication, not from the assistant's choice. The assistant cannot widen its own visibility by asking more broadly.
  </Accordion>

  <Accordion title="Can this be used in our own software">
    Yes. The same server works from your own code and from the command line, not only in a chat interface. If you're building something on top of Rise data, ask your accountant team and we'll point you to the right person.
  </Accordion>
</AccordionGroup>

## Related pages

<CardGroup cols={2}>
  <Card title="Integrations" icon="arrow-left-arrow-right" href="/features/integrations">
    The API, the automation platforms, and where responsibility sits.
  </Card>

  <Card title="AI Bookkeeping" icon="bolt" href="/features/ai-bookkeeping">
    What the AI does to your books in the background without being asked.
  </Card>

  <Card title="Dimensions" icon="chart-diagram" href="/features/dimensions">
    The axes your figures are split along in reports.
  </Card>

  <Card title="Compliance" icon="briefcase-blank" href="/account/compliance">
    Data security, permissions and archiving.
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.