Toolport for Teams

Share your team's MCP servers without sharing keys.

Give every teammate the same approved MCP servers across Claude, Cursor, Codex, and 18 more AI agents. Choose the stack once; each person adds their own credentials locally. Free for 5 people, no card.

No account yet? Continuing creates one. Sign in with Google, GitHub, or email. Evaluating against edge portals? Toolport vs Cloudflare MCP portals.

From click to shared stack

Know exactly what happens next.

Start in the browser. Connect the desktop app when you are ready.

  1. 1
    Create your account and team

    Use Google, GitHub, or an email magic link. No separate registration form.

  2. 2
    Choose what your team shares

    Start with a curated stack or add the MCP servers you already use.

  3. 3
    Invite people when you are ready

    Teammates connect locally, so their credentials never pass through the dashboard.

The Toolport for Teams dashboard: a shared MCP server set, team members with admin and member roles, and tokens saved across the team

Your team's shared server set, your members, and the tokens you're all saving, in one dashboard.

One shared server set

Define your team's MCP servers once. Every member's Toolport syncs the same set, non-destructively, right alongside their own.

Keys never leave the machine

Only the server set syncs, never a secret. Each member authenticates locally and keys stay in their OS keychain. No central credential vault to breach.

Central governance

Per-server access, per-tool allow-lists, and a tighten-only safety policy members cannot loosen. Apply receipts show which clients actually enforced the policy. Servers on a private or local network are refused so a shared config cannot become a path into internal systems.

Exportable audit trail

Usage and cost as CSV, org audit events, and opt-in per-call export (tool, time, duration, ok, args hash; never args or results). Free keeps 14 days; Team keeps full history.

Up to 91% fewer tokens, at scale

The same lazy-discovery token cut, multiplied across every agent and developer on your team. Context stays flat as you add servers.

Hosted or self-hosted

Start on our cloud in a minute, no infrastructure to run. Or self-host on your own network for full data sovereignty when compliance demands it. Same product, your call.

What admins see

The controls are visible, not buried in config.

The shared server set, members, roles, and usage all sit in one place, nothing to dig for in config.

Toolport for Teams server access controls showing shared MCP servers and governance status
Govern shared servers Admins decide which servers belong in the shared set and who can use them.
Toolport for Teams members screen showing roles and invited teammates
Invite and manage members Bring teammates in with roles, invites, and a clear view of who has access.
Toolport for Teams usage dashboard showing team activity, saved tokens, and estimated cost saved
Track usage and savings See tool activity, token savings, and audit-ready usage without asking each developer.
Why not just commit a config file?

Because a file in your repo can't enforce anything.

Checking an mcp.json into the repo shares a list. Toolport shares a setup you can actually enforce, with secrets kept out of the repo and a safety policy applied on every machine. That's the part that matters once more than one person is involved.

Enforced, not a suggestion

A checked-in file is advice a teammate can ignore or edit. Toolport applies the shared set and the safety policy on every member's machine, tighten-only, and a member can't silently loosen it.

Secretless onboarding

A new hire gets the whole server set without anyone passing a key around. Each person authenticates locally; secrets never land in a repo, a PR, or a shared vault.

Policy at runtime

A file can't make an agent stop and ask before something destructive, or quarantine a tool whose definition changed under you. Toolport does that live, as calls happen.

Every agent, one set

The same set syncs to Claude, Cursor, and every other AI agent each member runs. A dotfile is per-tool and per-machine, and drifts the moment someone edits theirs.

Pricing

Free to share. Team to govern.

Start free for a small team sharing a set of servers. Move to Team when you need access control, per-tool policy, rate limits, signed webhooks, full audit, and coverage receipts. Every plan runs hosted by us or self-hosted on your own network, both are just below. How this compares to Cloudflare MCP portals →

Free

$0

For a small team sharing one set of MCP servers.

  • Up to 5 people
  • One shared MCP server set, synced to everyone
  • Each person's keys stay on their own machine
  • Safety policy: destructive-tool gate + injection screening
  • One signed security-alert webhook channel
  • Audit trail and usage, with 14 days of searchable CSV history
Create a free team Free for 5 people. It does not expire or require a card. Or self-host it
Most popular

Team

$39/ month for up to 5 people

or $390/year (2 months free). Choose annual at checkout.

Then $12/person. For teams that need to govern and control access. Everything in Free, plus:

  • Per-server access control (who can see which servers)
  • Per-tool allow-lists and deny-lists on shared servers
  • Roles: admin, billing, auditor, viewer
  • Tool-call rate limits (day/month; team, member, group, or tool)
  • Spend budgets with over-budget email alerts (showback, not a model meter)
  • Policy coverage receipts for instructions and screening policy
  • Full audit trail, opt-in per-call export, config version history
  • HMAC-signed webhooks (Slack, Discord, MS Teams, generic) + API tokens for CI
  • Dashboard TOTP two-factor authentication
Try Team features free 14 days of Team features, no card. After that you stay on Free (up to 5) unless you subscribe, we never charge a card you didn't add. Buy a self-host license Checkout here; we email a license key for the server you run.

