Are you an LLM? Read llms.txt for a summary of the docs, or llms-full.txt for the full context.
Skip to content

How It Works

You talk to your AI assistant. Your AI assistant talks to your tools. That's it.

The Flow

You → AI Assistant → Gateway MCP Server → Linear, Notion, Slack

When you say "Find my Linear issues about the auth bug", your AI:

  1. Asks Gateway what's available
  2. Finds the right action (search Linear issues)
  3. Runs it and gets results
  4. Gives you a clean answer

You never interact with Gateway directly — your AI handles it all behind the scenes.

What Can It Do?

Gateway gives your AI access to 71 actions across three providers:

ProviderActionsWhat Your AI Can Do
Linear24Search issues, create/update issues, manage sprints, add comments, assign work, track projects, initiatives
Notion21Search pages, read/write docs, query databases, manage blocks, create databases
Slack26Send messages, search conversations, manage channels, react to messages, read threads, DMs

Your AI discovers these automatically — you just describe what you want in plain language.

Authentication

Gateway supports two ways to connect:

  • Automatic (Cursor, Claude Code) — Your editor handles login for you. Just click install and authorize when prompted.
  • Token-based (any other tool) — Copy a config snippet from your dashboard. Works with any MCP-compatible client.

Both give you the same access. Your connected providers, your data, your permissions.

Procedures

Beyond one-off actions, Gateway supports procedures — structured documents that encode repeatable processes like expense reports, onboarding, and approvals. Your AI reads the procedure and executes it step by step.

Procedures can wait for approvals, handle timeouts, and hand off between people — even when you're offline. See Procedures for more.

Privacy

  • Interactive use — Gateway uses your OAuth tokens to call provider APIs on your behalf. You only see data you already have access to in each tool.
  • Procedure runs — In-flight data is stored in Gateway's internal database, not in your Notion or Slack. Only you, assigned people, and procedure admins can see your run data.
  • Autonomous execution — When Gateway acts on its own (approvals, timeouts), it uses a bot identity and sandboxed access. It can only touch what the procedure explicitly declares.
  • Tokens are stored securely and never shared
  • No data is indexed or stored beyond what's needed for the request