> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt # Linking Metorial as a source Canonical URL: https://posthog.com/docs/data-pipelines/sources/metorial > **Cloud region:** This page uses US Cloud hosts. For an EU Cloud project, use `https://eu.posthog.com` instead of `https://us.posthog.com` or `https://app.posthog.com` (app host for links). ## On this page - [Prerequisites](#prerequisites) - [Adding a data source](#adding-a-data-source) - [Sync modes](#sync-modes) - [Configuration](#configuration) - [Supported tables](#supported-tables) - [Troubleshooting](#troubleshooting) **Beta release** This source is currently in **beta**. It works end to end, but you may still hit rough edges. [Let us know](https://us.posthog.com/#panel=support%3Asupport%3Adata_warehouse%3A%3Atrue) if you do. ![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_9608fcca70) ![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_dark_a92b0e022d) Let AI connect your sources for you Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog. `npx @posthog/wizard warehouse` ![PostHog Wizard hedgehog](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png) ![](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)Let AI connect your sources for you The Metorial connector syncs sessions, session messages, session errors, and more into the PostHog data warehouse, so you can analyze them alongside your product data. ## Prerequisites Credentials that can read the data you want to sync. PostHog only reads data, so read access is enough. ## Adding a data source 1. In PostHog, go to the [Sources tab](https://app.posthog.com/data-management/sources) of the data pipeline section. 2. Click **\+ New source** and click **Link** next to this source. 3. Enter your credentials (see [Configuration](#configuration) below) and click **Next**. 4. Select the tables you want to sync, choose a sync method and frequency, then click **Import**. Once the syncs are complete, you can start querying this data in PostHog. Enter your Metorial secret API key to pull your Metorial MCP data. Create a secret API key (`metorial_sk_...`) in your [Metorial dashboard](https://metorial.com). Keys are project-scoped, so connect one source per project you want to sync. A publishable key (`metorial_pk_...`) only exposes public data and will not work here. You'll be asked for: - **Secret API key**: for example `metorial_sk_...`. ## Sync modes Each table can be synced in one of several modes, depending on what the source supports: - **Webhook** (when available) – the source pushes changes to PostHog in real time. Fastest freshness, lowest ongoing cost, and the only mode that reliably captures updates and deletes. - **Incremental** – only new or updated rows are synced on each run, using a cursor field (such as an `updated_at` timestamp). Cheaper than a full refresh, but deletes aren't captured. - **Append only** – new rows are appended using a cursor field; existing rows are never updated. Ideal for immutable, append-only tables like event logs. - **Full refresh** – the whole table is reloaded on every sync. Use it when a table has no reliable cursor or when you need deletions reflected. See [sync methods](https://posthog.com/docs/data-pipelines/sources.md#sync-methods) for a full explanation of how each mode works and how to choose between them. All Metorial tables are full refresh. Each sync replaces the contents of the table. ## Configuration | Option | Type | Required | | --- | --- | --- | | `Secret API key` | password | Yes | ## Supported tables | Table | Description | Sync method | Incremental field | Primary key | | --- | --- | --- | --- | --- | | `sessions` | Connections to providers that let clients interact with MCP servers. | Incremental, Full refresh | updated\_at, created\_at | — | | `session_messages` | The MCP protocol messages exchanged during a session (read-only). | Incremental, Full refresh | created\_at | — | | `session_errors` | Errors that occurred during a session (read-only). | Incremental, Full refresh | created\_at | — | | `provider_runs` | Executions of provider operations within a session (read-only). | Incremental, Full refresh | updated\_at, created\_at | — | | `tool_calls` | Individual tool invocations within a session, tracking input, output, and status. | Incremental, Full refresh | created\_at | — | | `provider_deployments` | Running provider instances pinned to a specific provider version. | Incremental, Full refresh | updated\_at, created\_at | — | | `session_providers` | Providers actively connected to a session. Providers can be added or removed during the session. | Incremental, Full refresh | updated\_at, created\_at | — | | `integration_instances` | Integrations materialized for a specific actor, identity, or runtime configuration. | Incremental, Full refresh | updated\_at, created\_at | — | | `provider_versions` | Specific releases of a provider. Each version has its own tools, auth methods, and config schema. | Incremental, Full refresh | updated\_at, created\_at | — | | `providers` | Read-only catalog of MCP server integration templates available on Metorial. | Full refresh | — | — | ## Troubleshooting - If the connection fails with an authorization error, the secret API key is wrong, expired, or has been revoked. Create a new one, then reconnect the source. - If a table syncs no rows, the credential may not have access to that data. Check its permissions, then reconnect the source. If your sync is failing or data looks wrong, see the [Data warehouse troubleshooting guide](https://posthog.com/docs/data-warehouse/troubleshooting.md). If that doesn't help, [contact support](https://us.posthog.com/#panel=support%3Asupport%3Adata_warehouse%3A%3Atrue) – we're happy to help.