Gcore (BYOK)

Gcore (BYOK) — connector documentation

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

What Gcore (BYOK) is for

Gcore (BYOK) lets an AI assistant read your own Gcore data through the Gcore API with a key you supply (permanent API token). Read-only: 12 tools (get_cdn_service, list_cdn_resources, get_cdn_resource, list_cdn_rules, list_cdn_origin_groups, list_cdn_ssl_certificates, list_cdn_purge_history, list_dns_zones, get_dns_zone, list_dns_rrsets, list_waap_domains, get_waap_domain). 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.gcore.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Gcore. Gcore 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:

• "Is my Gcore CDN service enabled?"
• "Which CDN resources do I have on Gcore and are they active?"
• "Show Gcore CDN resource 1"
• "What rules does Gcore CDN resource 1 have?"
• "Which origin groups are configured in Gcore CDN?"
• "Which Gcore CDN certificates expire soon?"

What it does

• get_cdn_service: Show the state of your Gcore CDN service: whether it is enabled, status, utilization level and the default CNAME.
• list_cdn_resources: List CDN resources with domain, name, active and enabled flags, status, origin group, protocol, HTTPS and shielding flags and dates.
• get_cdn_resource: Get one CDN resource: delivery domain, status, origin group and protocol, HTTPS, shielding and dates. Option details are left out.
• list_cdn_rules: List the path rules of one CDN resource with name, pattern, active flag, weight and origin group.
• list_cdn_origin_groups: List origin groups with name, authentication type, failover flag and whether CDN resources use them. Origin credentials and sources are left out.
• list_cdn_ssl_certificates: List SSL certificates used by CDN resources with name, subject, issuer, validity dates and whether they were issued automatically.
• list_cdn_purge_history: List past cache purge requests with id, status, resource, type and creation time.
• list_dns_zones: List your Gcore DNS zones with name, enabled flag, DNSSEC state, status, serial and record counts.
• get_dns_zone: Get one DNS zone: SOA values, DNSSEC state, status, and record counts.
• list_dns_rrsets: List the record sets of a DNS zone with name, type, TTL and record contents.
• list_waap_domains: List domains protected by Gcore WAAP with name, status (active, bypass, monitor, locked), aliases and linked CDN resource.
• get_waap_domain: Get one WAAP domain by id: name, status, aliases and creation time.

BYOK key

You bring your own Gcore permanent API token (https://accounts.gcore.com/reports/dashboard). 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.gcore.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

• https://docs.gcore.com/api-reference/overview (the API this connector calls, with a BYOK key)

Live from the Gcore API (api.gcore.com) with a BYOK key; documentation: https://docs.gcore.com/api-reference/overview. 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 Gcore. Gcore 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 Gcore account.

Built for: Worldwide. Languages: English.

Gcore (BYOK) — Privacy Policy

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

What Gcore (BYOK) is. Gcore (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Gcore data: Read your Gcore CDN resources, origin groups, certificates, purge history, DNS zones and records and WAAP domains with your own API token. You bring your own Gcore permanent API token; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Gcore 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.gcore.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 Gcore 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 Gcore receives. The request we make on your behalf, including the key and the arguments, under Gcore's own terms and privacy policy. Gcore acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Gcore 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 Gcore 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. Gcore (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 Gcore at any time to end all access.

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

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

Gcore (BYOK) — Terms of Service

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

1. The Service. Gcore (BYOK) provides: Read your Gcore CDN resources, origin groups, certificates, purge history, DNS zones and records and WAAP domains with your own API token. 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 Gcore credentials and only access data you are allowed to access. Gcore's terms apply to your use of Gcore; 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 Gcore. Gcore 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 Gcore returns, lightly trimmed; it may be incomplete, delayed or changed by Gcore. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Gcore 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 Gcore'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; Gcore 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 Gcore 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 Gcore 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-gcore

Gcore (BYOK) support

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

• MCP endpoint: https://byok-gcore.connectorbay.com/mcp
• REST API: https://byok-gcore.connectorbay.com/openapi.json
• Live status: https://byok-gcore.connectorbay.com/health

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. Gcore (BYOK) never asks for them.