Skip to main content

​
Overview

A connector is more than a list of tools. Customers need the assistant to understand what can be done, ask for the right confirmation, and show useful context at the right moment. Satsuma packages your existing product capabilities into connector surfaces that work across modern AI assistants.

​
Core Surfaces

MCP Server

The backend surface that exposes product actions, resources, prompts, and metadata to compatible AI clients.

MCP App

The interactive UI surface for previews, account state, confirmations, results, and follow-up actions.

Channel Adapters

Compatibility work for ChatGPT, Claude, Gemini, Perplexity, Copilot, and private MCP clients.

Brand Layer

Copy, visuals, legal language, and interaction details that make the connector feel native to your product.

​
How We Choose Tools

Satsuma starts from customer intent, not from a raw API inventory. A good connector action should be:
  • Useful: it completes something customers already ask assistants to help with
  • Scoped: it has clear permission requirements and bounded inputs
  • Explainable: the assistant can describe what will happen before it happens
  • Recoverable: failures produce helpful next steps rather than dead ends
  • Observable: the action emits enough context for debugging and analytics

​
App UI Moments

Some workflows should stay conversational. Others need a user-visible surface. Satsuma designs UI moments for:
  • Account connection and connection health
  • Review screens before sensitive actions
  • Rich previews where structured data matters
  • Progress states for long-running actions
  • Result summaries and next-best actions
  • Error recovery and support escalation

​
Channel Readiness

Different assistant environments have different review processes, capabilities, and UX constraints. Satsuma helps adapt the same underlying connector to each channel without making your product team rebuild the core implementation each time.
Endpoint-level API reference is not included in this docs site yet. During implementation, Satsuma works from your existing API documentation and creates connector-facing tools only after the launch scope is agreed.