OpenViSTAI · Agents · Blockchain · Crypto
Submit a project
Menu
MCP & Tooling

Open Connector

Open Connector is an open-source TypeScript authentication gateway that connects AI agents with SaaS providers through a connector catalog and SDK, CLI, MCP, HTTP and OpenAPI interfaces. It handles provider credentials, connection scopes and inspectable Action contracts so applications can expose SaaS operations without placing provider credentials in the agent process.

Explore the practical guide ↓

Independent OpenViST project profile, based on linked sources.

Open Connector — OpenViST project profile in MCP & Tooling.
OpenViST project illustration. See the linked sources for product details.
Understand the project

Practical overview

When it fits

Use it when an AI agent needs durable, reusable access to user-connected SaaS services and the integration should remain available through more than one interface, such as MCP and HTTP or SDK.

Who it is for

  • Teams building AI agent products with access to work applications, developer tools or data systems.
  • Developers integrating SaaS Actions through MCP, SDK, CLI, HTTP or OpenAPI.
  • Organizations choosing between a hosted runtime and self-hosted infrastructure.

Documented uses

  • Connect agent products to SaaS providers through authenticated integrations.
  • Expose provider Actions to MCP-compatible agent hosts.
  • Inspect Action schemas, required scopes and execution contracts.
  • Manage connections, runtime tokens, policies and run-log visibility.
  • Run the gateway locally, on private infrastructure or through a hosted runtime.
Before you choose

Requirements & limits

The repository is public and open source under the Apache-2.0 license. The project describes hosted OOMOL, local and self-hosted deployment options, including Docker or Node.js for self-hosting.

  • Choose the SDK for application code, the oo CLI for a local-agent relay, MCP for compatible agent hosts, or HTTP/OpenAPI for custom clients.
  • Self-hosting requires managing storage and OAuth applications; the hosted option provides managed OAuth and a hosted runtime according to the repository README.
  • The documented self-hosted state options are SQLite or PostgreSQL, with local or S3-compatible transit storage.
  • The connector catalog and Action contracts can cover providers such as GitHub, Gmail, Notion, BigQuery, Google Analytics, Supabase, Airtable and Slack.

Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.

Source-based practical guide

Expose SaaS Actions through MCP

Make Open Connector Actions available to an MCP-compatible AI agent host.

Before you start

  • An Open Connector runtime, either hosted or self-hosted.
  • An MCP-capable agent host.
  • A configured provider connection and available Action in the connector catalog.

Steps

  1. Configure the provider credentials and connection in the Open Connector Dashboard.

  2. Use the runtime’s MCP interface at http://localhost:3000/mcp when working with a local runtime.

  3. Connect the MCP-capable agent host to the Open Connector MCP interface.

  4. Select and invoke the available provider Actions through the agent host.

Expected outcome

The agent host can access configured SaaS Actions through MCP.

Guide limitations

  • The supplied documentation identifies the MCP interface and configuration flow but does not document a complete provider-specific invocation example.
  • Cloudflare compatibility is identified as likely compatible; no deployment test was supplied.
Documentation 1 ↗
Evidence and transparency

Sources & review

Official repository ↗
Source record details
Source availability
Active
Sources checked
2 October 2026
Original website title
oomol-lab/open-connector · Official homepage title · retained in its source language
How we review sourcesSuggest a correction