Enterprise

Let's talk

For scale, compliance, and identity. These are roadmap capabilities we scope with you before you commit, not self-serve today. Everything in Team, plus:

  • SSO with SAML or OIDC, plus SCIM provisioning (roadmap; scoped with you)
  • Audit streaming to your SIEM (Splunk, Datadog, S3)
  • Dedicated or on-prem managed deployment
  • DPA, security review, and data-residency review
  • SLA and priority support
What your team pays
Free · up to 5 $0/mo
Team · up to 5 $39/mo
10 people $99/mo
25 people $279/mo
50 people $579/mo

Free covers up to 5 people. Team is $39/mo for up to 5, then $12/mo per person. Same price hosted or self-hosted.

The token savings across a team usually dwarf the seat price. Estimate your savings →

Hosted is the quickest start. Choose self-hosting when compliance needs data to stay on your network. The product and price are the same either way.

Self-host in ~15 minutes

Keep it all inside your own network.

For teams that need data sovereignty, the Teams server runs entirely on your infrastructure. Nothing leaves your network, keys and secrets never touch our servers, and you own the audit trail end to end. Air-gap friendly. Docker pulls the prebuilt image, no source build. You need a server you control, a domain pointed at it (ports 80 + 443 open), and a free GitHub OAuth app for sign-in.

The Docker image and default database path still use conduit-teams for backward compatibility; it is the current Toolport for Teams server.

Show the self-host setup (Docker Compose, about 15 minutes)
  1. Create a sign-in app (2 min). The dashboard signs your team in with GitHub. At github.com/settings/developersNew OAuth App, set Homepage URL to https://teams.yourco.com (your domain) and Authorization callback URL to https://teams.yourco.com/auth/github/callback. Copy the Client ID and generate a Client secret.
  2. Pull and run. Save the compose below on your box, set these as a .env beside it, then docker compose up -d (Caddy fetches HTTPS automatically): TEAMS_DOMAIN and TOOLPORT_TEAMS_BASE_URL (your https domain), TOOLPORT_TEAMS_BOOTSTRAP (openssl rand -hex 16), GITHUB_CLIENT_ID / GITHUB_CLIENT_SECRET from step 1, and leave TOOLPORT_TEAMS_LICENSE unset for the free 5-seat tier.
    # docker-compose.yml
    services:
      toolport-teams:
        image: ghcr.io/tsouth89/conduit-teams:latest
        restart: unless-stopped
        environment:
          TOOLPORT_TEAMS_BIND: 0.0.0.0:8787
          TOOLPORT_TEAMS_DB: /data/conduit-teams.db
          TOOLPORT_TEAMS_BASE_URL: ${TOOLPORT_TEAMS_BASE_URL}   # https://teams.yourco.com
          TOOLPORT_TEAMS_BOOTSTRAP: ${TOOLPORT_TEAMS_BOOTSTRAP}  # openssl rand -hex 16
          GITHUB_CLIENT_ID: ${GITHUB_CLIENT_ID}
          GITHUB_CLIENT_SECRET: ${GITHUB_CLIENT_SECRET}
          TOOLPORT_TEAMS_LICENSE: ${TOOLPORT_TEAMS_LICENSE}      # omit for the free 5-seat tier
        volumes: ["teams-data:/data"]
        expose: ["8787"]
      caddy:
        image: caddy:2
        restart: unless-stopped
        depends_on: [toolport-teams]
        ports: ["80:80", "443:443"]
        command: caddy reverse-proxy --from ${TEAMS_DOMAIN} --to toolport-teams:8787
        volumes: ["caddy-data:/data", "caddy-config:/config"]
    volumes:
      teams-data:
      caddy-data:
      caddy-config:
  3. Open your domain and set up. Visit https://teams.yourco.com, click Sign in with GitHub, then Create teamAdd serverInvite, all in the browser.
  4. Your team joins. Each teammate installs the free Toolport app, opens Teams, and pastes your server URL + their invite code. The shared servers appear; their keys stay on their machine.

Cert won't issue? It's almost always DNS not propagated yet or port 80 firewalled. Bought a Team license? Paste it as TOOLPORT_TEAMS_LICENSE and restart to turn on Team on your server. Left unset, it stays free for up to 5.

Ready to give your team one governed set of servers?

Free for up to 5 people. About 15 seconds, no card.

Create a free team
Enterprise

SSO, SCIM, and your SIEM, on your terms.

Team is self-serve and live. For SSO/SCIM, audit streaming to your SIEM, a dedicated or on-prem deployment, or a larger rollout, tell us your setup and we'll get you set up directly. Your keys still stay on each member's machine, Toolport syncs the server set, never a secret.

  • SSO & SCIM. SAML/OIDC single sign-on and automated user provisioning.
  • Audit & SIEM export. Stream signed audit events to Splunk, Datadog, or S3, with long retention.
  • Dedicated or on-prem. A managed single-tenant deployment, or run it entirely inside your network.
  • DPA, security review & SLA. The paperwork and support commitments procurement needs.

Create a free teamNo account? Continuing creates one.