durin
Sign up
Getting started

MCP basics

Learn what an MCP client, server, and gateway do.

The three parts

MCP stands for Model Context Protocol. It lets AI clients discover tools and request their execution.

  • Client: the application proposing a tool call.
  • Server: the system exposing tools and their input schemas.
  • Gateway: Durin checks access before routing a call to an upstream system.

Discovery is not permission

A listed tool describes a capability. Executing it still requires current identity, connection, resource, credential, and policy checks.

Frequently asked questions

Which clients can connect?

Use a client version that supports Durin’s remote HTTP transport and authorization flow. Claude Code, Cursor, and Codex have remote MCP configuration paths; compatibility and syntax depend on the installed version.

Is a Durin endpoint a provider credential?

No. It identifies your gateway entry point. Authenticate separately as its owner; provider credentials stay within their connection boundary.

Try Durin with your MCP workflow.

Create an account to connect a client, route governed MCP requests, and review decisions with your admins.

Create an account