Private beta · access by requestUnified Integration Platform

Connect your app to everything, through one gateway.

AppConnectHQ brings OAuth flows, connection credentials, and the Model Context Protocol together behind one consistent interface. We are inviting a limited number of private-beta users.

Early access is reviewed individually while the product is in beta.

960 catalogued integrations, with assets reviewed continuously
1Password
1Password Events API
2Chat
7shifts
A-Leads
Ably
Ably Control
Abstract
AbuseIPDB
Abyssale
Accredible Certificates
AccuLynx
AccuWeather
ActiveCampaign
ActiveTrail
Adafruit IO

Showing a small selection. Browse the full catalogue.

Platform

One platform.
Every integration primitive.

Four tightly‑integrated services that replace the dozen homegrown systems most teams cobble together.

OAuth Aggregation

One unified API for every OAuth flow — authorization code, refresh tokens, PKCE, and client credentials. We handle the dance; you ship.

Configured provider connections

Credential Vault

Credential handling and connection flows are centralized so teams can build against a consistent interface.

Private-beta capability

MCP Server Gateway

Explore a unified Model Context Protocol server for connected services during the private beta.

JSON‑RPC · streaming

Credential handling

Credentials are encrypted before storage in the current application implementation. Confirm your requirements with the team during beta access.

Private-beta implementation detail
Developer experience

Three lines.
One shared connection layer.

The same SDK shape is used across supported providers. Switch from Slack to Notion to another supported service by changing one string, then tell us what your product needs during the private beta.

Consistent provider interfaceExplore connected services through one SDK shape during the private beta.
Provider-aware connectionsEvaluate OAuth and other connection flows against the supported catalogue.
Feedback-led iterationPrivate-beta access helps us validate the workflows your product needs.
Read the full quickstart
1
Illustrative response
{ provider: "github", status: "connected", scopes: [...] }
MCP server

One MCP endpoint.
Every connected tool.

POST /api/mcp exposes every tool a user has connected as a single Streamable HTTP JSON‑RPC endpoint — point any MCP client at it and get typed tools for every service that user is authorized on.

Claude Code & CursorDrop a static bearer token into your MCP client config — no OAuth dance required for local dev tools.
Claude.ai & ChatGPT connectorsA full OAuth 2.1 authorization server — PKCE, dynamic client registration, consent, and token revocation — for hosted connector flows.
Spec‑compliant transportStreamable HTTP with MCP protocol‑version negotiation (2025‑06‑18, 2025‑03‑26, 2024‑11‑05) and session‑scoped Mcp‑Session‑Id.
Read the MCP connect guide
.mcp.json
{
  "mcpServers": {
    "appconnect": {
      "type": "http",
      "url": "<PRODUCTION_API_ORIGIN>/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_ACCESS_TOKEN>"
      }
    }
  }
}
Method 1 · static bearer token
Works today for Claude Code, Cursor, and any config‑based MCP client.
SDKs

Typed clients,
plus adapters for the frameworks you already use.

The TypeScript and Python SDKs share one shape: list a user’s tools, adapt them for your framework, execute whatever the model calls. Adapters ship for OpenAI, Anthropic, the Vercel AI SDK, and LangChain in TypeScript — OpenAI, Anthropic, and LangChain in Python.

TypeScript
import {
  AppConnectClient,
  toOpenAITools,
  executeOpenAIToolCall,
} from "appconnect";

const tools = await toOpenAITools({ client, accessToken });
const reply = await openai.chat.completions.create({
  model: "gpt-4o-mini",
  messages,
  tools,
});

for (const call of reply.choices[0].message.tool_calls ?? []) {
  messages.push(
    await executeOpenAIToolCall({ client, accessToken }, call),
  );
}
Python
from appconnect import AppConnectClient
from appconnect.framework.openai import (
    to_openai_tools,
    execute_openai_tool_call,
)

tools = await to_openai_tools(client, access_token)
reply = openai_client.chat.completions.create(
    model="gpt-4o-mini", messages=messages, tools=tools,
)

for call in reply.choices[0].message.tool_calls or []:
    messages.append(
        await execute_openai_tool_call(client, access_token, call)
    )
Browse the API referenceBrowse the per‑service tools reference
Triggers

Real‑time events,
not just request/response.

Subscribe your agents to what happens next — GitHub commits, Shopify orders, Google Calendar changes — delivered as signed webhooks with automatic retries.

GitHub webhooks

Subscribe to push, issue, and pull‑request events on any repo a connected user grants access to. AppConnect registers the GitHub webhook for you and verifies every payload's HMAC signature before delivery.

new_commit · new_issue · new_pull_request

Shopify webhooks

Order and product events land the moment they happen — HMAC‑verified against the store's OAuth app secret, with big‑integer‑safe parsing for Shopify's numeric order and product ids.

order_created · order_updated · product_created

Google Calendar polling

For providers with no native webhook, a scheduled poller diffs calendar state every five minutes and classifies created, updated, and cancelled events with cursor‑based idempotency.

5‑minute interval · cursor tracking

Reliable delivery pipeline

Every event is queued and retried with backoff on failure, with an atomic claim so the same delivery is never dispatched twice. Manage subscriptions and inspect delivery history from the SDK or the admin dashboard.

atomic claim · retry + backoff · SDK‑managed
How it works

From handshake to API call,
in three steps.

01

Connect

Embed the AppConnectHQ SDK and point it at any of our supported providers. Your users authenticate through the provider's real OAuth screen — we never see their password.

02

Store

Connection data is handled by the current application backend. Storage and retention details are being documented with private-beta users as supported flows are evaluated.

03

Call

Use the typed SDK or explore the MCP server for supported connected services. Request private-beta access to evaluate the operations your product needs.

Use cases

Built for the way teams
build software now.

Discuss your use case
AIgithub.readslack.sendnotion.writestripe.charge

Give agents controlled access to connected services.

Explore connected services as typed MCP tools. Your agent gets the capability while users authorize the connection.

AI Agents
your-saas.com/integrationsGSNLH

Prototype integration features with a shared layer.

Evaluate native Slack, GitHub, or Notion experiences without starting a separate connection service for each provider.

SaaS Products
connectedconnectedconnectedconnectedconnectedconnected

Explore automations across connected services.

Evaluate a shared connection workflow for the services your team uses, with private-beta support while the product is being prepared.

Internal Tools
Early feedback

What we are hearing in customer conversations.

Early customer conversations have highlighted the value of having one place to reason about connected services and agent access.
Identity withheld
Paraphrased customer feedback; identity withheld by request.
Frequently asked

Questions, answered.

The Model Context Protocol is an open standard for exposing tools and data to AI agents. AppConnectHQ is exploring a unified MCP experience for connected services during the private beta.
AppConnectHQ is intended to give teams one place to explore common connection flows instead of rebuilding each integration separately. The private beta is where we are validating the product with early users.
The current application encrypts credentials before storage. Ask the team about the implementation and fit for your use case during private-beta onboarding; no certification or compliance claim is implied.
The catalogue is generated from the current repository service definitions. Browse the integration directory for the current entries, and request private-beta access if you need a specific service.
No. AppConnectHQ is currently a private beta, so pricing and plan availability are not being published. Request access to discuss your use case.
Some backend paths have rate-limit handling, but behavior depends on the endpoint and integration. Private-beta users can discuss the behavior relevant to their workflow.
Ready when you are

Explore your connection layer.
With AppConnectHQ.

AppConnectHQ is currently a private beta. Request access to discuss your use case and learn what is available today.