Be the first to get access to new connectors. Get early access →
ConnectorBay Early access
Discover
New Relic Alerts (BYOK) icon

New Relic Alerts (BYOK)

Read your New Relic alert policies, NRQL alert conditions and muting rules through NerdGraph with your own user API key

Unify Dynamics LLC

Tools6read-only
Sign-inBYOKbring your own key
Key keptNeverused for one call only
PriceFreeoptional Pro limits
ProviderNew Relic Alertsunofficial, not affiliated
Works withMCP · RESTany agent

Try asking

Real questions, and the tools your agent calls to answer them.

Which alert policies does my New Relic account have?
Tools called
list_alert_policies
Show New Relic alert policy 456
Tools called
get_alert_policy
Which NRQL alert conditions watch the Transaction event in New Relic?
Tools called
search_nrql_conditions
Show New Relic NRQL alert condition 123
Tools called
get_nrql_condition
Which New Relic muting rules are enabled?
Tools called
list_muting_rules
Show New Relic muting rule 77
Tools called
get_muting_rule

About

New Relic Alerts (BYOK) lets an AI assistant read your own New Relic Alerts data through the New Relic Alerts API with a key you supply (New Relic user API key (US data center)). Read-only: 6 tools (list_alert_policies, get_alert_policy, search_nrql_conditions, get_nrql_condition, list_muting_rules, get_muting_rule). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.newrelic.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by New Relic Alerts. New Relic Alerts and its logos are trademarks of their owners and are used only to say which service the connector works with.

Sources: Live from the New Relic Alerts API (api.newrelic.com) with a BYOK key; documentation: https://docs.newrelic.com/docs/apis/nerdgraph/get-started/introduction-new-relic-nerdgraph/. Endpoints checked against that documentation on 2026-10-16.

Privacy

The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.

Data not collectedNo account, no profile, no stored prompts or results.

What it can do

6 tools, grouped by job. Every one is read-only or compute-only.

OpenAPI
Read your data6 tools
  • List alert policiesList alert policies of an account with id, name, incident preference (PER_POLICY, PER_CONDITION, PER_CONDITION_AND_TARGET) and entity guid.
  • Get alert policyGet one alert policy by id: name, incident preference and entity guid.
  • Search nrql conditionsSearch NRQL alert conditions of an account, optionally by exact name, name fragment, policy id or query fragment.
  • Get nrql conditionGet one NRQL alert condition by id: query, thresholds, signal and expiration settings, policy id and enabled flag.
  • List muting rulesList muting rules that silence notifications: name, description, enabled flag and the matching conditions.
  • Get muting ruleGet one muting rule by id with its conditions and schedule (start, end, time zone, repeat).

Information

PublisherUnify Dynamics LLC
CategoryDeveloper tools
LanguagesEnglish
Built forWorldwide
CompatibilityAny MCP client · any agent · REST
Version0.1.0
MCP endpointhttps://byok-newrelic-alerts.connectorbay.com/mcp
REST APIopenapi.json
SupportGet help · Status
CountryWorldwide
FunctionOther
LayerDeep connectors

Connect it to your agent

Three ways in, the same 6 tools.

MCP (Claude, Cursor, Windsurf, VS Code, any MCP client)https://byok-newrelic-alerts.connectorbay.com/mcp
RESTPOST https://byok-newrelic-alerts.connectorbay.com/v1/tools/<tool>
OpenAI function callinghttps://connectorbay.com/openai/byok-newrelic-alerts.json
OpenAI-compatible chathttps://connectorbay.com/v1/chat/completions · how it works
  • Add the MCP URL in your client's connector, MCP or integration settings (streamable HTTP, no OAuth).
  • Key: send your New Relic user API key (US data center) in the X-Upstream-Key header (get one at one.newrelic.com).
  • Ask a question; the agent picks the right tool and answers from the live data.

New Relic Alerts connector: questions and answers

