> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gatetrix.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Supported protocols

> Understand Access's REST, GraphQL, JMAP, MCP, PostgreSQL, and authentication support.

These protocols describe how Access reaches connected services. They are separate
from the [interfaces](/access/interfaces) an agent or person uses to reach Access.

| Protocol | Supported use | Key limits |
| - | - | - |
| **HTTP / REST** | Saved operations with fixed methods and paths, constrained inputs, and request mappings. | Provider compatibility depends on its endpoint and authentication requirements. POST, PUT, and PATCH require write capability; DELETE requires destructive capability. |
| **GraphQL** | Saved query or mutation documents; callers provide constrained variables. | No subscriptions. Provider semantics still determine whether filters restrict the intended resources. |
| **JMAP** | Supported mail operations, account/mailbox discovery, and explicitly scoped mail access. | Not every JMAP extension is supported. Sending is account-wide authority and cannot guarantee mailbox-only sending. |
| **MCP** | Tools over local stdio or Streamable HTTP, with discovery and owner review. | The upstream connector does not expose legacy HTTP+SSE, resources, prompts, sampling, elicitation, or task-required tools. |
| **PostgreSQL** | Scoped database operations or an explicitly configured raw SQL mode. | Raw SQL relies on the database role for its scope; it is not constrained by an Access table allowlist. |

Filesystem access and Apple Calendar/Reminders are also supported as
[connection types](/access/connection-types), using local mechanisms rather than
one of these remote API protocols.

## Authentication

REST, GraphQL, and JMAP connections support no authentication, bearer tokens,
custom headers, and supported OAuth authorization-code flows. OAuth supports
PKCE, refresh tokens, and public or confidential clients. Provider registration
and owner consent may be required.

Remote MCP supports no authentication, bearer tokens, or supported OAuth.
PostgreSQL uses database credentials and verified TLS by default.
Credentials are entered in Access and stored in macOS Keychain.

OAuth support is not universal. For example, device-code and client-credentials
flows need additional implementation. Ask the agent to check installed support
before promising that a provider will connect.

## For agents

Read `configuration_connection_capabilities` for the installed builders,
authentication shapes, schemas, and templates. Follow the provider's official
documentation, then verify the smallest useful scope. A familiar protocol name
does not prove that every operation or authentication flow is supported.

Need another protocol or provider capability? Tell us the service and intended
use at [hello@gatetrix.ai](mailto:hello@gatetrix.ai?subject=Access%20protocol%20request).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.