Introduction
Get started with Gatana Gateway
The Gatana Gateway is a collection of MCP Servers. Each server provides a set of tools. When you add a server to your gateway, its tools will become available to the Gatana users.
- See Model Context Protocol Official Website for more information.
Each server in Gatana has a Slug. This is a technical identifier (a-z and hyphens only). Keep it short; it will be
prepended to the tool names which commonly have a limit of 64 characters. This is done to keep each tool name unique.
Gatana formats the tool name so: ${slug}_${toolname}.
The tools of each server are cached and are automatically refreshed periodically every couple of hours. To refresh the tool cache manually, you can navigate to the server in Gatana App and click on the Refesh button under the Tools section. Tools
Adding a Server
In the header right click on Add Server. You have several choices:
- Popular servers: a catalog of well-known services (GitHub, Linear, Notion, Slack, Google Workspace, and more). One click installs the vendor's official server and, where the vendor allows it, sets up the OAuth sign-in automatically. A few vendors, such as Google Workspace, require an OAuth client of your own; the server's settings show what is left to fill in.
- By transport: configure any server yourself. The choices are grouped by where the server runs; see Server Types below.
- Search MCP registries: search the official MCP registry by name, and the Glama directory.
- Built-in: tools Gatana provides itself, with nothing to host.
You can also ask the AI assistant to set a server up for you.
Server Types
Gatana supports three different categories of servers:
- Standard MCP (remote HTTP servers and executable apps)
- FaaS-style Runnable Code
- Public OpenAPI / Swagger endpoints
This only affects how Gatana talks to one particular server. Its tools and capabilities will always be available through the Gatana Gateway using the remote MCP protocol.
Access
Gatana supports flexible access configurations. A server can grant access based on individual users or teams. The following roles are available:
- Member: able to see and call the tools
- Maintainer: able to modify the server configuration
- Admin: modify permissions and delete the server
Organization Base Permissions
Each user's base permissions is controlled by the organization-wide Base Permissions setting. It provides least privileges each user has organization-wise. To only grant access on a per-server basis the "Base Permissions" should be set to "No permissions".
See Permissions and Roles for more information.