Back to Browse

Monexa MCP Server

Developer ToolsLow Risk10.0MCP RegistryRemote
Free

Server data from the Official MCP Registry

Track expenses and income, recurring payments and spending trends in Monexa from any AI assistant.

About

Track expenses and income, recurring payments and spending trends in Monexa from any AI assistant.

Remote endpoints: streamable-http: https://mcp.monexa.world/mcp

Security Report

10.0
Low Risk10.0Low Risk

Valid MCP server (4 strong, 1 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry. Trust signals: 4 highly-trusted packages.

Endpoint verified · Requires authentication · 1 issue found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Found in Source Code

Found by scanning the linked source code. This listing connects to a hosted endpoint, so none of this runs on your machine: it describes what the server software does where it is hosted.

env_vars

Applies to the server that hosts this plugin, not to your machine.

HTTP Network Access

Connects to external APIs or services over the internet.

file_system

Applies to the server that hosts this plugin, not to your machine.

How to Connect

Remote Plugin

No local installation needed. Your AI client connects to the remote endpoint directly.

Add this to your MCP configuration to connect:

{
  "mcpServers": {
    "io-github-emilijan-koteski-monexa": {
      "url": "https://mcp.monexa.world/mcp"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

Monexa

Personal finance and expense tracking app with multi-currency support. Go backend + React frontend.

What you need

mise install picks up both tool versions from mise.toml.

Development setup

The database runs in Docker; backend and frontend run on your machine for hot reload.

1. Environment variables

cp .env.example .env
cp frontend/.env.example frontend/.env

The example values work as-is locally. .env files are git-ignored; never commit real secrets.

2. Start the database

docker compose up -d

PostgreSQL listens on localhost:5433 (postgres / postgres, database monexa). If you used the previous compose file, run docker compose down --remove-orphans once to retire the old psql_monexa container.

3. Run the backend

go run ./cmd/api

The API listens on http://localhost:9000 (PORT in .env). Migrations run on startup.

4. Run the frontend

cd frontend
npm ci
npm run dev

Open http://localhost:5173.

Everything in Docker

Builds the same images that production uses and runs them next to Postgres (needs .env from step 1):

docker compose --profile app up --build

UI on http://localhost:3000, API on http://localhost:9000.

Tests

go test ./...
cd frontend && npm run lint

Deployment

See docs/DEPLOYMENT.md.

Reviews

No reviews yet

Be the first to review this server!