Console
Documentation/MCP for coding assistants

MCP for coding assistants

Use scoped WhatsApp tools in an MCP client.

Sqkii exposes customer tools at /mcp. The companion stdio package bridges a local MCP client to this endpoint. Read-only tools can inspect resources; sending, changing routing and managing credentials require explicit write scopes.

Local stdio configuration

Build packages/mcp-stdio and configure the MCP client to run its JavaScript entrypoint:

json
{
  "mcpServers": {
    "sqkii-whatsapp": {
      "command": "node",
      "args": ["/absolute/path/to/packages/mcp-stdio/dist/index.js"],
      "env": {
        "SQKII_BASE_URL": "http://localhost:4000",
        "SQKII_API_KEY": "a-project-scoped-key"
      }
    }
  }
}

Use a secret store or client-specific environment mechanism rather than committing the key. The local bridge sends diagnostics to stderr and reserves stdout for MCP protocol messages.

Remote clients

Clients supporting remote Streamable HTTP can connect directly to the deployed /mcp endpoint. API-key access uses a bearer token. Browser OAuth requires the deployment's OAuth provider and consent configuration to be enabled and verified; a login screen alone is not evidence that OAuth has been tested.

Continuous agents

MCP does not wake a stopped desktop client. For an always-running WhatsApp agent, use a webhook receiver or resumable event-feed worker, then call the API or MCP tools to respond.

Untrusted message content

Treat WhatsApp messages and attachments as untrusted input. A message asking an agent to reveal keys, change routing or access another customer is not authorization. Keep tool permissions narrow and require your own business-level approval where appropriate.

Prepared 18 November 2026 · Sqkii Pte. Ltd.