Skip to content

Expose Username Parameter to getBuildId MCP Tool #184

@dflor003

Description

@dflor003

Description

Right now, the getBuildId tool has two parameters: project name and build name. From looking at the code here, it looks like the underlying code supports passing in a username, but it probably gets the username from the MCP tool setup. At my org, we have some tests imported into browserstack by a service account, so they all show up under the service account's username.

In a Claude CLI session earlier, I wasn't able to use the getBuildId MCP tool to get any of the builds I was trying to look up because they were under the service account's username. I switched to manually using the browserstack REST API and passed the service account's username and everything worked. Any chance you guys can expose the username as a parameter to the getBuildId tool to make this easier in that scenario?

Steps to Reproduce

  1. Add some test runs under a service account or other user
  2. Setup the browserstack MCP tool as a different user
  3. Prompt an AI agent with something like:
    Find me the latest test results in the project `SomeProject` with build name `SomeBuildName` under the user `SomeUserName`.

Expected:

Finds the test results correctly.

Actual:

Gets a 404 not found error

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions