lurq

MCP server

Home

Qeemah Accounting & ZATCA e-Invoicing

Saudi ZATCA e-invoicing Phase 2 compliance audit, invoice drafting, and CFO VAT analytics.

Endpoint
Answering, needs sign-in
Works in
5 of 21 clients
Tools
behind sign-in
Last checked
Oct 7, 2026

Does Qeemah Accounting & ZATCA e-Invoicing work in your MCP client?

Registry name io.github.mosmn/qeemah, endpoint https://api.qeemahcloud.com/api/v1/mcp.

  • Claude Codeworks
  • Claude Desktopworks
  • Claude.aiworks
  • Claude API MCP connectorneeds setupClaude API MCP connector cannot run the OAuth sign-in; supply an access token as a header instead, if the server accepts one
  • ChatGPTworks
  • OpenAI Responses APIneeds setupOpenAI Responses API cannot run the OAuth sign-in; supply an access token as a header instead, if the server accepts one
  • Codexblockedthe server is reachable only over legacy HTTP+SSE, and Codex supports neither
  • Gemini CLIunknownthe server offers Client ID Metadata Documents; no source confirms whether Gemini CLI supports it
  • Cursorunknownthe server offers Client ID Metadata Documents; no source confirms whether Cursor supports it
  • VS Code (GitHub Copilot)works
  • Windsurf (Devin Desktop)unknownthe server offers Client ID Metadata Documents; no source confirms whether Windsurf (Devin Desktop) supports it
  • Zedblockedthe server is reachable only over legacy HTTP+SSE, and Zed supports neither
  • JetBrains AI Assistantneeds setupJetBrains AI Assistant cannot run the OAuth sign-in; supply an access token as a header instead, if the server accepts one
  • Junieunknownno source confirms Junie supports legacy HTTP+SSE
  • Clineneeds setupthe server offers Client ID Metadata Documents, which Cline cannot use: register an OAuth client with https://api.qeemahcloud.com/api/auth and enter its client id in Cline. Allow redirect URI(s): http://127.0.0.1:1456/mcp/oauth/callback, http://127.0.0.1:1457/mcp/oauth/callback, http://127.0.0.1:1458/mcp/oauth/callback, http://127.0.0.1:1459/mcp/oauth/callback, http://127.0.0.1:1460/mcp/oauth/callback, http://127.0.0.1:1461/mcp/oauth/callback.
  • Continueunknownthe server offers Client ID Metadata Documents, which Continue cannot use, and no source confirms it accepts a pre-registered client
  • Gooseblockedthe server is reachable only over legacy HTTP+SSE, and Goose supports neither
  • Lovableunknownno source confirms Lovable supports legacy HTTP+SSE
  • Replit Agentunknownno source confirms Replit Agent supports legacy HTTP+SSE
  • Bolt.newunknownthe server offers Client ID Metadata Documents; no source confirms whether Bolt.new supports it
  • v0unknownno source confirms v0 supports legacy HTTP+SSE

How clients sign in

OAuth sign-in. Client ID Metadata Documents: yes. Dynamic Client Registration: no. PKCE S256: yes.

Get the setup for your client from your agent

This page is a daily snapshot. lurq's connect_check answers for the client you are wiring this server into, with the exact steps and the config to paste in that client's own format, and lurq mcp-pin tells you when the server changes. One command connects Claude Code, Cursor, VS Code and other agents:

npx lurqrun

Free to start. How connect_check works

From lurq's credential-free probe of this server's endpoint on Oct 7, 2026, and each client's own documentation. This page refreshes every 168 hours. How the probe works, and how maintainers opt out. Source repository.