What is the New Relic Alerts connector?

New Relic Alerts (BYOK) lets an AI assistant read your own New Relic Alerts data through the New Relic Alerts API with a key you supply (New Relic… It is a hosted MCP server with 6 tools such as List alert policies, Get alert policy, Search nrql conditions, Get nrql condition, List muting rules, Get muting rule, published by Unify Dynamics LLC. It is independent and not affiliated with New Relic Alerts.

How do I connect New Relic Alerts to Claude, ChatGPT or Cursor?

Add the MCP endpoint https://byok-newrelic-alerts.connectorbay.com/mcp to your client's MCP, connector or integration settings (streamable HTTP, no OAuth). For REST, POST JSON to https://byok-newrelic-alerts.connectorbay.com/v1/tools/<tool>; the OpenAPI description is at /openapi.json. For OpenAI function calling, load https://connectorbay.com/openai/byok-newrelic-alerts.json.

Do I need a New Relic Alerts account or API key?

Yes: this is a bring-your-own-key connector. Create a New Relic user API key (US data center) at https://one.newrelic.com/api-keys and send it in the X-Upstream-Key header. ConnectorBay uses it for that one call only and never stores, logs or caches it.

Is New Relic Alerts read-only?

Yes. Every tool reads or computes. Nothing is created, changed, sent, paid or deleted in your account.

Is the New Relic Alerts connector free?

Yes. It is free to use within the published rate limits; an optional Pro key raises them. There is no account to create.

More like this

More in Other

SchoolDigger (BYOK)

Search US K-12 schools and districts, read school profiles, rankings and enrollment details with your own SchoolDigger app ID and app key

Live · MCP + REST8 tools

Scorecard (BYOK)

Read your Scorecard AI evaluation projects, testsets, metrics, metric groups, runs and systems with your own API key

Live · MCP + REST10 tools

Scrive (BYOK)

Read your Scrive user groups, group settings, folder structure, data retention policy and usage statistics with your own personal access credentials

Live · MCP + REST9 tools

Secoda (BYOK)

Read your Secoda data catalog resources, integrations, collections, tags, monitors, incidents and lineage with your own API key

Live · MCP + REST11 tools

SecurityTrails (BYOK)

Read domain DNS, subdomains, WHOIS, DNS and WHOIS history, certificates and neighbouring IPs from SecurityTrails with BYOK

Live · MCP + REST9 tools

Segment (BYOK)

Read your Segment workspace, tracking plans, functions, event volume and MTU and API call usage with your own Segment Public API token

Live · MCP + REST11 tools

Documentation

Back to top

New Relic Alerts (BYOK) — connector documentation

  • MCP endpoint: https://byok-newrelic-alerts.connectorbay.com/mcp
  • REST API: POST https://byok-newrelic-alerts.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-newrelic-alerts.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own New Relic Alerts New Relic user API key (US data center), sent in the X-Upstream-Key header of every request (never stored, logged or cached)
  • Health: https://byok-newrelic-alerts.connectorbay.com/health · Tool schemas: https://byok-newrelic-alerts.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-newrelic-alerts · agent@connectorbay.com

What New Relic Alerts (BYOK) is for

New Relic Alerts (BYOK) lets an AI assistant read your own New Relic Alerts data through the New Relic Alerts API with a key you supply (New Relic user API key (US data center)). Read-only: 6 tools (list_alert_policies, get_alert_policy, search_nrql_conditions, get_nrql_condition, list_muting_rules, get_muting_rule). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.newrelic.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by New Relic Alerts. New Relic Alerts and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

  • "Which alert policies does my New Relic account have?"
  • "Show New Relic alert policy 456"
  • "Which NRQL alert conditions watch the Transaction event in New Relic?"
  • "Show New Relic NRQL alert condition 123"
  • "Which New Relic muting rules are enabled?"
  • "Show New Relic muting rule 77"

What it does

  • list_alert_policies: List alert policies of an account with id, name, incident preference (PER_POLICY, PER_CONDITION, PER_CONDITION_AND_TARGET) and entity guid. Page with the cursor.
  • get_alert_policy: Get one alert policy by id: name, incident preference and entity guid.
  • search_nrql_conditions: Search NRQL alert conditions of an account, optionally by exact name, name fragment, policy id or query fragment. Returns query, thresholds (terms), signal settings and enabled flag. Page with the cursor.
  • get_nrql_condition: Get one NRQL alert condition by id: query, thresholds, signal and expiration settings, policy id and enabled flag.
  • list_muting_rules: List muting rules that silence notifications: name, description, enabled flag and the matching conditions.
  • get_muting_rule: Get one muting rule by id with its conditions and schedule (start, end, time zone, repeat).

BYOK key

You bring your own New Relic Alerts New Relic user API key (US data center) (https://one.newrelic.com/api-keys). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.newrelic.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

Live from the New Relic Alerts API (api.newrelic.com) with a BYOK key; documentation: https://docs.newrelic.com/docs/apis/nerdgraph/get-started/introduction-new-relic-nerdgraph/. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by New Relic Alerts. New Relic Alerts and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your New Relic Alerts account.

Built for: Worldwide. Languages: English.

Privacy policy

Back to top

New Relic Alerts (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What New Relic Alerts (BYOK) is. New Relic Alerts (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own New Relic Alerts data: Read your New Relic alert policies, NRQL alert conditions and muting rules through NerdGraph with your own user API key. You bring your own New Relic Alerts New Relic user API key (US data center); the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one New Relic Alerts call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to api.newrelic.com, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If New Relic Alerts rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What New Relic Alerts receives. The request we make on your behalf, including the key and the arguments, under New Relic Alerts's own terms and privacy policy. New Relic Alerts acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer New Relic Alerts gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your New Relic Alerts data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. New Relic Alerts (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at New Relic Alerts at any time to end all access.

Children. New Relic Alerts (BYOK) is a general-audience service operated by the adult using the assistant, under New Relic Alerts's own age rules.

Changes. We will post changes here with a new effective date.

Terms of service

Back to top

New Relic Alerts (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the New Relic Alerts (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

  1. The Service. New Relic Alerts (BYOK) provides: Read your New Relic alert policies, NRQL alert conditions and muting rules through NerdGraph with your own user API key. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
  2. Your own key, your own account. You must use your own New Relic Alerts credentials and only access data you are allowed to access. New Relic Alerts's terms apply to your use of New Relic Alerts; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
  3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by New Relic Alerts. New Relic Alerts and its logos are trademarks of their owners and are used only to say which service the connector works with.
  4. No advice, no guarantees. Output is the data New Relic Alerts returns, lightly trimmed; it may be incomplete, delayed or changed by New Relic Alerts. Check important facts at the source.
  5. Read-only. The Service does not create, change, send or delete anything in your New Relic Alerts account.
  6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent New Relic Alerts's controls, or to attack any system.
  7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; New Relic Alerts may change or end its API at any time.
  8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
  9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your New Relic Alerts key.
  10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action New Relic Alerts takes on your account. Our total liability is limited to US $100.
  11. Governing law. California law; venue in San Mateo County, California.
  12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-newrelic-alerts

New Relic Alerts (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. New Relic Alerts (BYOK) never asks for them.

Get New Relic Alerts (BYOK)

Free · BYOK · Read-only

BYOK: bring your own keyThis connector uses your own New Relic Alerts New Relic user API key (US data center). Create one at https://one.newrelic.com/api-keys, with the fewest permissions it needs (read-only if the provider offers it). Your assistant sends it in the X-Upstream-Key header with every request. It is used for that one call only: never stored, logged or cached, and only ever sent to New Relic Alerts. Revoke it at the provider whenever you like. Unofficial connector: not affiliated with New Relic Alerts.