How to connect New Relic to OpenClaw
Connect New Relic to OpenClaw in one click. 12 New Relic tools your agent can call from chat. No API keys.
ClawLink gives OpenClaw a more practical New Relic setup than rolling your own integration. Instead of building auth, token refresh, and tool wiring yourself, you connect once and start using real New Relic actions from chat.
New Relic MCP for OpenClaw
Looking for a New Relic MCP server for OpenClaw? ClawLink connects New Relic to OpenClaw and exposes 12 New Relic tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself.
Install the New Relic skill
Copy this prompt into OpenClaw, or open the skill on ClawHub.
Setup
1Install ClawLink
Add the plugin to OpenClaw once.
- 2
Connect New Relic
One-click OAuth in the dashboard.
- 3
Use it from chat
Ask OpenClaw in plain English.
What OpenClaw can do with New Relic
- Developer Tools — 12 tools ready for OpenClaw.
- Common actions —
new_relic_add_notification_channels_to_policy(Add notification channels to policy),new_relic_add_tags_to_entity(Add tags to entity),new_relic_add_widgets_to_dashboard_page(Add widgets to dashboard page),new_relic_configure_cloud_integration(Configure cloud integration),new_relic_create_ai_notifications_channel(Create AI notifications channel),new_relic_create_ai_notifications_destination(Create AI notifications destination),new_relic_create_ai_workflow(Create AI workflow),new_relic_create_alert_channel(Create alert channel),new_relic_create_alert_policy(Create alert policy),new_relic_create_alerts_nrql_condition_static(Create alerts nrql condition static),new_relic_create_alerts_policy_graphql(Create alerts policy graphql),new_relic_create_api_access_keys(Create API access keys).
Just ask in plain English
On it. Using New Relic.
Example prompts
Use New Relic to add notification channels to policy and walk me through the result in plain English.
Use New Relic to add widgets to dashboard page and walk me through the result in plain English.
Use New Relic to configure cloud integration and walk me through the result in plain English.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want New Relic working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the New Relic API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected New Relic account becomes available to the agent without you building credential management. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for New Relic. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. |
| Agent usability | You still need to expose the right New Relic actions to the runtime in a format your agent can reliably use. | 12 tools for New Relic are already exposed through ClawLink, so the agent can read and act from chat immediately. |