Grafana Cloud (BYOK)
Read your Grafana Cloud stacks, their regions, readiness, connection endpoints, usage counts and installed plugins with your own access policy token
Read your Val Town vals, branches, files, blobs, organizations and logs with your own API token
Unify Dynamics LLC
Real questions, and the tools your agent calls to answer them.
get_melist_valslist_my_valsget_valget_val_by_namelist_branchesVal Town (BYOK) lets an AI assistant read your own Val Town data through the Val Town API with a key you supply (API token). Read-only: 10 tools (get_me, list_vals, list_my_vals, get_val, get_val_by_name, list_branches, list_files, list_blobs, list_organizations, list_logs). 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.val.town. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Val Town. Val Town and its logos are trademarks of their owners and are used only to say which service the connector works with.
Sources: Live from the Val Town API (api.val.town) with a BYOK key; documentation: https://docs.val.town/api/. Endpoints checked against that documentation on 2026-10-16.
The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.
10 tools, grouped by job. Every one is read-only or compute-only.
https://byok-valtown.connectorbay.com/mcpThree ways in, the same 10 tools.
https://byok-valtown.connectorbay.com/mcpPOST https://byok-valtown.connectorbay.com/v1/tools/<tool>https://connectorbay.com/openai/byok-valtown.jsonhttps://connectorbay.com/v1/chat/completions · how it worksX-Upstream-Key header (get one at www.val.town).Val Town (BYOK) lets an AI assistant read your own Val Town data through the Val Town API with a key you supply (API token). It is a hosted MCP server with 10 tools such as Get me, List vals, List my vals, Get val, Get val by name, List branches, published by Unify Dynamics LLC. It is independent and not affiliated with Val Town.
Add the MCP endpoint https://byok-valtown.connectorbay.com/mcp to your client's MCP, connector or integration settings (streamable HTTP, no OAuth). For REST, POST JSON to https://byok-valtown.connectorbay.com/v1/tools/<tool>; the OpenAPI description is at /openapi.json. For OpenAI function calling, load https://connectorbay.com/openai/byok-valtown.json.
Yes: this is a bring-your-own-key connector. Create a API token at https://www.val.town/settings/api and send it in the X-Upstream-Key header. ConnectorBay uses it for that one call only and never stores, logs or caches it.
Yes. Every tool reads or computes. Nothing is created, changed, sent, paid or deleted in your account.
Yes. It is free to use within the published rate limits; an optional Pro key raises them. There is no account to create.
Read your Grafana Cloud stacks, their regions, readiness, connection endpoints, usage counts and installed plugins with your own access policy token
Read your Grafana Cloud library panels, playlists, dashboard tags and versions, public dashboard list and snapshots with your own service account token
Read your Grafana OnCall integrations, routes, escalation chains and policies, schedules, alert groups, teams and Slack channels with your own OnCall API key
Read your Microsoft Entra tenant: organization profile, domains, licenses, directory roles, groups, devices and administrative units with a Microsoft Graph access token
Read Microsoft Intune device policy configuration: compliance and configuration policies, enrollment rules, apps, roles and device counts, with a Microsoft Graph access token
Read Microsoft 365 service health, incidents and Message center announcements for your tenant with a Microsoft Graph access token
https://byok-valtown.connectorbay.com/mcpPOST https://byok-valtown.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-valtown.connectorbay.com/openapi.jsonX-Upstream-Key header of every request (never stored, logged or cached)https://byok-valtown.connectorbay.com/health · Tool schemas: https://byok-valtown.connectorbay.com/tools.jsonVal Town (BYOK) lets an AI assistant read your own Val Town data through the Val Town API with a key you supply (API token). Read-only: 10 tools (get_me, list_vals, list_my_vals, get_val, get_val_by_name, list_branches, list_files, list_blobs, list_organizations, list_logs). 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.val.town. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Val Town. Val Town 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:
get_me: Show the Val Town account the token belongs to: id, type, username, bio, tier and profile URL.list_vals: List vals visible to you (all public ones plus your own unlisted and private ones), optionally by privacy or owner, newest first.list_my_vals: List the vals owned by the token's account (beta endpoint), with offset paging.get_val: Get one val's name, privacy, description, author and links.get_val_by_name: Find a val by its owner's username and the val name.list_branches: List a val's branches with version, creation and update time and the branch they were forked from.list_files: List files and directories of a val (metadata only: name, path, type, version, update time).list_blobs: List the keys, sizes and last-modified times of your blob storage entries, optionally by key prefix.list_organizations: List the organizations you belong to.list_logs: List recent OpenTelemetry log lines from your vals, newest first, optionally within a time window or for one file.You bring your own Val Town API token (https://www.val.town/settings/api). 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.val.town 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.
Live from the Val Town API (api.val.town) with a BYOK key; documentation: https://docs.val.town/api/. Endpoints checked against that documentation on 2026-10-16.
Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Val Town. Val Town 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 Val Town account.
Built for: Worldwide. Languages: English.
Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.
What Val Town (BYOK) is. Val Town (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Val Town data: Read your Val Town vals, branches, files, blobs, organizations and logs with your own API token. You bring your own Val Town API token; the assistant sends it to us with each request.
BYOK key. The key you supply is used to make the one Val Town 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.val.town, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Val Town 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 Val Town receives. The request we make on your behalf, including the key and the arguments, under Val Town's own terms and privacy policy. Val Town acts at your direction and is the only recipient of the data of your request besides our hosting provider.
What we return. The answer Val Town 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 Val Town 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. Val Town (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 Val Town at any time to end all access.
Children. Val Town (BYOK) is a general-audience service operated by the adult using the assistant, under Val Town's own age rules.
Changes. We will post changes here with a new effective date.
Effective 24 October 2026. These terms govern use of the Val Town (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").
Email agent@connectorbay.com. We answer within two business days.
https://byok-valtown.connectorbay.com/mcphttps://byok-valtown.connectorbay.com/openapi.jsonWhen 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. Val Town (BYOK) never asks for them.