Optiak Docs
Connections

Connect MCP Servers

Prepare provider identities and choose which MCP tools applications can use.

Connect an MCP server by authorizing an identity or supplying credentials. Applications assigned to a tool setup share that identity, so prepare it with only the access the selected tools need.

Required role

Organization Admin

Applies to

Tool calls
Organization Admins connect MCP servers, select the tools each setup exposes, and choose which applications can use it.

How connections work

A tool setup stores one connection and the tools selected from one server. Applications assigned to the setup share its identity. The provider still controls which resources that identity can access.

Selecting tools limits which operations the setup exposes; it does not narrow the resources those operations can reach. Limit permissions at the provider, then expose only the operations applications need.

In the table below, you can see how the different MCP providers that Optiak supports handle authentication, the identity shared by applications, the access granted, and the admin involvement required.

ProviderAuthenticationIdentity shared by applicationsAccessAdmin involvement
Atlassian
  • Rovo service-account API key
Atlassian service accountJira and Confluence scopes plus account permissionsOrganization admin enables API-token auth and creates the account
BigQuery
  • Service-account JSON key
Google Cloud service accountQuery project, datasets, and jobs allowed by IAMProject admin grants roles and enables the API
Databricks
  • OAuth client credentials
  • Service-principal PAT
Databricks service principalWorkspace, server, and resource permissionsAdmin creates and assigns the principal
DeepWiki
  • None
Shared public servicePublic GitHub repository documentationNot required
Exa
  • OAuth
  • API key
Connected Exa teamTeam plan, rate limits, and selected toolsExa team access
GitHub
  • Fine-grained PAT
Token ownerRead-only tools; selected private repositories plus public repositories, subject to token permissionsOrganization approval may be required by policy
Linear
  • OAuth
Linear appRead-only issues, projects, and documents in the workspaceWorkspace app approval may be required
Notion
  • OAuth
Authorized Notion memberPages and connected sources the member can accessWorkspace policy may require approval
Slack
  • User OAuth token
Authorizing Slack memberToken scopes plus member permissionsWorkspace app approval may be required
Custom MCP server
  • OAuth
  • API key/token
  • No authentication
Identity or credential accepted by the serverResources and operations allowed by the serverDepends on the server

Before you connect

  • Use an Organization Admin account to create and manage tool setups.
  • Choose an organization-owned identity where the provider supports one. Grant only the resource access and permissions the selected tools need.
  • Check whether the provider or your organization requires an administrator to approve an app, create an account, enable authentication, or issue a credential.
  • Declare the provider's confirmed processing region in Data residency, or choose Unknown if you cannot confirm it. With a regional organization policy active, Optiak checks this declaration when resolving tools for each request and makes servers with a different or unknown region unavailable; changes take effect on the next request. The label is a declaration, not a guarantee of provider routing. See Data Governance.
  • Have the provider details ready, such as the workspace or project, server URL, resource ID, API key, or OAuth secret.

See Supported MCPs for detailed instructions on how to connect to the different MCP servers supported by Optiak. Use a Custom MCP server to connect to a private MCP server or a public MCP server without a pre-integration.

After you connect

  1. In the setup form, select Discover tools and choose only the operations this setup needs.
  2. Set the setup Scope to the organization, selected projects, or selected applications that should be allowed to use it. Keep the setup active and save.
  3. In each application, open Configuration → Tools, enable the assigned setup, and select the tools the application needs. An application can use only tools exposed by the setup and enabled for that application.
  4. Verify the result with the application's key by following the tool access check.

To test the tools available to an application, follow the optional MCP check in the Quickstart. For MCP client requirements, see Tools.

Supported MCPs

Pre-integrated MCP servers

Custom MCP server

Troubleshooting

  • Authentication failed: reconnect the OAuth connection, or update the API key or header settings, then select Rediscover tools.
  • Connection required or Connection unavailable: edit the setup and connect or reconnect its provider account or credential.
  • Could not reach the server: check that the server URL is correct and publicly reachable over HTTPS, and that its TLS certificate and firewall allow access.
  • Server timed out: check that the endpoint is reachable and responds within 30 seconds, then rediscover tools.
  • Server rate limit reached: wait a moment before rediscovering tools.
  • A tool is missing or unavailable: confirm that the server exposes it and the connected identity can access it. Check that the setup is active, its scope includes the application, the application enables the setup and tool, and the external connection is ready. Reconnect credentials or refresh provider access if needed.
Copyright © 2026