Skip to main content

​
Overview

Goose is an on-machine AI agent (CLI and Desktop) from Block with MCP support.

​
Prerequisites

​
Get your MCP URL

Before configuring Goose, get your MCP URL from the StackOne dashboard:
  1. Go to Connectors in the left nav and open the connector you want to use
  2. Click Use Connector in the top right
  3. On the Use tab, click MCP Server under “Use with Agent Client”
  4. Select a linked account from the dropdown
  5. Choose HTTPS MCP as the client
  6. Copy the generated URL — it looks like: 
    https://api.stackone.com/mcp?token=<session_token>
The token encodes your account identity. No separate API key or account ID header is needed.
The token expires after one year. Regenerate it at any time using the refresh button in the MCP tile.

​
Setup Methods

Goose supports two methods: Interactive Configuration (easiest) and Manual YAML (advanced).
Run the configuration wizard: 
goose configure
1

Select 'Add Extension'

When prompted, choose “Add Extension” from the menu.
2

Choose Extension Type

Select “Remote Extension” — StackOne uses HTTP transport.
3

Name Your Extension

Enter a name: stackone (or any name you prefer).
4

Enter Server URL

Paste the URL from the dashboard:
https://api.stackone.com/mcp?token=<session_token>
5

Enable Extension

When asked if you want to enable the extension, select “Yes”.

​
Method 2: Manual YAML Configuration

Find your Goose config file:
  • Linux/Mac: ~/.config/goose/config.yaml
  • Windows: %APPDATA%\goose\config.yaml
Add the following under extensions: 
extensions:
  stackone:
    name: stackone
    type: http
    url: https://api.stackone.com/mcp?token=<session_token>
    enabled: true
    timeout: 300
Replace <session_token> with the token from the dashboard.
Add separate entries for each account:
extensions:
  salesforce:
    name: salesforce
    type: http
    url: https://api.stackone.com/mcp?token=<salesforce_session_token>
    enabled: true
    timeout: 300

  slack:
    name: slack
    type: http
    url: https://api.stackone.com/mcp?token=<slack_session_token>
    enabled: true
    timeout: 300

​
Advanced: Manual API Key Setup

If you prefer to authenticate with your API key and account ID directly: 
extensions:
  stackone:
    name: stackone
    type: http
    url: https://api.stackone.com/mcp
    enabled: true
    timeout: 300
    headers:
      Authorization: "Basic <YOUR_BASE64_TOKEN>"
      x-account-id: "<YOUR_ACCOUNT_ID>"
To generate the base64 token: 
echo -n "<stackone_api_key>:" | base64
Using environment variables: 
extensions:
  stackone:
    name: stackone
    type: http
    url: https://api.stackone.com/mcp
    enabled: true
    timeout: 300
    headers:
      Authorization: "Basic ${STACKONE_AUTH_TOKEN}"
      x-account-id: "${STACKONE_ACCOUNT_ID}"
See Authentication & Security for details.

​
Verify Installation

After configuration, start a Goose session and check available tools: 
goose session
Then ask: 
what tools do you have?
You should see StackOne operations based on your connected accounts.

​
Desktop Application

If using Goose Desktop:
  1. Open Goose Desktop
  2. Go to Settings → Extensions
  3. Your StackOne extension should appear in the list
  4. Toggle to enable/disable as needed

​
Troubleshooting

Symptoms: StackOne tools don’t appear when asked “what tools do you have?”
  1. Verify config file location: 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: goose logs
Symptoms: “401 Unauthorized” or “403 Forbidden”If using a dashboard token, regenerate it from the MCP tile in the dashboard.If using manual API key auth:
  1. Verify base64 encoding includes the trailing colon: echo -n "your_api_key:" | base64
  2. Confirm the account ID matches your linked account
  3. Check the API key is valid in StackOne Dashboard
Increase the timeout in your config:
timeout: 600  # 10 minutes
  1. Verify you have active integrations in the StackOne Dashboard
  2. Check that actions are enabled in your integration config
  3. Review StackOne Playground to see expected tools
  1. Validate YAML syntax at https://www.yamllint.com/
  2. Check indentation (use spaces, not tabs)
  3. Ensure quotes around header values
  4. Run: goose info -v to see config parsing errors

​
Next Steps

Dashboard Setup

Generate MCP configs from any connector

Authentication Guide

Configure authentication and security

Goose Documentation

Learn more about Goose capabilities

Explore All Tools

See all available operations in StackOne Playground