Remote MCP · OAuth 2.1 · Streamable HTTP

Your AI. Your operation. One connection.

Connect ChatGPT, Claude, Cursor, or another MCP-compatible client to StackPass. Give the AI you already trust a governed way to read context and execute approved work across the customer lifecycle.

Connect in minutes ↘Inspect live endpoint ↗
Live endpoint verified179 tools advertised2 auth paths
Live public discovery reviewed August 18, 2026. Granted tools depend on workspace authority and connected services.
ChatGPTCustom appClaudeConnectorCursorMCP tools
GOVERNED CONTROL PLANEStackPass MCP
CONNECTED
CRMContacts · dealsTalkVoice · inboxDeliverJobs · tasksGrowSites · campaignsMoneyDocs · paymentsTrustScopes · audit

The AI-controllable business operating system

Not another chatbot. An operating interface.

StackPass is built to be controlled through MCP—not merely searched.

One governed connection can expose approved tools across CRM, conversations, appointments, voice, sites, documents, payments, workspaces, automation, and analytics. Your AI client still honors its own plan limits and approval rules; StackPass enforces the authenticated workspace and scopes.

Exact connection path

URL in. Approve. Get to work.

OAuth is the recommended path. Use a workspace API key only when your client requires header-based authentication, and never expose that key in a public prompt or repository.

  1. 01

    Open your AI client

    Find Apps, Connectors, Tools, or MCP settings and choose to add a custom remote server.

  2. 02

    Name it StackPass

    Use the canonical Streamable HTTP endpoint below. No local server or SDK is required.

    https://api.aeosos.com/mcp
  3. 03

    Authorize the workspace

    Choose OAuth, sign in, select the intended StackPass workspace, and approve only the access you need.

  4. 04

    Scan the tools

    Let the client list the currently granted tools. In ChatGPT, use Scan Tools; in Claude, click Connect; in Cursor, enable the server under Tools & MCP.

  5. 05

    Bootstrap first

    Start with: Call agent_bootstrap first and summarize the workspace, available tools, and approval boundaries.

Choose your interface

ChatGPT. Claude. Cursor. Your call.

The same StackPass operating record, reached from the AI environment your team already uses.

01

ChatGPT

Enable developer mode, create a custom app, enter the endpoint, choose OAuth, Scan Tools, then test the draft app in a new chat.

Official setup details ↗Full write-capable MCP is plan-dependent and currently beta.
02

Claude

Open Customize → Connectors, add a custom connector, paste the endpoint, then click Connect to complete OAuth and enable it in a conversation.

Official setup details ↗Organization owners may need to add the connector first.
03

Cursor

Add a remote server in Tools & MCP or place the configuration below in your global or project mcp.json, then authorize and enable its tools.

Official setup details ↗Use the latest client for current Streamable HTTP support.

Header-based fallback

Copy the config. Keep the key private.

For clients that accept explicit HTTP headers, create a workspace-scoped StackPass API key and replace the placeholder locally.

  • Use the smallest practical workspace scope.
  • Keep write tools disabled until the read path is verified.
  • Rotate or revoke the key when access changes.
stackpass-mcp.jsonSTREAMABLE HTTP
{
  "mcpServers": {
    "stackpass": {
      "type": "http",
      "url": "https://api.aeosos.com/mcp",
      "headers": {
        "Authorization": "Bearer <your StackPass workspace API key>"
      }
    }
  }
}

Connection answers

Bring your AI. Keep the controls.

StackPass gives compatible AI clients a governed operating surface while workspace identity, scopes, provider state, and approvals stay explicit.

What is StackPass MCP?

StackPass MCP is a remote Model Context Protocol connection that lets compatible AI clients read approved business context and execute granted StackPass tools inside an authenticated workspace.

Which AI clients can connect to StackPass?

StackPass publishes setup paths for ChatGPT, Claude, Cursor, and other clients that support remote Streamable HTTP MCP servers.

How does StackPass MCP authenticate?

OAuth 2.1 with PKCE is the recommended path. Workspace-scoped API keys can be used as an Authorization Bearer header when a client requires header-based authentication.

What should I do immediately after connecting?

List the tools granted to the workspace and call agent_bootstrap first so the AI can summarize available context, tools, and approval boundaries before taking action.

The interface is now optional

Run the operation from the AI you already trust.

Connect one approved workspace, verify the tool surface, and move from questions to governed execution.

Open StackPass settings ↗View server card