Real tools for your agents — without handing over the keys.

1Connector gives every coding agent one governed way to discover and call approved services — 100 providers and 499 structured actions out of the box — while credentials stay with the organization, never with the agent.

118

provider definitions in the catalog

100

available by default

499

structured actions

Agents wired directly to services fail in predictable ways.

Token sprawl

Every agent × every service = another credential to issue, leak, and forget to rotate.

All-or-nothing access

Tool access is either wide open or switched off. Nothing in between, nothing reviewable.

Shadow MCP

Engineers register MCP servers locally with personal credentials — outside anyone's view or policy.

No paper trail

When an agent touches production, there's no record of who allowed it, what ran, or what came back.

One gateway closes all four.

Connect once. Govern everywhere.

Browse supported providers, connect them with OAuth or org-managed credentials, and let every agent in the organization use them through one gateway. Deactivate or revoke a connection once — no reconfiguring every developer's setup.

1Connector integrations: connect providers via OAuth or org-managed credentials

Bring your own MCP servers.

Register any HTTPS MCP server, discover its tools, and put them under the same governance as built-in actions. No special cases.

1Connector permissions: grant members specific actions on specific resources

Permissions that match how teams actually work.

Grant members specific actions on specific resources. Scope agent tokens to explicit actions and lifetimes. Before anything executes, 1Connector checks who is acting, with which token, requesting what action, on which resource.

Approvals, where the risk is.

Routine actions run without friction. Sensitive or policy-flagged actions pause before the request reaches the provider, and wait for review. After approval, permissions are re-checked — an old approval never bypasses a newer permission change.

1Connector approvals: sensitive actions pause for review before reaching the provider
1Connector runs: status, input/output summaries, errors and full event history for every run

Every run on the record.

Status, input/output summaries, errors, and full event history for every run. Organization-level audit events, viewable and exportable.

Provider coverage and connection methods vary. A provider appearing in the catalog doesn't mean every capability has been production-certified — the catalog and its hardening grow continuously.

Four steps from setup to a governed tool call.

01

Admins connect services and custom MCP servers.

02

Members get only the actions and resources they need.

03

Developers install the plugin and hand agents an org-scoped token.

04

Agents discover and call approved tools. Routine actions run; sensitive ones wait for approval.

Frequently asked questions

Do agents ever see raw service credentials?
No. Agents call actions through the gateway; credentials stay managed by the organization.
What happens when someone leaves or a token leaks?
Rotate, deactivate, or delete agent tokens centrally; revoke a connection once and it's gone for every agent.
Is this just an MCP gateway?
It's the connector layer of a control plane. Every governed call here shows up as evidence in 1Signal, and feeds the practices you publish through 1Knowledge.

1Connector is where the loop starts.

See what your agents actually did → 1Signal — every session captured, explained, and traceable.
Turn what worked into governed skills 1Knowledge coming soon

Stop wiring credentials into agents.

Be among the first to give your agents one governed path to real tools. 1Connector is launching soon.