MCP: surface default workspace + set_default_cloud_workspace tip in list_cloud_workspaces and get_default_cloud_context

Open Beginner friendly
  • Is something wrong?
#1,370 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
62/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
python
Domain
api

Research direction

Start in the MCP tool handlers for list_cloud_workspaces and get_default_cloud_context, then in CloudClient.get_default_context_for_user(), which currently adds the set_default_cloud_workspace hint only when no default is stored. Read CloudClient.resolve_default_workspace_id() to see how the stored defaultWorkspaceId is read. Done when list_cloud_workspaces marks the default workspace when one is set, and both tools always include the set_default_cloud_workspace tip.

Written by the indexing model from the issue text.

Description

airbyte-mcp-beta enhancement

Summary

Agents keep hitting AirbyteMissingWorkspaceContextError, and they never save a default workspace. In the last 24h, 4 users (8 failures) hit it on list_cloud_connections, list_cloud_connectors, show_workspace_sync_status, and list_custom_source_definitions. Each recovered by calling get_default_cloud_context and/or list_cloud_workspaces and then passing workspace_id explicitly. None called set_default_cloud_workspace, and none has called it in the last 60 days. 3 of the 4 hit the same error again later (4 min, 8 min, 4.5h).

Setting a default would have prevented the repeats: when workspace_id is omitted, CloudClient.resolve_default_workspace_id() reads the user's stored defaultWorkspaceId live.

Requested by @aaronsteers.

Current behavior (release-candidate/v1)

  • get_default_cloud_context: CloudClient.get_default_context_for_user() adds a set_default_cloud_workspace hint to discovery_hints only when the user has no stored default.
  • list_cloud_workspaces: never mentions set_default_cloud_workspace, and doesn't mark which workspace is the default.

Requested changes

  1. list_cloud_workspaces names or annotates the user's default workspace when one is set.
  2. Both list_cloud_workspaces and get_default_cloud_context always include a short tip that set_default_cloud_workspace can set the default, or change it if the current one is wrong. This applies whether or not a default is already set.

Out of scope: the AirbyteMissingWorkspaceContextError guidance itself.

Dominant language
Python
Stars
342
Forks
82
Avg merge
1d 7h
Merged PRs (30d)
74

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from airbytehq/PyAirbyte

All issues in airbytehq/PyAirbyte

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.