connecta

One connection between your agent and the services you choose.

Connecta puts your MCP servers and HTTP APIs behind one endpoint that you run yourself. Connect your agent once; decide in code who can reach what.

How it works

flowchart LR
    Agent["Your agent"] <-->|"One connection<br/>six small tools"| Connecta

    subgraph Connecta["Your Connecta deployment"]
        Sandbox["Sandbox<br/>runs the agent's short programs"]
        Keys["Credentials<br/>stay on the server"]
    end

    Connecta <--> Work["Linear, GitHub, Notion"]
    Connecta <--> Business["Stripe, RevenueCat, Mixpanel"]
    Connecta <--> Yours["Any remote MCP server<br/>or HTTP API"]

    style Connecta fill:#e0e7ff,stroke:#4338ca,color:#1e1b4b,stroke-width:2px

The agent doesn't load every service's tools into the conversation. It writes a short program that gathers, joins, and trims results inside Connecta, so only the answer comes back.

flowchart LR
    Q["Which open issues affect<br/>our biggest customers?"] --> P["Program in Connecta"]
    P --> I["Open issues"]
    P --> C["Customer records"]
    I --> J["Match, filter, group"]
    C --> J
    J --> A["Short answer"]

    style J fill:#e0e7ff,stroke:#4338ca,color:#1e1b4b,stroke-width:2px
    style A fill:#dcfce7,stroke:#15803d,color:#14532d

Related MCP server: mcp-store

What you can connect

Maintained connections: Basecamp, Breeze ChMS, Church Community Builder, Cloudflare, GitHub, Gmail, Google Docs, Google Drive, Google Forms, Google Sheets, Google Slides, Infisical, Linear, Mixpanel, Notion, Overflow, Planning Center, RevenueCat, Stripe, Tithe.ly, Vercel, and Wispr Flow. Plus any remote MCP server or HTTP API you describe.

Who can use it

Two kinds of caller, kept apart on purpose:

People come in two roles:

• Maintainers run the deployment: they reach every tool, connect shared accounts, manage agent tokens, and read activity.

• Pool members reach only the pools they're listed in.

Pools

A pool is a named set of tools plus a list of who may use it. Each pool has its own address, and every caller sees exactly that pool's tools.

flowchart LR
    Maint["Maintainer<br/>(signs in)"] --> Main["/mcp<br/>every tool"]
    Bob["Bob<br/>(signs in)"] --> Team["/mcp/team<br/>CRM + tickets"]
    Bot["assistant agent<br/>(token)"] --> AgentPool["/agent/assistant<br/>CRM + tickets"]

    style Main fill:#e0e7ff,stroke:#4338ca,color:#1e1b4b
    style Team fill:#dcfce7,stroke:#15803d,color:#14532d
    style AgentPool fill:#fef3c7,stroke:#b45309,color:#78350f

• Not a member? You get the same "not found" as a pool that doesn't exist.

• In two pools? You use two addresses. Pools never merge.

• Maintainers aren't in any pool automatically.

• Agent tokens are refused at people addresses, and sign-ins are ignored at agent addresses. Behind Cloudflare Access, an agent sends only its token.

• With no sign-in and no agent tokens configured, a deployment is open: anyone who can reach it gets everything, and Connecta warns at startup. The shipped templates always configure agent tokens, so they are never open.

Whose account a connection uses

Reaching a tool and which downstream account it runs as are separate questions.

flowchart TB
    Call["An allowed call"] --> Kind{"Connection type"}
    Kind -->|"Shared (default)"| Dep["The deployment's account<br/>connected once by a maintainer"]
    Kind -->|"Personal"| Own["The caller's own account<br/>each person connects their own"]
    Kind -->|"Google Workspace"| WS["The signed-in person's account<br/>for an agent, the pool's owner<br/>or one fixed shared account"]

    style Dep fill:#e0e7ff,stroke:#4338ca,color:#1e1b4b
    style Own fill:#dcfce7,stroke:#15803d,color:#14532d
    style WS fill:#fef3c7,stroke:#b45309,color:#78350f

Agents have no account of their own, so personal connections never appear for them. An agent reaches a person's account only through a shared connection set up for that person and placed in that person's pool.

One agent, many people

An assistant that talks to several people keeps one token and one connection. Its harness, not the model, picks the pool each turn:

flowchart LR
    Group["Group chat or<br/>scheduled job"] --> Base["/agent/assistant<br/>shared tools only"]
    Alice["One-on-one<br/>with Alice"] --> PA["/agent/assistant-alice<br/>shared tools + Alice's accounts"]
    Bob["One-on-one<br/>with Bob"] --> PB["/agent/assistant-bob<br/>shared tools + Bob's accounts"]

    style Base fill:#e0e7ff,stroke:#4338ca,color:#1e1b4b
    style PA fill:#dcfce7,stroke:#15803d,color:#14532d
    style PB fill:#dcfce7,stroke:#15803d,color:#14532d

Anyone else in a person's pool would act as that person, so those pools hold only the agent. Organizing an agent's pools has the full layout.

Who can do what

Reads and writes

Every endpoint is writable or read-only, and you choose explicitly.

flowchart TB
    Change["Your agent wants to change something"] --> Choice{"Is this endpoint<br/>read-only?"}
    Choice -->|"Yes"| Refused["Refused; nothing is sent"]
    Choice -->|"No"| Host["Your agent's host handles approval"]
    Host --> Access["Connecta checks the caller's access"]
    Access --> Services["The connected service receives the change"]

    style Host fill:#fef3c7,stroke:#b45309,color:#78350f
    style Access fill:#e0e7ff,stroke:#4338ca,color:#1e1b4b,stroke-width:2px

On a read-only endpoint, search hides write tools and every write is refused. Neither setting grants access to more services.

Operator UI (optional)

A web page for seeing connections, tools, access, and configuration. Changes to integrations and access rules still happen in deployment code.

Where it runs

Both serve the same agent tools.

Getting started

Give your agent the agent documentation and ask it to set up Connecta with the integrations you want, where to run it, and who should have access.

Upgrading? Point your agent at the upgrade guidance.

Status

Built for its author's deployments first and published openly. Breaking changes are expected before 1.0. See the changelog and security policy.

Principles · Decision records · Planned work (a plan is not a shipped feature)