Skip to main content
These pages are step-by-step references that take a single path from start to a working result. Each one uses concrete values you can copy and tells you what you should see at every step. Follow them in order to set up the core of MCP Manager: adding a server, packaging it in a gateway, governing it, observing it, and driving it from code. For task-oriented guidance you adapt to your own situation, see the deployment guides; for the concepts behind what you’re doing, start with the Introduction.
You’ll need an MCP Manager workspace. A few steps (adding servers, creating gateways, inviting people) depend on capabilities your role may or may not have — each tutorial flags the capability it needs near the top. If a button or page in a tutorial isn’t visible to you, that’s the capability talking, not a wrong turn.

Start here

The two first-win lessons — one for an administrator standing the system up, one for a person who was handed a gateway URL.

Your first governed tool call

Add the public docs MCP server, put it behind a gateway, connect your AI client, call a tool, and watch the request land in your audit log. About five minutes.

Connect your AI client to a gateway

Add a gateway URL to Claude, Claude Code, Cursor, or VS Code, authorize, and start using its tools. About five minutes.

Connect your own servers

Bring a server that isn’t on the public internet under the same governance.

Connect a workstation MCP server

Run an MCP server on your own machine and connect it through an encrypted tunnel — nothing exposed to the internet, no firewall changes, fully logged. About ten minutes.

Run it for your team

Go from a single connection to a governed, observable rollout: scope tools to a team, add a guardrail, and learn to read what happened.

Build a team gateway

Create a team, build a gateway for it, trim its tools, invite a teammate, and confirm they see only that gateway.

Add your first gateway rule

Add a rule that detects sensitive data, run it in a non-blocking alert configuration, trigger it, and see it fire.

Redact PII with Presidio

Add a Presidio rule on the response leg, fail it closed, and watch an email get replaced with a typed tag.

Trace a call in your logs

Follow one tool call through the logs and answer who did what, when, and through which tool.

Build with it

Drive a gateway from code, with no browser in the loop.

Run a headless agent

Create a token-based host, generate an API access token, and call a tool over HTTP with a bearer token — fully attributed and logged.

Build a custom rule engine

Write a webhook that redacts emails, register it, test it, attach it to a rule, and see its verdict in your logs.

Further reading

Your first governed tool call

The best place to start if you’re new to MCP Manager.

Introduction

What MCP Manager is and the problem it solves.

MCP Gateways

How a gateway aggregates servers, brokers identity, and applies rules.

Gateway Deployment Strategies

Topologies for rolling gateways out across an organization.