Goose CLI & Desktop

Overview

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

Prerequisites

Goose installed (installation guide)
StackOne API key (get one here)
StackOne account ID (find it here)
Node.js installed (for npx command)

Setup Methods

Goose supports two methods for adding MCP servers: Interactive Configuration (easiest) and Manual YAML Configuration (advanced).

Method 1: Interactive Configuration (Recommended)

Step 1: Run Configuration Wizard

Open your terminal and run:

goose configure

This starts an interactive configuration wizard.

Step 2: Add StackOne Extension

Select 'Add Extension'

When prompted, choose “Add Extension” from the menu

Choose Extension Type

Select “Remote Extension” (StackOne uses HTTP transport)

Name Your Extension

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

Enter Server URL

When prompted for the URL, enter:

https://api.stackone.com/mcp

Configure Headers

Add the required headers:Authorization:

Basic <YOUR_BASE64_TOKEN>

x-account-id:

<YOUR_ACCOUNT_ID>

Content-Type:

application/json

Accept:

application/json,text/event-stream

Enable Extension

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

Step 3: Prepare Your Base64 Token

Before running the wizard, encode your StackOne API key:

echo -n "<stackone_api_key>" | base64

Important: Include the colon (:) after your API key before encoding.

Step 4: Verify Installation

After configuration, verify Goose has picked up the StackOne tools:

goose session

Then in the Goose session, ask:

what tools do you have?

You should see StackOne operations based on your connected accounts, such as:

gong_crm_search_calls
salesforce_list_accounts
slack_send_message
And many more provider-specific operations

To see all available integrations and operations:

Browse Integrations: stackone.com/integrations
Explore Operations: app.stackone.com/actions

Method 2: Manual YAML Configuration

Step 1: Locate Config File

Find your Goose configuration file: Linux/Mac:

~/.config/goose/config.yaml

Windows:

%APPDATA%\goose\config.yaml

Step 2: Add StackOne Configuration

Edit the config file and add under extensions:

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>"
      Content-Type: "application/json"
      Accept: "application/json,text/event-stream"

Replace:

<YOUR_BASE64_TOKEN> with your base64-encoded API key
<YOUR_ACCOUNT_ID> with your StackOne account ID

Step 3: Validate Configuration

After editing, validate your configuration:

goose info -v

This should show your StackOne extension loaded successfully.

Using StackOne with Goose

Basic Usage

Start a Goose session:

goose session

Now you can ask Goose to perform StackOne operations: Example Queries:

Search recent calls in Gong

List Salesforce accounts created this month

Send a message to our team Slack channel

Get documents from Google Drive

Goose will automatically use the appropriate StackOne tools from your connected integrations to fulfill your requests.

Running Specific Extensions

To start a session with only specific extensions:

goose session --with-extension stackone

Desktop Application

If using Goose Desktop:

Open Goose Desktop application
Go to Settings → Extensions
Your StackOne extension should appear in the list
Toggle to enable/disable
Start a new session with StackOne tools available

Advanced Configuration

Multiple StackOne Accounts

To use multiple StackOne accounts (e.g., production and staging):

extensions:
  stackone-prod:
    name: stackone-prod
    type: http
    url: https://api.stackone.com/mcp
    enabled: true
    headers:
      Authorization: "Basic <PROD_BASE64_TOKEN>"
      x-account-id: "47187425466113776871"
      Content-Type: "application/json"
      Accept: "application/json,text/event-stream"

  stackone-staging:
    name: stackone-staging
    type: http
    url: https://api.stackone.com/mcp
    enabled: true
    headers:
      Authorization: "Basic <STAGING_BASE64_TOKEN>"
      x-account-id: "47275639577318980035"
      Content-Type: "application/json"
      Accept: "application/json,text/event-stream"

Environment Variables

For better security, use environment variables in your config:

extensions:
  stackone:
    name: stackone
    type: http
    url: https://api.stackone.com/mcp
    enabled: true
    headers:
      Authorization: "Basic ${STACKONE_AUTH_TOKEN}"
      x-account-id: "${STACKONE_ACCOUNT_ID}"
      Content-Type: "application/json"
      Accept: "application/json,text/event-stream"

Then set in your shell:

export STACKONE_AUTH_TOKEN="<YOUR_BASE64_TOKEN>"
export STACKONE_ACCOUNT_ID="<YOUR_ACCOUNT_ID>"

Custom Timeout

For long-running operations, increase the timeout:

extensions:
  stackone:
    timeout: 600  # 10 minutes

Example Workflows

Workflow 1: Daily Activity Report

Create a script that runs daily:

#!/bin/bash
goose session --non-interactive << EOF
Summarize activity across all our connected platforms from the last 24 hours
EOF

