Wafeq accounting API: all 251 endpoints as safety-categorized MCP tools, over stdio or HTTP.
Connect Runs on your machine
claude mcp add wafeq-mcp -e MCP_TRANSPORT=<MCP_TRANSPORT> -e WAFEQ_API_KEY=<WAFEQ_API_KEY> -e WAFEQ_ACCESS_TOKEN=<WAFEQ_ACCESS_TOKEN> -e WAFEQ_TOOL_GROUPS=<WAFEQ_TOOL_GROUPS> -e WAFEQ_API_BASE_URL=<WAFEQ_API_BASE_URL> -e MCP_AUTH_TOKEN=<MCP_AUTH_TOKEN> -- docker run -i --rm ghcr.io/ohneben/wafeq-mcp:2.1.0
{
"mcpServers": {
"wafeq-mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/ohneben/wafeq-mcp:2.1.0"
],
"env": {
"MCP_TRANSPORT": "<MCP_TRANSPORT>",
"WAFEQ_API_KEY": "<WAFEQ_API_KEY>",
"WAFEQ_ACCESS_TOKEN": "<WAFEQ_ACCESS_TOKEN>",
"WAFEQ_TOOL_GROUPS": "<WAFEQ_TOOL_GROUPS>",
"WAFEQ_API_BASE_URL": "<WAFEQ_API_BASE_URL>",
"MCP_AUTH_TOKEN": "<MCP_AUTH_TOKEN>"
}
}
}
}
{
"mcpServers": {
"wafeq-mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/ohneben/wafeq-mcp:2.1.0"
],
"env": {
"MCP_TRANSPORT": "<MCP_TRANSPORT>",
"WAFEQ_API_KEY": "<WAFEQ_API_KEY>",
"WAFEQ_ACCESS_TOKEN": "<WAFEQ_ACCESS_TOKEN>",
"WAFEQ_TOOL_GROUPS": "<WAFEQ_TOOL_GROUPS>",
"WAFEQ_API_BASE_URL": "<WAFEQ_API_BASE_URL>",
"MCP_AUTH_TOKEN": "<MCP_AUTH_TOKEN>"
}
}
}
}
{
"servers": {
"wafeq-mcp": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/ohneben/wafeq-mcp:2.1.0"
],
"env": {
"MCP_TRANSPORT": "<MCP_TRANSPORT>",
"WAFEQ_API_KEY": "<WAFEQ_API_KEY>",
"WAFEQ_ACCESS_TOKEN": "<WAFEQ_ACCESS_TOKEN>",
"WAFEQ_TOOL_GROUPS": "<WAFEQ_TOOL_GROUPS>",
"WAFEQ_API_BASE_URL": "<WAFEQ_API_BASE_URL>",
"MCP_AUTH_TOKEN": "<MCP_AUTH_TOKEN>"
}
}
}
}
Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
This server runs locally, so its tools are listed by your MCP client once it starts.
Environment variables
| Name | Description |
|---|---|
MCP_TRANSPORTRequired | Server transport. Set to 'stdio' for local MCP clients; the image otherwise starts the Streamable HTTP transport. |
WAFEQ_API_KEYOptional, secret | Private organization API key, sent as `Authorization: Api-Key <key>`. Wafeq -> Settings -> Developer -> API keys. Required unless WAFEQ_ACCESS_TOKEN is set. |
WAFEQ_ACCESS_TOKENOptional, secret | OAuth2 app access token, sent as `Authorization: Bearer <token>`. Use instead of WAFEQ_API_KEY. |
WAFEQ_TOOL_GROUPSOptional | Comma-separated resource groups to expose, e.g. invoices,bills,reports. Empty exposes all 251 generated tools. |
WAFEQ_API_BASE_URLOptional | Overrides the Wafeq API base URL. Defaults to https://api.wafeq.com/v1 |
MCP_AUTH_TOKENOptional, secret | Only for MCP_TRANSPORT=http: bearer token required on /mcp. Without it a non-loopback bind refuses to start. |
Details
| Package | ghcr.io/ohneben/wafeq-mcp:2.1.0 (OCI, stdio) |
| First published | 15 Sep 2026 |
| Last updated | 15 Sep 2026 |
| Registry name | io.github.ohneben/wafeq-mcp |
More finance and crypto servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
