Can I use New Relic as a CLI?

Yes. KosmoKrator exposes a New Relic CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose New Relic through MCP?

Yes. The KosmoKrator MCP gateway can expose selected New Relic tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are New Relic credentials stored?

New Relic credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for New Relic MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

analytics

New Relic MCP Integration for Codex

Connect New Relic to Codex through the local KosmoKrator MCP gateway with scoped tools, credentials, and write policy.

7 functions 6 read 1 write API key auth

Submit New Relic feedback View package source

Connect New Relic to Codex

Use KosmoKrator as a local MCP proxy for Codex so coding sessions can reach selected integrations with explicit write policy.

Register kosmo mcp:serve as a local stdio server and choose the integration allowlist. The gateway is local, scoped to this integration, and starts with --write=deny so Codex can inspect read-capable tools without receiving write access by default.

New Relic MCP Config for Codex

Keep write access denied or ask-based unless the workspace is trusted.

{
  "mcpServers": {
    "kosmokrator-newrelic": {
      "type": "stdio",
      "command": "kosmo",
      "args": [
        "mcp:serve",
        "--integration=newrelic",
        "--write=deny"
      ]
    }
  }
}

Run the Gateway Manually

kosmokrator mcp:serve --integration=newrelic --write=deny

Why Use KosmoKrator Here

Scoped tools

Expose only New Relic instead of a broad multi-service tool list.

Local credentials

Reuse credentials already configured for the KosmoKrator CLI and Lua runtime.

Write policy

Start read-only, then opt into ask or allow for trusted workspaces.

New Relic Tools Visible to Codex

Codex sees stable MCP tool names generated from the New Relic integration catalog.

MCP tool	Source function	Type	Description
`integration__newrelic__newrelic_list_applications`	`newrelic.newrelic_list_applications`	Read	List APM applications in the configured New Relic account. Returns application names, GUIDs, IDs, language, reporting status, and health status.
`integration__newrelic__newrelic_get_application`	`newrelic.newrelic_get_application`	Read	Get details of a specific New Relic APM application by its application ID, including language, health status, and Apdex thresholds.
`integration__newrelic__newrelic_list_deployments`	`newrelic.newrelic_list_deployments`	Read	List deployment markers for a New Relic APM application. Requires the application entity GUID.
`integration__newrelic__newrelic_create_deployment`	`newrelic.newrelic_create_deployment`	Write	Record a new deployment marker in New Relic for a given application. This helps correlate deploys with performance changes.
`integration__newrelic__newrelic_list_alert_policies`	`newrelic.newrelic_list_alert_policies`	Read	List alert policies in the configured New Relic account. Returns policy names, IDs, and incident preferences.
`integration__newrelic__newrelic_list_dashboards`	`newrelic.newrelic_list_dashboards`	Read	List dashboards in the configured New Relic account. Returns dashboard titles, GUIDs, timestamps, and owner information.
`integration__newrelic__newrelic_get_current_user`	`newrelic.newrelic_get_current_user`	Read	Get the profile of the currently authenticated New Relic user. Useful for verifying API credentials and retrieving account information.

Related New Relic Pages

New Relic CLIUse direct JSON commands instead of MCP discovery. New Relic MCPFull gateway reference and MCP tool names. KosmoKrator for CodexClient-level gateway setup.