Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

vystrcild
Copy link
Collaborator

Added server.json and update CI pipeline.
Based on this tutorial: https://github.com/modelcontextprotocol/registry/blob/main/docs/guides/publishing/publish-server.md

@MichalKalita
Copy link
Contributor

We should prefer the remote streamable HTTP version.
There is a much bigger potential that many users will connect to the existing API instead of installing this source code and running it locally. Only remote MCP will work on mobile devices.

@MQ37
Copy link
Contributor

MQ37 commented Sep 18, 2025

We should prefer the remote streamable HTTP version. There is a much bigger potential that many users will connect to the existing API instead of installing this source code and running it locally. Only remote MCP will work on mobile devices.

Agree, lets do remote one. I will change that.

@MQ37
Copy link
Contributor

MQ37 commented Sep 18, 2025

@MichalKalita I also added the remote stremable http server, I guess we can also keep the local stdio one.

{
"name": "Authorization",
"description": "Apify API token for authentication with Apify platform services. For example 'Bearer <apify-api-token>'",
"is_required": true,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should define OAuth and not require an Apify token

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point, but I dont know how to explicitly configure OAuth there - they only mention headers in the MD docs on how to contribute.

Copy link
Collaborator

@jirispilka jirispilka left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess the release.yaml is in some temporary state? Let's review it again when it is ready.

"url": "https://github.com/apify/apify-mcp-server",
"source": "github"
},
"version": "0.4.10",
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We will need to update this value too? Is there some simple way?
If not, let's push it now and we will automate it later

"registry_type": "npm",
"registry_base_url": "https://registry.npmjs.org",
"identifier": "@apify/actors-mcp-server",
"version": "0.4.10",
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Again, we need to update version (can be automated later)

@MQ37
Copy link
Contributor

MQ37 commented Sep 18, 2025

I guess the release.yaml is in some temporary state? Let's review it again when it is ready.

the version bump for server.json is already automated in release cicd. Yes, it is in debug state since the public is still faling on the mcpName is missing on the package.json even though the mcpName was in the latest release when I tried (currently there is newer release that does not have that) - will debug tomorrow.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants