Connectors

Last validated:

Connectors let Aperture reach external MCP servers and HTTP APIs through a single authenticated gateway. Aperture handles credentials, request proxying, and access control, so agents do not need separate service connections. Connectors complement providers: providers route model requests, and connectors route tool calls and API requests.

The MCP servers and HTTP APIs you connect to are third-party services. When Aperture forwards requests and credentials to them, their handling of that data is governed by your agreement with each service, not your agreement with Tailscale.

Set up connectors

Add a connector, grant access, and verify the connection in Aperture.

Configure a verified connector such as Salesforce or Slack from Aperture's Add connector menu, supplying OAuth client credentials when required.

Connect Aperture to an MCP server that requires authentication using a shared bearer token or OAuth 2.0 client credentials.

Configure Aperture to proxy requests to an upstream REST API with automatic credential injection.

Connect Aperture to an external service that requires individual user consent using the OAuth 2.0 authorization code flow.

Configure Aperture grants to control which connector capabilities users can access, including MCP tools, resources, templates, and HTTP proxy access.

Label Aperture connectors and grant access by label so a single grant covers every connector in a group instead of naming each connector ID.

Set up built-in connectors to provision tailnet nodes and run commands over Tailscale SSH.

Use connectors

Authorize a connector, discover and call its tools, and reconnect when access expires.

Understand connectors

Understand how Aperture connectors give agents tools and APIs, how they relate to providers, and how authentication and access control apply.

Aperture has five kinds of tool integration. They differ by who runs the tool and who can reach it, which determines their configuration, grants, and failure behavior.

Understand the `aperture` system connector, conditional tool availability, HTTP connector discovery, and grant-based access.

Reference

Use the catalog to choose a provider, the authentication topic to configure upstream credentials, and the reference for connector fields and protocol behavior.

Find public verified connector providers, defaults, and prerequisites, plus the configured built-in connectors and Aperture system connector.

Choose connector upstream authentication, look up all six authentication types, and understand per-user OAuth callbacks, consent, and token lifecycle.

Reference for Aperture connector configuration fields, labels, access statuses, MCP and HTTP protocol behavior, grants, legacy MCP server registration, and migration.