IntakeQ MCP Server

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add intakeq-mcp -- npx -y @oktopeak/intakeq-mcp

{
  "mcpServers": {
    "intakeq-mcp": {
      "args": [
        "-y",
        "@oktopeak/intakeq-mcp"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.intakeq-mcp]
command = "npx"
args = ["-y", "@oktopeak/intakeq-mcp"]

{
  "mcpServers": {
    "intakeq-mcp": {
      "args": [
        "-y",
        "@oktopeak/intakeq-mcp"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "intakeq-mcp": {
      "args": [
        "-y",
        "@oktopeak/intakeq-mcp"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: INTAKEQ_API_KEY (IntakeQ API key (optional — prefer the set_api_key tool)), INTAKEQ_API_BASE (Override the default IntakeQ API base URL (https://intakeq.com/api/v1)), MCP_API_KEY (Bearer token gate on the HTTP /mcp endpoint. Required in http mode unless MCP_ALLOW_NO_AUTH is true), MCP_ALLOW_NO_AUTH (Set to true to allow HTTP mode without MCP_API_KEY (local development only)), TRANSPORT (Transport mode: stdio (default) or http), MCP_BASE_URL (Base URL for HTTP transport (e.g. http://127.0.0.1:3000)), PORT (HTTP listen port (default 3000). HTTP transport only.). The author declared them in the registry entry; get the values from the project itself.