fix: Change github repository links

README.md

@@ -26,7 +26,7 @@ The Apify Model Context Protocol (MCP) Server at **mcp.apify.com** instantly con
 >
 > It supports OAuth, so you can connect from clients like Claude.ai or Visual Studio Code with just the URL.
 
-![Actors-MCP-server](docs/actors-mcp-server.png)
+![Apify-MCP-server](docs/actors-mcp-server.png)
 
 ## Table of Contents
 - [🌐 Introducing the Apify MCP server](#-introducing-the-apify-mcp-server)
@@ -107,7 +107,7 @@ Check out [Apify Tester MCP Client](https://apify.com/jiri.spilka/tester-mcp-cli
 This interactive, chat-like interface provides an easy way to explore the capabilities of Apify MCP without any local setup.
 Just sign in with your Apify account and start experimenting with web scraping, data extraction, and automation tools!
 
-Or use the Anthropic Desktop extension file (dxt) for one-click installation: [Apify MCP server dxt file](https://github.com/apify/actors-mcp-server/releases/latest/download/actors-mcp-server.dxt)
+Or use the Anthropic Desktop extension file (dxt) for one-click installation: [Apify MCP server dxt file](https://github.com/apify/apify-mcp-server/releases/latest/download/apify-mcp-server.dxt)
 
 # 🛠️ Tools, resources, and prompts
 
@@ -237,9 +237,12 @@ Upon launching, the Inspector will display a URL that you can open in your brows
 
 ## 🐦 Canary PR releases
 
-Due to the current architecture where Apify MCP is split across two repositories, this one containing the core MCP logic and the private [apify-mcp-server](https://github.com/apify/apify-mcp-server) repository that handles the actual server implementation for [mcp.apify.com](https://mcp.apify.com), development can be challenging as changes need to be synchronized between both repositories.
+Apify MCP is split across two repositories: this one for core MCP logic and the private `apify-mcp-serverinternal` for the hosted server.
+Changes must be synchronized between both.
 
-You can create a canary release from your PR branch by adding the `beta` tag. This will test the code and publish the package to [pkg.pr.new](https://pkg.pr.new/) which you can then use, for example, in a staging environment to test before actually merging the changes. This way we do not need to create new NPM releases and keep the NPM versions cleaner. The workflow runs whenever you commit to a PR branch that has the `beta` tag or when you add the `beta` tag to an already existing PR. For more details check out [the workflow file](.github/workflows/pre_release.yaml).
+To create a canary release, add the `beta` tag to your PR branch.
+This publishes the package to [pkg.pr.new](https://pkg.pr.new/) for staging and testing before merging.
+See [the workflow file](.github/workflows/pre_release.yaml) for details.
 
 # 🐛 Troubleshooting (local MCP server)
 
@@ -262,7 +265,7 @@ The Actor input schema is processed to be compatible with most MCP clients while
 
 We welcome contributions to improve the Apify MCP Server! Here's how you can help:
 
-- **🐛 Report issues**: Find a bug or have a feature request? [Open an issue](https://github.com/apify/actors-mcp-server/issues).
+- **🐛 Report issues**: Find a bug or have a feature request? [Open an issue](https://github.com/apify/apify-mcp-server/issues).
 - **🔧 Submit pull requests**: Fork the repo and submit pull requests with enhancements or fixes.
 - **📚 Documentation**: Improvements to docs and examples are always welcome.
 - **💡 Share use cases**: Contribute examples to help other users.

src/examples/clientSse.ts

@@ -1,7 +1,7 @@
 /* eslint-disable no-console */
 /**
  * Connect to the MCP server using SSE transport and call a tool.
- * The Actors MCP Server will load default Actors.
+ * The Apify MCP Server will load default Actors.
  *
  * It requires the `APIFY_TOKEN` in the `.env` file.
  */

src/stdio.ts

@@ -87,7 +87,7 @@ Note: Tools that enable you to search Actors from the Apify Store and get their
         'To connect, set your MCP client server command to `npx @apify/actors-mcp-server`'
         + ' and set the environment variable `APIFY_TOKEN` to your Apify API token.\n',
     )
-    .epilogue('For more information, visit https://mcp.apify.com or https://github.com/apify/actors-mcp-server')
+    .epilogue('For more information, visit https://mcp.apify.com or https://github.com/apify/apify-mcp-server')
     .parseSync() as CliArgs;
 
 const enableAddingActors = argv.enableAddingActors && argv.enableActorAutoLoading;

tests/integration/actor.server-sse.test.ts

@@ -15,7 +15,7 @@ const httpServerHost = `http://localhost:${httpServerPort}`;
 const mcpUrl = `${httpServerHost}/sse`;
 
 createIntegrationTestsSuite({
-    suiteName: 'Actors MCP Server SSE',
+    suiteName: 'Apify MCP Server SSE',
     transport: 'sse',
     createClientFn: async (options) => await createMcpSseClient(mcpUrl, options),
     beforeAllFn: async () => {

tests/integration/actor.server-streamable.test.ts

@@ -15,7 +15,7 @@ const httpServerHost = `http://localhost:${httpServerPort}`;
 const mcpUrl = `${httpServerHost}/mcp`;
 
 createIntegrationTestsSuite({
-    suiteName: 'Actors MCP Server Streamable HTTP',
+    suiteName: 'Apify MCP Server Streamable HTTP',
     transport: 'streamable-http',
     createClientFn: async (options) => await createMcpStreamableClient(mcpUrl, options),
     beforeAllFn: async () => {