Nebcore Ai

nebcore-ai

NebCore AI tools for Claude Code, exposed as MCP tools.

What you get

Once installed and authenticated, Claude Code has structured tool access to:

• Issue tracking: list, read, comment on issues; transition state; request approvals; list projects, agents, skills.
• Platform observability: Kubernetes state queries, GitOps application status, cost summaries, policy violations, compliance scores.
• Per-tenant scope: every tool call is gated by your account's permissions. Read-only by default; mutation tools require explicit grants.

Install

This plugin connects to NebCore AI via a local CLI bridge. You need:

1. nebcli on your PATH:

   brew install nebinfra/tap/nebcli   # macOS / Linuxbrew
   

   Or download a release binary from the nebcli releases page and place it on your PATH.

2. Authenticate once. This opens a browser to complete sign-in and mints a 30-day API key stored in ~/.nebcore/config.yaml:

   nebcli login
   

3. Add the plugin in Claude Code:

   /plugin add nebinfra/claude-plugins/nebcore-ai
   

   Or via marketplace UI: select nebinfra → nebcore-ai → install.

That's it. Claude Code spawns nebcli mcp as a local subprocess whenever it needs tools; the CLI reads your stored API key and forwards JSON-RPC requests to the NebCore platform.

How it works

Claude Code ──stdio JSON-RPC──▶ nebcli mcp ──HTTPS Bearer──▶ NebCore platform
                                       │
                                       ├ reads NEBCORE_PLATFORM_KEY env, or
                                       └ ~/.nebcore/config.yaml (set by login)

The API key never leaves your machine. Each tool invocation produces a server-side audit record on the platform.

Refreshing your credential

The CLI auto-renews keys nearing expiry. To force a refresh manually:

nebcli login         # re-runs the browser auth flow

To revoke a key (e.g. when retiring a laptop):

nebcli sessions list
nebcli sessions revoke <session-id>

Multiple accounts / environments

Switch between accounts the same way you switch kubeconfig contexts:

nebcli ctx          # list contexts
nebcli ctx use <name>

The MCP bridge always uses the current context's stored key.

Troubleshooting

• nebcli mcp exits with no platform API key available: run nebcli login.
• HTTP 401 mid-session: the stored key was revoked or expired; re-run nebcli login and restart Claude Code.
• Tools missing from the catalog you expected: your account's scope vector may not include them. Contact your NebCore admin.

Support

• CLI docs: https://docs.nebcore.ai/cli
• Issues: https://github.com/nebinfra/nebcli/issues