Workflow 2: Cross-Platform Search

goose session --non-interactive << EOF
Search for mentions of "Q1 goals" across all our productivity tools
EOF

Workflow 3: Multi-System Data Correlation

goose session << EOF
Find all tickets in our support system related to users from Salesforce
EOF

Goose will automatically use multiple StackOne tools to correlate data across your connected systems.

Troubleshooting

Extension not loading

Symptoms: StackOne tools don’t appear when asked “what tools do you have?”Solutions:

Verify config file location: goose info -v
Check YAML syntax (indentation matters!)
Ensure extension is marked enabled: true
Restart Goose after config changes
Check logs: goose logs

Authentication errors

Symptoms: “401 Unauthorized” or “403 Forbidden”Solutions:

Verify base64 encoding includes colon:
```
echo -n "your_api_key:" | base64
```
Check API key is valid in StackOne Dashboard
Confirm account ID matches your linked account

Test with cURL:

curl -X POST https://api.stackone.com/mcp \
  -H 'Authorization: Basic <TOKEN>' \
  -H 'x-account-id: <ACCOUNT_ID>' \
  -d '{"jsonrpc":"2.0","id":"1","method":"tools/list"}'

Connection timeout

Symptoms: “Connection timeout” or “Request timed out”Solutions:

Increase timeout in config: timeout: 600
Check network connectivity
Verify StackOne API status
Use longer timeout for complex operations

No tools available

Symptoms: MCP server connects but no tools appearSolutions:

Verify you have active integrations in StackOne Dashboard
Check account ID is correct
Ensure API key has proper permissions
Review StackOne Playground to see expected tools

YAML configuration errors

Symptoms: Config file won’t load or syntax errorsSolutions:

Validate YAML syntax: https://www.yamllint.com/
Check indentation (use spaces, not tabs)
Ensure quotes around header values
Verify URL has no trailing slash
Run: goose info -v to see config parsing errors

Getting Started

Applications & IDEs

SDKs & Frameworks

Support

Goose CLI & Desktop

Overview

Prerequisites

Setup Methods

Method 1: Interactive Configuration (Recommended)

Step 1: Run Configuration Wizard

Step 2: Add StackOne Extension

Step 3: Prepare Your Base64 Token

Step 4: Verify Installation

Method 2: Manual YAML Configuration

Step 1: Locate Config File

Step 2: Add StackOne Configuration

Step 3: Validate Configuration

Using StackOne with Goose

Basic Usage

Running Specific Extensions

Desktop Application

Advanced Configuration

Multiple StackOne Accounts

Environment Variables

Custom Timeout

Example Workflows

Workflow 1: Daily Activity Report

Workflow 2: Cross-Platform Search

Workflow 3: Multi-System Data Correlation

Troubleshooting

Next Steps

Explore All Tools

Goose Documentation

Build Custom Extensions

Get Support

Additional Resources

Getting Started

Applications & IDEs

SDKs & Frameworks

Support

​Overview

​Prerequisites

​Setup Methods

​Method 1: Interactive Configuration (Recommended)

​Step 1: Run Configuration Wizard

​Step 2: Add StackOne Extension

​Step 3: Prepare Your Base64 Token

​Step 4: Verify Installation

​Method 2: Manual YAML Configuration

​Step 1: Locate Config File

​Step 2: Add StackOne Configuration

​Step 3: Validate Configuration

​Using StackOne with Goose

​Basic Usage

​Running Specific Extensions

​Desktop Application

​Advanced Configuration

​Multiple StackOne Accounts

​Environment Variables

​Custom Timeout

​Example Workflows

​Workflow 1: Daily Activity Report

​Workflow 2: Cross-Platform Search

​Workflow 3: Multi-System Data Correlation

​Troubleshooting

​Next Steps

Explore All Tools

Goose Documentation

Build Custom Extensions

Get Support

​Additional Resources

Overview

Prerequisites

Setup Methods

Method 1: Interactive Configuration (Recommended)

Step 1: Run Configuration Wizard

Step 2: Add StackOne Extension

Step 3: Prepare Your Base64 Token

Step 4: Verify Installation

Method 2: Manual YAML Configuration

Step 1: Locate Config File

Step 2: Add StackOne Configuration

Step 3: Validate Configuration

Using StackOne with Goose

Basic Usage

Running Specific Extensions

Desktop Application

Advanced Configuration

Multiple StackOne Accounts

Environment Variables

Custom Timeout

Example Workflows

Workflow 1: Daily Activity Report

Workflow 2: Cross-Platform Search

Workflow 3: Multi-System Data Correlation

Troubleshooting

Next Steps

Additional Resources