Lika Rika

se.likarikaPublished by likarika.seOfficial publisherv0.1.3Updated Oct 24, 2026

Manage shared household finances for two people - expenses, budgets, savings, and settlements.

VerifiedStreamable HTTPWeb executableFinance

Overview

AI-generated overview

Remote MCP server for managing shared household finances for two people: expenses, budgets, savings and settlements.

What you can do
  • Manage shared household finances for two people, covering expenses, budgets, savings and settlements.
  • No tool list is published, so the exact actions an assistant can take are not documented; expect working with the household's expense, budget, savings and settlement records.
When to use it
Useful for a couple or two-person household that keeps its shared spending, budgets, savings goals and settlement balances in Lika Rika and wants an assistant to work with that data.
Requirements
A remote endpoint at mcp.likarika.se over streamable HTTP; no local package needed. Requires a bearer token in the Authorization header, obtained as an API key from the Lika Rika settings (API Keys) page. Network access to the service.
Before you install
The Authorization header carries a secret API key; keep it private and revocable. The server manages financial records, so an assistant may read or change shared household expense, budget, savings and settlement data. Tool-level permissions are not documented, so review what it can do before connecting.

Installation

In SourceWeft

  1. Open Lika Rika in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/se.likarika%2Fbudget/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "lika-rika": {
      "type": "http",
      "url": "https://mcp.likarika.se/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v0.1.3LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.