Wafeq

io.github.ohneben/wafeq-mcp

Wafeq accounting API: all 251 endpoints as safety-categorized MCP tools, over stdio or HTTP.

Connect this server

Add this to your MCP client config — claude_desktop_config.json (Claude Desktop) or .cursor/mcp.json (Cursor).Suits: Claude Desktop · Cursor.

{
  "mcpServers": {
    "wafeq-mcp": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/ohneben/wafeq-mcp:2.1.0"
      ],
      "env": {
        "MCP_TRANSPORT": "<your MCP_TRANSPORT>",
        "WAFEQ_API_KEY": "<your WAFEQ_API_KEY>",
        "WAFEQ_ACCESS_TOKEN": "<your WAFEQ_ACCESS_TOKEN>",
        "WAFEQ_API_BASE_URL": "https://api.wafeq.com/v1",
        "MCP_AUTH_TOKEN": "<your MCP_AUTH_TOKEN>"
      }
    }
  }
}
Environment variables
  • MCP_TRANSPORTrequiredServer transport. Set to 'stdio' for local MCP clients; the image otherwise starts the Streamable HTTP transport.
  • WAFEQ_API_KEYsecretPrivate organization API key, sent as `Authorization: Api-Key <key>`. Wafeq -> Settings -> Developer -> API keys. Required unless WAFEQ_ACCESS_TOKEN is set.
  • WAFEQ_ACCESS_TOKENsecretOAuth2 app access token, sent as `Authorization: Bearer <token>`. Use instead of WAFEQ_API_KEY.
  • WAFEQ_API_BASE_URLOverrides the Wafeq API base URL. Defaults to https://api.wafeq.com/v1
  • MCP_AUTH_TOKENsecretOnly for MCP_TRANSPORT=http: bearer token required on /mcp. Without it a non-loopback bind refuses to start.

A starting point — check the repository for exact arguments and setup. Restart your client after editing the config.

Category
Developer Tools
Version
2.1.0
Registry
active
Published
9/15/2026
Browse all Developer Tools →

Add the badge to your site

Show visitors that Wafeq is listed here — it’s also the link we check for a free listing.

Wafeq — listed on Serverdex

HTML — for your website

<a href="https://serverdex.io/server/io-github-ohneben-wafeq-mcp?utm_source=badge"><img src="https://serverdex.io/brand/badge.svg" alt="Wafeq — listed on Serverdex" width="123" height="40" loading="lazy"></a>

Recommended. A dofollow link from your own domain is the one that counts for search engines, and it's the link we check for a free listing.

Markdown — for your README

[![Wafeq — listed on Serverdex](https://serverdex.io/brand/badge.svg)](https://serverdex.io/server/io-github-ohneben-wafeq-mcp?utm_source=badge)

Nice for visibility, but GitHub marks README links nofollow, so it doesn't pass authority. Use the HTML badge on your site as well.