Smana/cloud-native-ref

Opiniated Cloud Native Platform Reference

This repository also configures its own agents. See what cloud-native-ref tells them →

103Stars on the repository
18Mods indexed here, across every type
todayLast push, which is what freshness is scored on
Apache-2.0Licence, which decides whether bodies are shown

flux-schema

01

Smana/cloud-native-ref

MCP server Claude CodeCodexCursor +2

One of 6 in .mcp.json

MCP server "flux-schema", hosted remotely at schemas.fluxoperator.dev, as configured in Smana/cloud-native-ref.

not rated 103 today A tokens not measured original Apache-2.0

victorialogs

02

Smana/cloud-native-ref

MCP server Claude CodeCodexCursor +2

One of 6 in .mcp.json

MCP server "victorialogs" as configured in Smana/cloud-native-ref. Launched with /usr/local/bin/mcp-victorialogs. Needs 1 environment variable to run.

not rated 103 today A tokens not measured original Apache-2.0

victoriametrics

03

Smana/cloud-native-ref

MCP server Claude CodeCodexCursor +2

One of 6 in .mcp.json

MCP server "victoriametrics" as configured in Smana/cloud-native-ref. Launched with /usr/local/bin/mcp-victoriametrics. Needs 2 environment variables to run.

not rated 103 today A tokens not measured original Apache-2.0

turbot-steampipe

04

Smana/cloud-native-ref

MCP server Claude CodeCodexCursor +2

One of 6 in .mcp.json

Steampipe MCP server to query cloud infrastructure, SaaS, code and more with SQL using AI. Runs locally from the @turbot/steampipe-mcp npm package. Needs 1 environment variable to run.

not rated 103 today A tokens not measured original Apache-2.0

chrome-devtools

05

Smana/cloud-native-ref

MCP server Claude CodeCodexCursor +2

One of 6 in .mcp.json

Lets the agent inspect and automate a live Chrome instance through the DevTools protocol: performance traces, network, console. Runs locally from the chrome-devtools-mcp npm package.

not rated 103 today A tokens not measured copy · 92% Apache-2.0

At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: