Metorial Sessions (BYOK) — connector documentation

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

What Metorial Sessions (BYOK) is for

Metorial Sessions (BYOK) lets an AI assistant read your own Metorial Sessions data through the Metorial Sessions API with a key you supply (Metorial secret API key). Read-only: 8 tools (list_sessions, get_session, list_session_providers, list_session_templates, get_session_template, list_provider_runs, get_provider_run, list_session_errors). 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.metorial.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Metorial Sessions. Metorial Sessions 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 Metorial sessions have errors?"
"Show Metorial session ses_1"
"Which providers are attached to Metorial session ses_1?"
"What Metorial session templates do I have?"
"Show Metorial session template stp_1"
"Which Metorial provider runs are still running?"

What it does

list_sessions: List MCP sessions with status, connection state, error and warning flags and message-count usage (no client secrets or connection URLs).
get_session: Get one session by id with status, connection state, error and warning flags and message-count usage (no client secret).
list_session_providers: List the providers attached to sessions with deployment, template origin and message-count usage.
list_session_templates: List the reusable session templates of your project with name, description and status.
get_session_template: Get one session template by id with name, description and status.
list_provider_runs: List provider runs (one per running tool server instance) with status, session, provider and completion time.
get_provider_run: Get one provider run by id with status, session, provider and completion time (no logs).
list_session_errors: List session errors with error code, status, session, run and similar-error count (error messages and data are left out).

BYOK key

You bring your own Metorial Sessions Metorial secret API key (https://metorial.com/docs/build/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.metorial.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://metorial.com/docs/build/api (the API this connector calls, with a BYOK key)

Live from the Metorial Sessions API (api.metorial.com) with a BYOK key; documentation: https://metorial.com/docs/build/api. 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 Metorial Sessions. Metorial Sessions 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 Metorial Sessions account.

Built for: Worldwide. Languages: English.