Skip to main content

Using Extensions

Extensions are add-ons that provide a way to extend the functionality of Goose by connecting with applications and tools you already use in your workflow. These extensions can be used to add new features, access data and resources, or integrate with other systems.

Extensions are based on the Model Context Protocol (MCP), so you can connect Goose to a wide ecosystem of capabilities.

Tutorials

Check out the step-by-step tutorials for adding and using several Goose Extensions

Built-in Extensions

Out of the box, Goose is installed with a few extensions but with only the Developer extension enabled by default.

Here are the built-in extensions:

  1. Developer: provides a set of general development tools that are useful for software development.
  2. Computer Controller: provides general computer control tools for webscraping, file caching, and automations.
  3. Memory: teaches goose to remember your preferences as you use it
  4. JetBrains: provides an integration for working with JetBrains IDEs.
  5. Google Drive: provides an integration for working with Google Drive for file management and access.

Toggling Built-in Extensions

If you know the exact name of the extension you'd like to add, run:

goose mcp {name}

To navigate through available extensions:

  1. Run the following command:
goose configure
  1. Select Add Extension from the menu.
  2. Choose the type of extension you’d like to add:
    • Built-In Extension: Use an extension that comes pre-installed with Goose.
    • Command-Line Extension: Add a local command or script to run as an extension.
    • Remote Extension: Connect to a remote system via SSE (Server-Sent Events).
  3. Follow the prompts based on the type of extension you selected.

Example: Adding Built-in Extension

To select an option during configuration, hover over it and press Enter.

┌   goose-configure 

◇ What would you like to configure?
│ Add Extension

◇ What type of extension would you like to add?
│ Built-in Extension

◆ Which built-in extension would you like to enable?
│ ○ Developer Tools
│ ○ Computer Controller (controls for webscraping, file caching, and automations)
│ ○ Google Drive
│ ○ Memory
│ ● JetBrains

info

All of Goose's built-in extensions are MCP servers in their own right. If you'd like to use the MCP servers included with Goose with any other agent, you are free to do so.

Discovering Extensions

Goose provides a central directory of extensions that you can install and use.

You can also add any other MCP Server as a Goose extension, even if it's not listed in our directory.

Adding Extensions

Extensions can be installed directly via the extensions directory, CLI, or UI.

MCP Servers

You can install any MCP server as a Goose extension.

MCP Server Directory

See available servers in the MCP Server Directory.

  1. Run the following command:
goose configure
  1. Select Add Extension from the menu.

  2. Choose the type of extension you’d like to add:

    • Built-In Extension: Use an extension that comes pre-installed with Goose.
    • Command-Line Extension: Add a local command or script to run as an extension.
    • Remote Extension: Connect to a remote system via SSE (Server-Sent Events).
  3. Follow the prompts based on the type of extension you selected.

Example of adding the Knowledge Graph Memory MCP Server:

┌   goose-configure 

◇ What would you like to configure?
│ Add Extension

◇ What type of extension would you like to add?
│ Command-line Extension

◇ What would you like to call this extension?
│ Knowledge Graph Memory

◇ What command should be run?
│ npx -y @modelcontextprotocol/server-memory

◆ Would you like to add environment variables?
│ No

└ Added Knowledge Graph Memory extension

Config Entry

For advanced users, you can also directly edit the config file (~/.config/goose/config.yaml) to add, remove, or update an extension:

extensions:
fetch:
name: GitHub
cmd: npx
args: [-y @modelcontextprotocol/server-github]
enabled: true
envs: { "GITHUB_PERSONAL_ACCESS_TOKEN": "<YOUR_TOKEN>" }
type: stdio

Enabling/Disabling Extensions

You can enable or disable installed extensions based on your workflow needs.

  1. Run the following command to open up Goose's configurations:
goose configure
  1. Select Toggle Extensions from the menu.
  2. A list of already installed extensions will populate.
  3. Press the space bar to toggle the extension. Solid means enabled.

Example:

┌   goose-configure 

◇ What would you like to configure?
│ Toggle Extensions

◆ enable extensions: (use "space" to toggle and "enter" to submit)
│ ◼ developer
│ ◻ fetch

Removing Extensions

You can remove installed extensions.

info

To remove an extension, you must disable it first.

  1. Run the following command to open up Goose's configurations:
goose configure
  1. Select Remove from the menu. Disabled extensions will be listed.
  2. Arrow down to the extension you want to remove.
  3. Press the space bar to select the extension. Solid means selected.
┌   goose-configure 

◇ What would you like to configure?
│ Remove Extension

◆ Select extensions to remove (note: you can only remove disabled extensions - use "space" to toggle and "enter" to submit)
│ ◼ fetch

  1. Press Enter to save

Starting Session with Extensions

You can start a tailored Goose session with specific extensions directly from the CLI. This will add and enable the extensions, so there's no need to do this if you already have the extensions enabled.

Built-in Extensions

To enable a built-in extension while starting a session, run the following command:

goose session --with-builtin "{extension_id}"

For example, to enable the Developer and Computer Controller extensions and start a session, you'd run:

goose session --with-builtin "developer,computercontroller"

Or alternatively:

goose session --with-builtin developer --with-builtin computercontroller

External Extensions

To enable an extension while starting a session, run the following command:

goose session --with-extension "{extension command}" --with-extension "{antoher extension command}"

For example, to start a session with the Fetch extension, you'd run:

goose session --with-extension "uvx mcp-server-fetch"

Environment Variables

Some extensions require environment variables. You can include these in your command:

goose session --with-extension "VAR=value command arg1 arg2"

For example, to start a session with the GitHub extension, you'd run:

goose session --with-extension "GITHUB_PERSONAL_ACCESS_TOKEN=<YOUR_TOKEN> npx -y @modelcontextprotocol/server-github"
info

Note that you'll need Node.js installed on your system to run this command, as it uses npx.

Developing Extensions

Goose extensions are implemented with MCP, a standard protocol that allows AI models and agents to securely connect with local or remote resources. Learn how to build your own extension as an MCP server.