Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://block.github.io/goose/docs/getting-started/using-extensions below:

Using Extensions | codename goose

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.

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:

• Developer: Provides a set of general development tools that are useful for software development.
• Computer Controller: Provides general computer control tools for webscraping, file caching, and automations.
• Memory: Teaches Goose to remember your preferences as you use it.
• Tutorial: Provides interactive tutorials for learning about Goose.

• Goose Desktop
• Goose CLI

1. Click the button in the top-left to open the sidebar.
2. Click the Extensions button on the sidebar.
3. Under Extensions, you can toggle the built-in extensions on or off.

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

To navigate through available extensions:

1. Run the following command:

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 (SSE): Connect to a remote system via SSE (Server-Sent Events).
   • Remote Extension (Streaming HTTP): Connect to a remote system via Streaming HTTP
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 
│        
◇  Please set the timeout for this tool (in secs):
│  300
│ 
└  Enabled jetbrains extension    

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.

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.

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

You can install any MCP server as a Goose extension.

• Goose Desktop
• Goose CLI

1. Click the button in the top-left to open the sidebar.
2. Click the Extensions button on the sidebar.
3. Under Extensions, click Add custom extension.
4. On the Add custom extension modal, enter the necessary details
   • If adding an environment variable, click Add button to the right of the variable
   • The Timeout field lets you set how long Goose should wait for a tool call from this extension to complete
5. Click Add button

• Type: Standard IO
• ID: kgm-mcp (set this to whatever you want)
• Name: Knowledge Graph Memory (set this to whatever you want)
• Description: maps and stores complex relationships between concepts (set this to whatever you want)
• Command: npx -y @modelcontextprotocol/server-memory

1. Run the following command:

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 (SSE): Connect to a remote system via SSE (Server-Sent Events).
   • Remote Extension (Streaming HTTP): Connect to a remote system via Streaming HTTP

3. Follow the prompts based on the type of extension you selected.

• Node
• Python
• Java

┌   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
│
◇  Please set the timeout for this tool (in secs):
│  300
│
◆  Would you like to add environment variables?
│  No 
│
└  Added Knowledge Graph Memory extension

┌   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?
│  Wikipedia Reader
│
◇  What command should be run?
│  uvx mcp-wiki
│
◇  Please set the timeout for this tool (in secs):
│  300
│
◆  Would you like to add environment variables?
│  No
│
└  Added Wikipedia Reader extension

Note: Java and Kotlin extensions are only support on Linux and macOS

┌   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?
│  Spring Data Explorer
│
◇  What command should be run?
│  jbang -Dspring.profiles.active=dev org.example:spring-data-mcp:1.0.0
│
◇  Please set the timeout for this tool (in secs):
│  300
│
◆  Would you like to add environment variables?
│  Yes
│
◇  Environment variable name:
│  SPRING_DATASOURCE_URL
│
◇  Environment variable value:
│  jdbc:postgresql://localhost:5432/mydb
│
◇  Add another environment variable?
│  No
│
└  Added Spring Data Explorer extension

Extensions can be installed using Goose's deep link protocol. The URL format varies based on the extension type:

• StandardIO
• Server-Sent Events
• Streaming HTTP

goose://extension?cmd=<command>&arg=<argument>&id=<id>&name=<name>&description=<description>

Required parameters:

• cmd: The base command to run, one of jbang, npx, uvx, goosed, or docker
• arg: (cmd only) Command arguments (can be repeated for multiple arguments: &arg=...&arg=...)
• timeout: Maximum time (in seconds) to wait for extension responses
• id: Unique identifier for the extension
• name: Display name for the extension
• description: Brief description of the extension's functionality

A command like npx -y @modelcontextprotocol/server-github would be represented as:

goose://extension?cmd=npx&arg=-y&arg=%40modelcontextprotocol/server-github&timeout=<timeout>&id=<id>&name=<name>&description=<description>

Note that each parameter to the npx command is passed as a separate arg parameter in the deeplink.

goose://extension?url=<remote-sse-url>&id=<id>&name=<name>&description=<description>

Parameters:

• url: The URL of the remote SSE server
• timeout: Maximum time (in seconds) to wait for extension responses
• id: Unique identifier for the extension
• name: Display name for the extension
• description: Brief description of the extension's functionality

For example, a deeplink for a URL like http://localhost:8080/sse would look like this when URL-encoded:

goose://extension?url=http%3A%2F%2Flocalhost%3A8080%2Fsse&timeout=<timeout>&id=<id>&name=<name>&description=<description>>

goose://extension?url=<remote-streamable-http-url>&type=streamable_http&id=<id>&name=<n>&description=<description>

Parameters:

