Skip to content

fix: dockerhub init unauth server start and tool list #227

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Aug 20, 2025
Merged

fix: dockerhub init unauth server start and tool list #227

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
cbc5d8c
log token for debugging
MQ37 Aug 20, 2025
90d7d89
try to delete dummy token
MQ37 Aug 20, 2025
069247e
finalize
MQ37 Aug 20, 2025
5847f3d
lint
MQ37 Aug 20, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions src/apify-client.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,6 +24,17 @@ export function getApifyAPIBaseUrl(): string {

export class ApifyClient extends _ApifyClient {
constructor(options: ApifyClientOptions) {
/**
* In order to publish to DockerHub, we need to run their build task to validate our MCP server.
* This was failing since we were sending this dummy token to Apify in order to build the Actor tools.
* So if we encounter this dummy value, we remove it to use Apify client as unauthenticated, which is sufficient
* for server start and listing of tools.
*/
if (options.token?.toLowerCase() === 'your-apify-token') {
// eslint-disable-next-line no-param-reassign
delete options.token;
}

super({
...options,
baseUrl: getApifyAPIBaseUrl(),
Expand Down