Wafeq MCP Server
by ohnebenio.github.ohneben/wafeq-mcpv2.1.0
Wafeq accounting API: all 251 endpoints as safety-categorized MCP tools, over stdio or HTTP.
context tax
queued
security
queued
cold start
queued
freshness
Active24d ago
Install Wafeq MCP server
Install in Claude Code
claude mcp add wafeq -e MCP_TRANSPORT=stdio -e WAFEQ_API_KEY='<wafeq-api-key>' -e WAFEQ_ACCESS_TOKEN='<wafeq-access-token>' -e MCP_AUTH_TOKEN='<mcp-auth-token>' -- docker run -i --rm -e MCP_TRANSPORT -e WAFEQ_API_KEY -e WAFEQ_ACCESS_TOKEN -e MCP_AUTH_TOKEN ghcr.io/ohneben/wafeq-mcp:2.1.0Install in Cursor
{
"mcpServers": {
"wafeq": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"MCP_TRANSPORT",
"-e",
"WAFEQ_API_KEY",
"-e",
"WAFEQ_ACCESS_TOKEN",
"-e",
"MCP_AUTH_TOKEN",
"ghcr.io/ohneben/wafeq-mcp:2.1.0"
],
"env": {
"MCP_TRANSPORT": "stdio",
"WAFEQ_API_KEY": "<wafeq-api-key>",
"WAFEQ_ACCESS_TOKEN": "<wafeq-access-token>",
"MCP_AUTH_TOKEN": "<mcp-auth-token>"
}
}
}
}Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (project).
Install in Claude Desktop
{
"mcpServers": {
"wafeq": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"MCP_TRANSPORT",
"-e",
"WAFEQ_API_KEY",
"-e",
"WAFEQ_ACCESS_TOKEN",
"-e",
"MCP_AUTH_TOKEN",
"ghcr.io/ohneben/wafeq-mcp:2.1.0"
],
"env": {
"MCP_TRANSPORT": "stdio",
"WAFEQ_API_KEY": "<wafeq-api-key>",
"WAFEQ_ACCESS_TOKEN": "<wafeq-access-token>",
"MCP_AUTH_TOKEN": "<mcp-auth-token>"
}
}
}
}Settings → Developer → Edit Config (claude_desktop_config.json), then restart.
Install in VS Code
{
"servers": {
"wafeq": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"MCP_TRANSPORT",
"-e",
"WAFEQ_API_KEY",
"-e",
"WAFEQ_ACCESS_TOKEN",
"-e",
"MCP_AUTH_TOKEN",
"ghcr.io/ohneben/wafeq-mcp:2.1.0"
],
"env": {
"MCP_TRANSPORT": "stdio",
"WAFEQ_API_KEY": "<wafeq-api-key>",
"WAFEQ_ACCESS_TOKEN": "<wafeq-access-token>",
"MCP_AUTH_TOKEN": "<mcp-auth-token>"
}
}
}
}Add to .vscode/mcp.json in your workspace.
Install in Windsurf
{
"mcpServers": {
"wafeq": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"MCP_TRANSPORT",
"-e",
"WAFEQ_API_KEY",
"-e",
"WAFEQ_ACCESS_TOKEN",
"-e",
"MCP_AUTH_TOKEN",
"ghcr.io/ohneben/wafeq-mcp:2.1.0"
],
"env": {
"MCP_TRANSPORT": "stdio",
"WAFEQ_API_KEY": "<wafeq-api-key>",
"WAFEQ_ACCESS_TOKEN": "<wafeq-access-token>",
"MCP_AUTH_TOKEN": "<mcp-auth-token>"
}
}
}
}Add to ~/.codeium/windsurf/mcp_config.json.
Configuration
| Variable | Required | Secret | Description |
|---|---|---|---|
| MCP_TRANSPORT | yes | — | Server transport. Set to 'stdio' for local MCP clients; the image otherwise starts the Streamable HTTP transport. |
| WAFEQ_API_KEY | — | yes | Private organization API key, sent as `Authorization: Api-Key <key>`. Wafeq -> Settings -> Developer -> API keys. Required unless WAFEQ_ACCESS_TOKEN is set. |
| WAFEQ_ACCESS_TOKEN | — | yes | OAuth2 app access token, sent as `Authorization: Bearer <token>`. 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 | — | yes | Only for MCP_TRANSPORT=http: bearer token required on /mcp. Without it a non-loopback bind refuses to start. |
Freshness
Active — last maintenance signal 24d ago. The newest of the signals below sets the band.
Last commit (default branch)
2026-09-15 · 24d ago · GitHub
Latest release
2026-09-15 · 24d ago · GitHub · v2.1.0
Package published
no data · npm/PyPI
Registry entry updated
2026-09-15 · 24d ago · official registry · v2.1.0
FAQ
›How do I install the Wafeq MCP server in Claude Code?
Run: claude mcp add wafeq -e MCP_TRANSPORT=stdio -e WAFEQ_API_KEY='<wafeq-api-key>' -e WAFEQ_ACCESS_TOKEN='<wafeq-access-token>' -e MCP_AUTH_TOKEN='<mcp-auth-token>' -- docker run -i --rm -e MCP_TRANSPORT -e WAFEQ_API_KEY -e WAFEQ_ACCESS_TOKEN -e MCP_AUTH_TOKEN ghcr.io/ohneben/wafeq-mcp:2.1.0. For Cursor, VS Code, Claude Desktop and Windsurf, use the install tabs above.
›Does Wafeq require an API key?
Yes. It expects MCP_TRANSPORT, WAFEQ_API_KEY, WAFEQ_ACCESS_TOKEN, MCP_AUTH_TOKEN, of which 3 are secrets.
›Can I use Wafeq as a remote (hosted) MCP server?
No hosted endpoint is published; it runs locally over stdio.
›Is Wafeq in the official MCP registry?
Yes, as io.github.ohneben/wafeq-mcp.
Alternatives to Wafeq
Other finance & fintech MCP servers.