connecta

One connection between your agent and the services you choose.

Connecta puts the services your agent needs behind one connection. It uses Model Context Protocol (MCP), a standard that lets AI apps use tools. You run Connecta and choose what each agent may access.

flowchart LR
    Agents["Agent apps and people"] --> Pools
    subgraph Connecta["Your Connecta server"]
        Pools["Pools<br/>which tools each caller can use"] --> Checks["Access checks<br/>reads · changes · secrets"]
    end
    Checks --> Stripe
    Checks --> Google["Google Workspace"]
    Checks --> Other["Other services"]

A tool is an action, such as finding a ticket or updating a record. The agent can call one action directly or combine several in a short program inside Connecta. The program can return a small answer instead of every record. Connecta supplies the service credentials, so the agent doesn't need them.

What you can connect

Maintained connections: Breeze ChMS, Church Community Builder, Cloudflare, GitHub, Gmail, Google Docs, Google Drive, Google Forms, Google Sheets, Google Slides, Granola, Overflow, Planning Center, QuickBooks Online, Stripe, Tithe.ly, and Vercel.

Maintained API providers pair reviewed vendor contracts with tools built by Connecta. See the API sources and tool inventory for each provider's named workflows and reviewed API tools.

You can also connect another hosted MCP tool server through remoteMcp(), which discovers the server's live tool catalog, or describe an API Connecta should call.

Related MCP server: mcp-router

What it protects

Read-only protection and single-attempt writes depend on truthful tool labels. The AI app using Connecta decides when to ask for approval; a writable pool can write unattended. Safety and trust explains these boundaries and their limits.

Try it in three steps

You'll need somewhere to run Connecta and permission to connect the service accounts you choose. Creating the project is the start of setup; account connections and access rules still need configuring.

1. Create a deployment. Start with the Node template:

   npx @zackbart/connecta init my-connecta
   cd my-connecta
   npm install

2. Choose services and access. Your operator—the person or team running Connecta—can use a coding assistant as a setup agent. Give that assistant the operator documentation. It configures services, enables the credential vault, connects accounts, and starts the server with the access rules you choose.

3. Connect your AI app. This app is the MCP client: it uses Connecta's tools on your agent's behalf. Give it the pool address and authentication method supplied by your operator. A person in a single pool can use the plain /mcp address; their sign-in selects the pool. Connecting agents explains what to ask for; the deployment guide has runnable steps.

flowchart LR
    Create["1 · Create"] --> Configure["2 · Choose services + access"] --> Connect["3 · Connect your AI app"]

The package is @zackbart/connecta (npm install @zackbart/connecta). Run it on Node, in Docker, or on Cloudflare Workers. The deployment guide covers each.

Read a little more

Upgrading? Follow the upgrade guide. Pre-0.29 storage and OAuth layouts must first migrate on 0.37.1; see the required bridge upgrade. Breaking changes are expected before 1.0. See the changelog and security policy.