• url: The URL of the remote Streaming HTTP server
• type: Must be set to streamable_http to specify the protocol type
• timeout: Maximum time (in seconds) to wait for extension responses
• id: Unique identifier for the extension
• name: Display name for the extension
• description: Brief description of the extension's functionality

For example, a deeplink for a URL like https://example.com/streamable would look like this when URL-encoded:

goose://extension?url=https%3A%2F%2Fexample.com%2Fstreamable&type=streamable_http&timeout=<timeout>&id=<id>&name=<n>&description=<description>

note

All parameters in the deeplink must be URL-encoded. For example, spaces should be replaced with %20, and @ should be replaced with %40.

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

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

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

• Goose Desktop
• Goose CLI

1. Click the button in the top-left to open the sidebar.
2. Click the Extensions button on the sidebar.
3. Use the toggle switch next to each extension to enable or disable it.

1. Run the following command to open up Goose's configurations:

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 
└   

The Smart Extension Recommendation system in Goose automatically identifies and suggests relevant extensions based on your tasks and needs. This section explains how to use this feature effectively and understand its capabilities and limitations.

When you request a task, Goose checks its enabled extensions and their tools to determine if it can fulfill the request. If not, it suggests or enables additional extensions as needed. You can also request specific extensions by name.

warning

Any extensions enabled dynamically are only enabled for the current session. To keep extensions enabled between sessions, see Enabling/Disabling Extensions.

Goose automatically detects when an extension is needed based on your task requirements. Here's an example of how Goose identifies and enables a needed extension during a conversation:

• Goose Desktop
• Goose CLI

Find all orders with pending status from our production database

I'll help you search for available extensions that might help us interact with PostgreSQL databases.

🔍 Search Available Extensions
└─ Output ▼

 I see there's a PostgreSQL extension available. Let me enable it so we can query your database.

🔧 Manage Extensions
└─ action           enable
   extension_name   postgresql

The extension 'postgresql' has been installed successfully

Great! Now I can help you query the database...

Find all orders with pending status from our production database

I apologize, but I notice that I don't currently have access to your database. Let me search if there are any database-related extensions available.
─── search_available_extensions | platform ──────────────────────────

I see that there is a "postgresql" extension available. Let me enable it so I can help you query your database.
─── enable_extension | platform ──────────────────────────
extension_name: postgresql


■  Goose would like to enable the following extension, do you approve?
| ● Yes, for this session 
| ○ No

Goose responds to explicit requests for extensions, allowing users to manually enable specific tools they need. Here's an example of how Goose handles a direct request to enable an extension:

• Goose Desktop
• Goose CLI

I'll help enable the PostgreSQL extension for you.

🔧 Manage Extensions
└─ action           enable
   extension_name   postgresql

The extension 'postgresql' has been installed successfully

The PostgreSQL extension is now ready to use. What would you like to do with it?

Use the PostgreSQL extension

I'll help enable the PostgreSQL extension for you.
─── enable_extension | platform ──────────────────────────
extension_name: postgresql


■  Goose would like to enable the following extension, do you approve?
| ● Yes, for this session 
| ○ No

Goose relies on extension properties to determine how to handle an extension. You can edit these properties if you want to change the extension's display settings and behavior, such as the name, timeout, or environment variables.

• Goose Desktop
• Config file

1. Click the button in the top-left to open the sidebar.
2. Click the Extensions button on the sidebar.
3. Under Extensions, click the button on the extension you'd like to edit.
4. In the dialog that appears, edit the extension's properties as needed.
5. Click Save Changes.

1. Navigate to the Goose configuration file. For example, navigate to ~/.config/goose/config.yaml on macOS.
2. Edit the extension properties as needed and save your changes.

You can remove installed extensions.

• Goose Desktop
• Config file

1. Click the button in the top-left to open the sidebar.
2. Click the Extensions button on the sidebar.
3. Under Extensions, click the button on the extension you'd like to remove.
4. In the dialog that appears, click Remove Extension.

info

To remove an extension, you must disable it first.

1. Run the following command to open up Goose's configurations:

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

You can start a tailored Goose session with specific extensions directly from the CLI.

Notes

• The extension will not be installed. It will only be enabled for the current session.
• There's no need to do this if you already have the extensions enabled.

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

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

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

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

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

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.

To enable a remote extension over SSE while starting a session, run the following command:

goose session --with-remote-extension "{extension URL}" --with-remote-extension "{another extension URL}"

For example, to start a session with a remote extension over SSE running on localhost on port 8080, you'd run:

goose session --with-remote-extension "http://localhost:8080/sse"

To enable a remote extension over Streaming HTTP while starting a session, run the following command:

goose session --with-streamable-http-extension "{extension URL}" --with-streamable-http-extension "{another extension URL}"

For example, to start a session with a Streaming HTTP extension, you'd run:

goose session --with-streamable-http-extension "https://example.com/streamable"

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.

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4