Wafeq MCP Server

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

Packages and local setup

The published oci package is ghcr.io/ohneben/wafeq-mcp:2.1.0. Its declared MCP transport is stdio.

The package declares MCP_TRANSPORT (required): Server transport. Set to 'stdio' for local MCP clients; the image otherwise starts the Streamable HTTP transport.; WAFEQ_API_KEY: Private organization API key, sent as Authorization: Api-Key . Wafeq -> Settings -> Developer -> API keys. Required unless WAFEQ_ACCESS_TOKEN is set.; WAFEQ_ACCESS_TOKEN: OAuth2 app access token, sent as Authorization: Bearer . Use instead of WAFEQ_API_KEY.; WAFEQ_TOOL_GROUPS: Comma-separated resource groups to expose, e.g. invoices,bills,reports. Empty exposes all 251 generated tools.; WAFEQ_API_BASE_URL: Overrides the Wafeq API base URL. Defaults to https://api.wafeq.com/v1; MCP_AUTH_TOKEN: Only for MCP_TRANSPORT=http: bearer token required on /mcp. Without it a non-loopback bind refuses to start..

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository · Project website. This profile uses version 2.1.0 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related finance & market data MCP servers for tools that cover the same kind of work.