Skip to main content
Goose connects to remote servers over streamable HTTP as an extension.

Before you start

  • A StackOne project you are a member of.
  • A connector profile in the project for each provider the client should reach, with the actions you want exposed enabled.
  • (Optional) A linked account for each provider. Accounts can also be linked during the consent flow.

Connect StackOne

Interactive configuration

Run the configuration wizard:
1

Add an extension

When prompted, choose Add Extension from the menu.
2

Choose extension type

Select Remote Extension (Streamable HTTP).
3

Name your extension

Enter stackone (or any name you prefer).
4

Enter the server URL

Paste https://mcp.stackone.com/mcp.
5

Sign in and authorize

  1. Sign in to StackOne. In a desktop app or code editor, this opens in your browser.
  2. If StackOne asks for a project, pick yours and click Continue to Accounts.
  3. Pick the work systems Goose can use (your Linked Accounts).
  4. If you see Load tools when needed, leave it on.
  5. Click Authorize.
StackOne's Select accounts screen with two Linked Accounts ticked, Load tools when needed on, and the Authorize button

Manual YAML configuration

Find your Goose config file:
  • Linux or Mac: ~/.config/goose/config.yaml
  • Windows: %APPDATA%\goose\config.yaml
Add the following under extensions:
Goose prompts for authorization the first time the extension loads. If it does not, use a token app URL instead. One grant covers every account you approved, so a single stackone extension is usually all you need.

Verify installation

Start a Goose session and check available tools:
Then ask:
You should see StackOne operations for the accounts you approved.

Desktop application

If using Goose Desktop, open Settings → Extensions. Your StackOne extension appears in the list, where you can toggle it on and off.

Troubleshooting

Symptoms: StackOne tools don’t appear when you ask “Which of my Linked Accounts can you reach through StackOne?”
  1. Verify config file location with goose info -v.
  2. Check YAML syntax (indentation matters).
  3. Ensure the extension is marked enabled: true.
  4. Restart Goose after config changes.
  5. Check logs with goose logs.
Symptoms: “401 Unauthorized” or “403 Forbidden”If you connected with OAuth, re-run goose configure to authorize again, and check the grant still exists under Connected Apps in the StackOne dashboard.If using a token app URL, regenerate it under Connected Apps → Token apps in the StackOne dashboard.
Increase the timeout in your config:
  1. Confirm you approved at least one account on the consent screen.
  2. Check that actions are enabled on the account’s Connector Profile.
  3. Review StackOne Playground to see expected tools.
  1. Validate YAML syntax at yamllint.com.
  2. Check indentation (use spaces, not tabs).
  3. Run goose info -v to see config parsing errors.
Goose reaches only the Linked Accounts you approved when you connected. To add one you link later, or one someone shares with you afterwards:
1

Open Connected Apps

In the StackOne dashboard, go to Connected Apps.
2

Edit the connection

  1. Open the ⋮ menu on the row for Goose and select Edit tool access.
  2. Select the Linked Account.
  3. Click Save changes.
To review or revoke the connection, use the same ⋮ menu in Connected Apps.