Skills & MCP Gateway

Connect a tool once. Every agent gets it.

The zwrm MCP gateway puts your tools and skills behind one endpoint. Agents, Claude Desktop, Cursor, and any other MCP client use the same connections with scoped access.

  • One MCP endpoint
  • Scoped credentials
  • Reusable skills
MCP Gateway
4 tools · 4 clients 5 tools · 4 clients
Connect your stack

Bring the tools your team already relies on.

Any MCP server

Add any MCP-compatible server as an upstream. Your agents can also build new connections for you, so you are never limited to the integrations we publish.

From silo to shared

One endpoint in three steps.

  1. 01

    Add an upstream

    Paste the URL of an MCP server or pick one of the published integrations. Credentials are stored once, in the gateway.

  2. 02

    Scope the access

    Decide which agents and clients may use which tools. Every consumer sees only what it was granted.

  3. 03

    Point everything at the gateway

    Agents on zwrm are connected automatically. External clients such as Claude Desktop or Cursor get one URL and one token.

What you get

Tools and skills, managed in one place.

Stop pasting the same API key into five agents and three desktop apps.

  • One endpoint, every consumer

    Agents, scheduled runs, and external AI clients share the same gateway. Add a tool once and every consumer has it.

  • Scoped credentials

    Secrets live in the gateway, not in prompts or client configs. Each agent gets exactly the tools it needs.

  • Skills

    Package a repeatable job such as a CRM lookup or a weekly report as a skill and reuse it across agents.

  • Works with external clients

    Claude Desktop, Cursor, and any MCP-compatible client connect with one URL, so your team uses the same tools you give your agents.

  • Self-extending

    When a connection is missing, an agent can build it. New upstreams go through the same gateway and the same access rules.

  • Visible

    Every run shows which tools the agent used and what came back, so you know who used what.

EU hosting and self-hosting

Hosted in the EU. Or on your infrastructure.

Run the gateway on our managed European infrastructure or inside your own network, next to the systems it connects to.

Discuss your deployment
Managed by you

Your infrastructure

Install the gateway in your own data center or private cloud so internal tools never have to be exposed to the internet.

  • On-premises or private cloud
  • Direct access to internal systems
  • Your security and compliance policies
Questions, answered

Before you connect.

What is an MCP gateway?

A single MCP endpoint that aggregates many tool servers. Clients connect to the gateway instead of to every tool, and the gateway handles credentials and access.

Which tools can I connect?

Any MCP-compatible server, from published integrations like HubSpot, GitHub, Postgres, Teams, and Slack to servers your own team runs.

Can I use it outside of zwrm agents?

Yes. Claude Desktop, Cursor, and other MCP clients connect with one URL and a token and get the tools you grant them.

How is access controlled?

Per consumer. Each agent or client is granted a set of tools; credentials for the upstreams stay inside the gateway and are never handed to the client.

What are skills?

Reusable instructions plus tools for a specific job, such as a CRM lookup or a weekly report. Define a skill once and attach it to any agent.

Can I see which tools were used?

Yes. Each run lists the tools the agent called and their results, next to the rest of your platform activity in the dashboard.

Connect once, use everywhere

Put your tools behind one endpoint.

Set up the gateway in minutes, or talk with us about internal systems and access policies.