riseup-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RISEUP_HEADLESS | No | false also shows the sign-in browser's window | true |
| RISEUP_LOGIN_URL | No | The link handed out, when the page sits behind a reverse proxy. When set, the page starts with the server. | http://localhost:<port>/ |
| RISEUP_CONFIG_DIR | No | Where the session and the sign-in browser's profile are saved | ~/.config/riseup-mcp |
| RISEUP_LOGIN_HOST | No | Address the sign-in page listens on | 127.0.0.1 |
| RISEUP_LOGIN_PORT | No | Its port; a free one is used if another copy holds it | 8768 |
| RISEUP_CHROMIUM_PATH | No | Another Chromium to sign in with | Playwright's Chromium |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| riseup_loginA | Get the link where the user signs in to RiseUp (phone number, codes and two-step sign-in are done on that page, never in the chat). Returns the status when already signed in. |
| riseup_session_statusA | Whether this server is signed in to RiseUp, since when, until when, and the sign-in link when it is not. |
| riseup_logoutA | Sign out of RiseUp here: end the session and forget it. |
| get_budgetB | One cashflow month as RiseUp's app reads it: its envelopes (fixed, variable, tracking categories, income) with planned amounts and their transactions, and the transactions excluded from the cashflow. |
| list_transactionsB | One cashflow month's transactions, each with the category it is in (variable, fixed, excluded, income, or a tracking category), its merchant, date and amount. |
| list_categoriesA | The categories a transaction can be moved to with move_transaction: variable, excluded, and the user's tracking categories (with their ids), as of the given month. |
| move_transactionA | Move a transaction to variable expenses, out of the cashflow (excluded), or into a tracking category; with applyTo=merchant, RiseUp applies it to the merchant's transactions too. Changes the user's RiseUp account. Returns where the transaction is afterwards. |
| set_transaction_commentC | Set the note on a transaction in RiseUp. Changes the user's RiseUp account. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Most tools have clearly distinct purposes (session vs. read vs. modify). The main overlap is between get_budget and list_transactions, since both return a month's transactions with categories, though descriptions differentiate their framing (envelopes/planned amounts vs. flat transaction list).
The data tools use a clean verb_noun pattern (get_budget, list_transactions, move_transaction), but the three session tools are prefixed riseup_ (riseup_login, riseup_session_status, riseup_logout), creating two conventions. Readable, but not uniform.
Eight tools is well within the ideal range and each earns its place: session lifecycle, budget/transaction reads, category lookup, and two account-mutating actions. No redundancy that inflates the count.
Covers the session lifecycle plus the core read (budget, transactions, categories) and write (move, comment) operations on transactions. Gaps remain, e.g. creating transactions or editing planned/budget amounts, but core workflows are functional.