Put AI to work across your company, safely

Every agent gets approved MCP tools and skills, tied to the person behind it. One MCP gateway, governed by role and recorded call by call.

Connect any agent to any tool.

The problem

AI reaches company tools faster than anyone can govern it

The moment a second team wants agents connected to real apps, the workarounds start. These are the three that stall most rollouts.

  1. 01

    Shadow MCP

    People install MCP servers on their own laptops to get work done, and nobody knows which tools reach company data. What is shadow AI?

  2. 02

    API keys in config files

    A personal token pasted into a local config works, so a teammate copies it. Months later it still works, with no owner and no expiry. Are MCP servers secure?

  3. 03

    No record of what ran

    When an agent changes the wrong record, the first question is whose access it used. A shared credential has no answer. Audit agent activity

Connect, govern, and see
every agent call.

Metorial puts one governed layer between the AI clients your company uses and the tools they reach. See how the MCP gateway works.

lumon-industries.metorial.com
Metorial dashboard
Codex
metorial · support-agent
session live
userA Pro customer says checkout keeps failing. Dig into it and follow up for me.
agentOn it. I'll pull their recent payments, check the error logs, and open a ticket if it's a real bug.
tool
stripelist_charges→ 3 failed · payment_intent timeout
tool
sentrysearch_issues→ matched CHECKOUT-1471 · 28 events today
tool
linearcreate_issue→ ENG-2231 opened · P1
agentThree charges failed on a payment-intent timeout. Filed ENG-2231 and pinged the on-call channel.
tool
slackpost_message→ sent to #payments-oncall
tool
notionupdate_page→ incident log → Investigating
userRefund the customer and send them a heads up.
agentRefunding the failed attempts and emailing them now.
tool
stripecreate_refund→ $49.00 refunded
tool
gmailsend_email→ reply sent to [email protected]
tool
hubspotcreate_note→ logged on contact timeline
agentDone — refund issued, customer updated, and ENG-2231 tracks the root cause.
userSet up a follow-up with their account owner and share a recap.
agentBooking the call and writing up the recap now.
tool
google-calendarcreate_event→ Fri 10:00 · owner invited
tool
google-docscreate_document→ "Lumon checkout recap" shared
agentScheduled for Friday and the recap doc is shared with the account owner.
userOne more — pull this week’s failed-payment numbers so we can spot a trend.
agentQuerying the data warehouse and wiring up an alert so we catch the next spike.
tool
postgresrun_query→ 41 failures · +18% WoW
tool
datadogcreate_monitor→ alert on timeout rate > 2%
tool
linearcreate_comment→ posted trend to ENG-2231
agentFailures are up 18% week over week — added a Datadog monitor so the next spike pages on-call automatically.
Ask the agent to handle a task...
Metorial  142 tools connected across 18 integrations

Connect, govern, and see
every agent call.

Metorial puts one governed layer between the AI clients your company uses and the tools they reach. See how the MCP gateway works.

metorial · support-agent
session live
userA Pro customer says checkout keeps failing. Dig into it and follow up for me.
agentOn it. I'll pull their recent payments, check the error logs, and open a ticket if it's a real bug.
tool
stripelist_charges→ 3 failed · payment_intent timeout
tool
sentrysearch_issues→ matched CHECKOUT-1471 · 28 events today
tool
linearcreate_issue→ ENG-2231 opened · P1
agentThree charges failed on a payment-intent timeout. Filed ENG-2231 and pinged the on-call channel.
tool
slackpost_message→ sent to #payments-oncall
Ask the agent to handle a task...
Metorial  142 tools connected across 18 integrations
Metorial dashboard
Metorial dashboard

How Metorial works

One governed path from the AI client each person already uses to the company tools they are allowed to reach.

Metorial single sign-on settings showing identity providers.
  1. People sign in to their portal with the identity provider you already run. Their groups decide which integrations and skills they see.

Your tools.
Ready for agents.

Pick from 1,000 ready-to-use integrations, add your own, and let any agent reach them through one secure connection.

Give your team a place to connect agents.

People sign in, see the tools and skills they're allowed to use, and connect their agent with one link. You stay in control of who can do what.

lumon-industries.metorial.com
Metorial Portals showing the integrations and skills an employee can connect their agent to.
lumon-industries.metorial.com

What your team can do with skills

  1. Write

    See what you can use

    Each person opens their portal and finds the integrations and skills they have access to. Everything is already approved, so there is nothing to configure or figure out on their own.

  2. Connect

    Connect with one link

    Paste a single link into the agent they already use, like Cursor or Claude. No tokens to copy, no accounts to create, and no setup for IT to manage.

  3. Share

    Share what your team knows

    An expert writes a skill once in a shared editor, and it shows up for everyone who should have it. The skill carries the instructions and the tools it needs, so agents follow the same approach every time.

How it works

How every tool call stays secure

The same four checks apply to every agent and every client, from the first sign-in to the record your security team reviews.

  1. 1

    Sign in with your identity provider

    People sign in with SAML SSO, and SCIM keeps accounts and groups in step, so leavers lose access when they leave.
  2. 2

    Policy decides what is allowed

    Access policies grant tools by person and group, down to single tools and read-only sets.
  3. 3

    Protoguard screens the call

    Protoguard checks every request for prompt injection and watches providers for unexpected schema changes.
  4. 4

    It runs isolated and is recorded

    The call runs in its own enclave with the person’s own credentials from Vault, and lands in the audit log.

What customers say about Metorial

Moonfire

“With Metorial, we've been able to build a single pane of glass across all our data sources, tools, and messaging platforms, and it's worked incredibly well.”

Ben Coughlan
Ben CoughlanSite Reliability Engineer, Moonfire
Read Story

Frequently asked questions

The questions teams ask most before rolling Metorial out.

  1. What is Metorial?
    Metorial is an open-source MCP and skills gateway. It connects AI agents and assistants to the tools and data your company uses, behind one sign-in, with access control and an audit log. See how the MCP gateway works.
  2. An MCP gateway sits between AI clients like Claude, ChatGPT and Cursor and the MCP servers that connect them to company apps. It handles routing, sign-in, access rules and logging in one place, so each team does not solve them again.
  3. Any MCP-compatible client, including Claude, ChatGPT, Cursor and Codex. Each person pastes one Magic MCP URL and gets the same approved tools, so switching client does not mean setting access up again.
  4. Yes. Metorial is open core on GitHub and runs self-hosted or on-prem, or you can use Metorial Cloud. See how it works.
  5. People sign in with the SSO you already run, and SCIM keeps accounts in step. Admins grant tools by role, and access control applies everywhere at once, across every client and agent.
  6. Every tool call runs on a real person's identity and is recorded. Metorial is SOC 2 Type II and GDPR compliant, with EU and US regions, and checks each call for prompt injection. See security.
  7. There is a free Dev plan, a fixed-price Scale plan, and custom Enterprise pricing. See pricing for the current plans.
  8. Yes. Alongside the catalog, you can connect your own internal servers and remote MCP servers from other vendors, behind the same access rules and audit log.

Ready to connect your agents?

Get started for free, or book a demo to see Metorial with your own tools.