Skip to main content

Goose Integration

Connect MCPBundles MCP servers to Goose to give the AI assistant access to external tools and APIs.

Requirements​

  • Goose installed (CLI or app)
  • An MCP server enabled in your MCPBundles dashboard
  • Credentials connected for the providers on that MCP server

Time to complete: 2-3 minutes

Goose runs in the terminal, so the fastest way to connect is via the MCPBundles CLI:

pip install mcpbundles
mcpbundles init

This automatically discovers your MCP servers and writes the Goose MCP config. No manual JSON editing needed.

Option B: Manual Config Setup​

1. Get your MCP server URL​

  1. Log in to MCPBundles Dashboard
  2. Open the MCP server you want to connect
  3. Scroll to the "Quick Setup" section (only visible when the MCP server is operational)
  4. Copy the MCP Server URL

2. Locate Goose Config File​

Goose stores MCP configuration in a JSON file.

Typical locations:

  • macOS/Linux: ~/.goose/config.json or ~/.config/goose/config.json
  • Windows: %APPDATA%\Goose\config.json

If the file doesn't exist, create it.

3. Add MCP server configuration​

Edit the config file:

{
  "mcpServers": {
    "your-bundle-name": {
      "transport": "http",
      "url": "https://mcp.mcpbundles.com/bundle/YOUR-BUNDLE-ID"
    }
  }
}

Replace:

  • your-bundle-name — Short MCP server name key (e.g., marketing)
  • https://mcp.mcpbundles.com/bundle/YOUR-BUNDLE-ID — Your actual MCPBundles MCP server URL

Example with multiple MCP servers:

{
  "mcpServers": {
    "marketing": {
      "transport": "http",
      "url": "https://mcp.mcpbundles.com/bundle/abc123"
    },
    "dev-tools": {
      "transport": "http",
      "url": "https://mcp.mcpbundles.com/bundle/def456"
    }
  }
}

4. Restart Goose​

  1. Quit Goose completely
  2. Reopen it
  3. Wait 10-20 seconds for MCP to initialize

5. Verify Connection​

Ask Goose: "What tools do you have access to?"

Expected response: List of tools from your MCP server(s).

Using Tools in Goose​

Once connected, Goose can use your tools when relevant.

Example Prompts​

Data retrieval:

"Check my Smartlead campaigns and summarize the top 3 by reply rate"

CRM operations:

"Add these contacts to HubSpot:
- John Doe, john@example.com
- Jane Smith, jane@example.com"

Automation:

"List my GitHub repos, find any with open PRs, and send me a Slack message with the summary"

Goose will call the necessary tools and respond.

Troubleshooting​

"MCP server connection failed"​

Fix:

  • Check URL is correct (including https://)
  • Verify transport is set to "http"
  • Make sure the MCP server is enabled in dashboard
  • Restart Goose

Tools don't appear after adding config​

Fix:

  1. Quit Goose completely
  2. Wait 5 seconds
  3. Reopen
  4. Wait 20 seconds for MCP initialization

"Authentication required" when calling tools​

Fix:

  1. Go to Settings → Credentials
  2. Connect credentials for needed providers
  3. Try the tool again in Goose

See Provider Credentials Guide.

JSON syntax error in config file​

Common mistakes:

Missing comma:

{
  "mcpServers": {
    "marketing": { "transport": "http", "url": "..." }  // ❌ Missing comma
    "sales": { "transport": "http", "url": "..." }
  }
}

Should be:

{
  "mcpServers": {
    "marketing": { "transport": "http", "url": "..." },  // ✅ Has comma
    "sales": { "transport": "http", "url": "..." }
  }
}

Trailing comma:

{
  "mcpServers": {
    "marketing": { "transport": "http", "url": "..." },  // ❌ Trailing comma
  }
}

Fix: Use a JSON validator to check syntax.

Advanced Configuration​

Multiple MCP servers​

{
  "mcpServers": {
    "marketing": {
      "transport": "http",
      "url": "https://mcp.mcpbundles.com/bundle/abc123"
    },
    "dev": {
      "transport": "http",
      "url": "https://mcp.mcpbundles.com/bundle/def456"
    },
    "crm": {
      "transport": "http",
      "url": "https://mcp.mcpbundles.com/bundle/ghi789"
    }
  }
}

All tools from all MCP servers will be available in Goose.

With Other MCP Servers​

Goose can use MCPBundles alongside other MCP servers:

{
  "mcpServers": {
    "mcpbundles-marketing": {
      "transport": "http",
      "url": "https://mcp.mcpbundles.com/bundle/abc123"
    },
    "local-filesystem": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-filesystem", "/path/to/files"]
    }
  }
}

Configuration Details​

FieldValueNotes
transport"http"Required for MCPBundles
url"https://mcp.mcpbundles.com/..."From dashboard

Note: Both fields are required.

Next Steps​

Need Help?​