Skip to main content The #1 agentic semantic tool search: 91.6% first-try accuracy on S1 Search Bench Explore Tool Discovery

goose MCP

Turn goose into an enterprise agent

Let your employees delegate real work to goose across all their apps, under their own identity and permissions.

DrataGPLocalyzeFlipMindtoolsScreenloop

Get goose to work.
Not just chat.

One connection to StackOne, and goose gets scoped access to every app your employees use, to act on their behalf.

Connect

Make every system AI-ready

Give your AI access to 450+ managed MCP servers and 28,000+ tested tools. No auth code to write, no API maintenance.

Secure

Keep AI under control

Enforce identity-based access, screen every response for prompt injection, and audit every action.

Optimize

Trust what AI delivers

Keep your agent sharp with lean tool loading, boost reliability with the Falcon execution engine, and enhance its context with pre-synced data.

Roll out MCP tools to every goose user.
Set up and onboarding in minutes.

One-time setup for IT. Self-serve for everyone else.

IT Admin

One-time setup, no per-user wiring.

The URL carries no access on its own, so it is safe to publish in an internal wiki or commit with your dotfiles. There is no cloud project to configure and no client secret to hand out. goose setup guide →

Which MCP server will you
connect goose to?

Connect to the StackOne MCP gateway once and give your employees' agents instant access to 450+ pre-built SaaS connectors and 28,000+ MCP tools.

Need another connector? Build one with the AI Connector Builder

What will your employees
delegate to goose?

From HR and recruiting to sales and support, goose completes work across any app you connect.

HR & People Ops

> List this month's Workday work anniversaries and draft a personalized celebration message for each.

UKG ReadyWorkday (Rest and Soap)FactorialHiBobOracle Fusion HCMHumaansSAP SuccessFactorsClockify
Recruiting

> Compare Greenhouse interview feedback across stages and flag candidates trending toward an offer.

JobAdderVincereSmartRecruitersAshbyManatalFactorialHiBobSAP SuccessFactors
Sales & CRM

> Analyze Salesforce deals stuck 30+ days and draft a re-engagement email for each owner.

SalesforceKeapZoho CRMPipedriveFreshsalesJustCallPardotAircall
Support

> Cluster yesterday's Zendesk tickets by theme and surface the top 3 trending issues.

IntercomSurveyMonkeyFreshserviceServiceNowFreshdeskGorgiasDiscourseDixa

Not everyone on goose?
Your integration layer stays the same.

The same setup works across Coding agents like Codex, Gemini CLI, and every other MCP client.

Explore MCP clients

Frequently Asked Questions

You connect goose to StackOne over MCP through the setup wizard: run goose configure, choose Add ExtensionRemote Extension (Streamable HTTP), name it stackone, and paste https://mcp.stackone.com/mcp. A browser tab opens — sign in, pick your project, choose accounts, and authorize. Same entry can go straight into config.yaml. Setup guide.
The goose config file holds it: ~/.config/goose/config.yaml on Mac/Linux, %APPDATA%\goose\config.yaml on Windows, under the extensions key with type: streamable_http and the gateway address as url. goose configure writes that block for you. It's a plain YAML file, so IT can commit or push it with your dotfiles — it holds only the gateway address, never credentials.
You do not need a paid plan to use MCP servers with goose. It is free and open source, developed under the Linux Foundation, and reads remote extensions from your own config file — no edition to upgrade, no admin console. You bring your own model provider, billed separately.
You don't configure each app in StackOne yourself. IT connects the apps and sets the action ceiling for your project. In the consent screen the browser tab opens, you pick which of those accounts and actions goose gets, narrowing further if you want. Rerun the flow to change it.
Once connected, goose can run whatever actions you granted, across 450+ live connectors and 28,000+ tested actions — CRM, HRIS, ATS, ticketing, finance, and more. Tools go live as soon as you authorize: start a session with goose session and ask what tools it has. Browse the actions in the directory above.
Your app credentials — Zendesk, Salesforce, and the rest — live server-side in StackOne and never reach goose or your machine. The gateway address in your config file carries no access on its own, so it's safe to commit with your dotfiles. There's no client ID or secret to fill in; goose registers itself during the OAuth handshake.
IT can roll out the StackOne MCP connector to a whole team in one pass: connect the apps once, and distribute a single extensions block for config.yaml instead of briefing people individually. Each person still signs in, picks their own accounts and actions, and authorizes — so nobody exceeds the ceiling IT set.
Skip connecting goose to StackOne when any of these is true:
  • An existing first-party MCP server already covers your apps
  • You use only a handful of actions across a few apps
  • You don't need multi-tenancy or per-action scoping
  • Prompt injection isn't a concern
  • Nobody can complete a browser consent step — a CI job or headless server, for instance

Connect All Your Apps to goose.

One URL, 450+ pre-built SaaS connectors. Set up in minutes.