AI and MCP integration

The server is available at https://monetize.nordicdevhouse.com/api/mcp. This product currently exposes public resources and prompts without executable tools.

{
  "type": "mcp",
  "server_label": "data-monetization-mcp",
  "server_url": "https://monetize.nordicdevhouse.com/api/mcp",
  "require_approval": {
    "always": {
      "read_only": false
    },
    "never": {
      "read_only": true
    }
  }
}

ChatGPT: In ChatGPT developer mode, create a custom MCP connection and paste the endpoint below. OAuth starts automatically.

https://monetize.nordicdevhouse.com/api/mcp

Claude / Claude Code: Add the remote HTTP server in Claude or Claude Code, then complete OAuth with /mcp.

claude mcp add --transport http data-monetization-mcp https://monetize.nordicdevhouse.com/api/mcp

Cursor: Add this server to your project or user MCP configuration.

{
  "mcpServers": {
    "data-monetization-mcp": {
      "url": "https://monetize.nordicdevhouse.com/api/mcp"
    }
  }
}

VS Code: Add this server to .vscode/mcp.json or your user MCP configuration.

{
  "servers": {
    "data-monetization-mcp": {
      "type": "http",
      "url": "https://monetize.nordicdevhouse.com/api/mcp"
    }
  }
}

Codex: Add the remote Streamable HTTP server with the Codex CLI. Codex stores the connection in your MCP configuration.

codex mcp add data-monetization-mcp --url https://monetize.nordicdevhouse.com/api/mcp

OpenAI Responses API: Use the remote MCP tool in the Responses API and keep approval enabled for non-read operations.

{
  "type": "mcp",
  "server_label": "data-monetization-mcp",
  "server_url": "https://monetize.nordicdevhouse.com/api/mcp",
  "require_approval": {
    "always": {
      "read_only": false
    },
    "never": {
      "read_only": true
    }
  }
}

The server is stateless. Use server/discover, follow long-running operations through the Tasks extension, and answer input_required confirmations without changing the sealed requestState value.

1. 1
   Grant only the API scopes the agent needs
2. 2
   Keep the API key server-side
3. 3
   Fulfil the signed confirmation round for write and destructive tools
4. 4
   Honor returned quota, retry, and circuit-breaker metadata
5. 5
   Preserve request and trace identifiers for auditing