Skip to content

Conversation

TC-MO
Copy link
Contributor

@TC-MO TC-MO commented Sep 15, 2025

Stremline the prose for clarity & conciseness
Remove outdated SSE section
Restructure the content
Adjusted description in frontmatter


Note

Restructures MCP docs with tabbed OAuth/Bearer client configs (Cursor, VS Code, Claude), adds tool selection and advanced/troubleshooting sections, updates links/frontmatter, and removes legacy SSE guidance.

  • Docs restructuring and content:
    • Authentication & setup: Introduce tabbed configs for OAuth and Bearer token; add client-specific setup for Cursor, VS Code, and Claude Desktop using Tabs.
    • Quick start split: Clarify hosted Streamable HTTP vs local stdio with updated examples and config snippets.
    • Tool selection: Explain tools query/CLI flags with minimal and default examples; add UI configurator link.
    • Available tools: Refresh table; add get-actor-output tool and note on retrieving full outputs.
    • Advanced/troubleshooting: Add production best practices, rate limits/performance, and troubleshooting (auth, local env, actor issues).
  • Removals/cleanups:
    • Remove legacy SSE transport section and related examples.
  • Metadata and links:
    • Update frontmatter description and add toc_max_heading_level: 4.
    • Update images/prose and GitHub links to apify/apify-mcp-server.

Written by Cursor Bugbot for commit 71640ce. This will update automatically on new commits. Configure here.

Stremline the prose for clarity & conciseness
Remove outdated SSE section
Restructure the content
Adjusted description in frontmatter
@TC-MO TC-MO self-assigned this Sep 15, 2025
@TC-MO TC-MO added documentation Improvements or additions to documentation. t-docs Issues owned by technical writing team. labels Sep 15, 2025
@TC-MO TC-MO requested review from MQ37 and jirispilka September 15, 2025 20:39
@apify-service-account
Copy link

Preview for this PR was built for commit f72c67f0 and is ready at https://pr-1927.preview.docs.apify.com!

@apify-service-account
Copy link

Preview for this PR was built for commit 68d98c36 and is ready at https://pr-1927.preview.docs.apify.com!

@apify-service-account
Copy link

Preview for this PR was built for commit f8d417e4 and is ready at https://pr-1927.preview.docs.apify.com!

@apify-service-account
Copy link

Preview for this PR was built for commit 796dca20 and is ready at https://pr-1927.preview.docs.apify.com!

@apify-service-account
Copy link

Preview for this PR was built for commit ff851083 and is ready at https://pr-1927.preview.docs.apify.com!

@apify-service-account
Copy link

Preview for this PR was built for commit cd071cad and is ready at https://pr-1927.preview.docs.apify.com!

@TC-MO TC-MO marked this pull request as ready for review September 16, 2025 16:15
@TC-MO
Copy link
Contributor Author

TC-MO commented Sep 16, 2025

@jirispilka @MQ37 as discussed back in the office and in the issue #1777. This PR aims to improve MCP docs.

I've streamlined them and cleaned up legacy section, cleaned up the language, restructured them for better logical flow & clarity, and based on this discussion on slack I've added a new section describing how to add the MCP server to popular editors like VSC & Cursor & Claude Desktop. I think this is vast improvement over what we had, but all feedback is welcome. I'll also try to research how to create deeplinks like Stripe has in their docs for easy install in Cursor & VSC

Copy link
Contributor

@MQ37 MQ37 left a comment

Choose a reason for hiding this comment

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

Nice overhaul, thank you! Just a few comments regarding the content 👍

_Claude Desktop_: Download and run the [Apify MCP Server DXT file](https://github.com/apify/actors-mcp-server/releases/latest/download/apify-mcp-server.dxt) for one-click installation.
:::

#### Text editor configuration
Copy link
Contributor

Choose a reason for hiding this comment

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

I know code is essentially text but I would call this Code editor configuration

Copy link
Contributor

Choose a reason for hiding this comment

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

Also Claude Desktop is not a text or code editor, so I would maybe just use "Client configuration"

Copy link
Contributor

Choose a reason for hiding this comment

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

BTW I like the DXT one click install block for the Claude desktop, that is really nice 👍

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yup, I admit Text editor config was a bit of placeholder but I do like Client configuration a lot thanks!

By default, the server is pre-configured with one Actor, `apify/rag-web-browser`, and several helper tools.
The MCP server loads an Actor's input schema and creates a corresponding MCP tool.
This allows the AI agent to know exactly what arguments to pass to the Actor and what to expect in return.
For development environments, you can run the MCP server locally. This approach gives you more control over the server configuration and is ideal for testing.
Copy link
Contributor

Choose a reason for hiding this comment

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

I would not mention this in context of development envs but rather that this is alternative approach for client that do not support remote MCP servers using the url mcp.apify.com

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Makes sense, I'll rephrase

Copy link
Contributor

Choose a reason for hiding this comment

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

Agree with @MQ37

Also, this: "This approach gives you more control over the server configuration and is ideal for testing"
It does not give you more control over the server configuration. It just a different way of how to run it. Stdio might eventually die anyway

:::caution Important recommendation
- Always use the latest version of the server by appending `@latest` to your npm commands.
- Monitor your API usage through Apify Console to stay within your plan limits.
- For optimal performance, batch related operations when possible and use Actor webhooks for long-running tasks instead of polling for results.
Copy link
Contributor

Choose a reason for hiding this comment

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

Can users somehow manage and use webhooks via MCP? I am not sure how would I do this myself since we do not support tasks. I would probably not mention this.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yeah I might have went overboard here, I'll remove it

Co-authored-by: Jakub Kopecký <themq37@gmail.com>
@apify-service-account
Copy link

Preview for this PR was built for commit b7d83fef and is ready at https://pr-1927.preview.docs.apify.com!

Copy link
Contributor

@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.

@TC-MO great work! This is really a big improvement, love it ❤️

I left a couple of suggestions.

## Quick start

Before you start, make sure you have the following:
You can connect to the Apify MCP server in two ways: use our hosted service for a quick and easy setup, or run the server locally for development and testing.
Copy link
Contributor

Choose a reason for hiding this comment

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

Here you write: "use our hosted service for a quick and easy setup, or run the server locally"

But then, just one line below, you have tittle "Streamable HTTP with OAuth".

Some users might not connected hosted service with Streamable HTTP with OAuth. I know it might be obvious, but still it would be able to reference it to remove some confusion.

By default, the server is pre-configured with one Actor, `apify/rag-web-browser`, and several helper tools.
The MCP server loads an Actor's input schema and creates a corresponding MCP tool.
This allows the AI agent to know exactly what arguments to pass to the Actor and what to expect in return.
For development environments, you can run the MCP server locally. This approach gives you more control over the server configuration and is ideal for testing.
Copy link
Contributor

Choose a reason for hiding this comment

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

Agree with @MQ37

Also, this: "This approach gives you more control over the server configuration and is ideal for testing"
It does not give you more control over the server configuration. It just a different way of how to run it. Stdio might eventually die anyway

@jirispilka
Copy link
Contributor

@TC-MO I really like the changes you did, would you have time to finish it this week 🙏🏻 . Before MPC summit in London?

@TC-MO
Copy link
Contributor Author

TC-MO commented Sep 29, 2025

Hey! Yes I planeed to have it done before my vacation but in the end this didn't work out. I'm just now sitting down to finish this and have it released by tomorrow. Will that work for you?

@jirispilka
Copy link
Contributor

Yeah, that would be great!

@apify-service-account
Copy link

Preview for this PR was built for commit 5800b41c and is ready at https://pr-1927.preview.docs.apify.com!

Co-authored-by: Jiří Spilka <jiri.spilka@apify.com>
@TC-MO TC-MO requested review from MQ37 and jirispilka September 30, 2025 21:52
@apify-service-account
Copy link

Preview for this PR was built for commit 5932f6cb and is ready at https://pr-1927.preview.docs.apify.com!

Copy link
Contributor

@MQ37 MQ37 left a comment

Choose a reason for hiding this comment

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

Thank you for the rework - great job 👍 Please merge the #1932 and then LGTM

@TC-MO
Copy link
Contributor Author

TC-MO commented Sep 30, 2025

Oh! So sorry! I completely forgot about that PR, will take a look ASAP


:::tip One-click installation

Download and run the [Apify MCP Server DXT file](https://github.com/apify/actors-mcp-server/releases/latest/download/apify-mcp-server.dxt) for one-click installation.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
Download and run the [Apify MCP Server DXT file](https://github.com/apify/actors-mcp-server/releases/latest/download/apify-mcp-server.dxt) for one-click installation.
Download and run the [Apify MCP Server MCPB file](https://github.com/apify/actors-mcp-server/releases/latest/download/apify-mcp-server.mcpb) for one-click installation.

I forgot to update the link and DXT was rebranded to MCP bundles (MCPB)

Copy link
Contributor

Choose a reason for hiding this comment

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

FYI @TC-MO

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Thanks, I also forgot about this

Add `get-actor-output` tools info and merge into the
#1927

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> Documents a new `get-actor-output` tool for retrieving full Actor
outputs, with a note on automatic inclusion, datasetId usage, and
pagination/field filtering.
> 
> - **Docs (MCP server)**:
> - **New tool**: Add `get-actor-output` entry to the Available tools
table.
> - **Usage note**: Explain that it’s auto-included with Actor tools
(e.g., `call-actor`, `add-actor`), used to fetch full output via
`datasetId`, and supports limit/offset/field filtering.
> 
> <sup>Written by [Cursor
Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit
a46162b. This will update automatically
on new commits. Configure
[here](https://cursor.com/dashboard?tab=bugbot).</sup>
<!-- /CURSOR_SUMMARY -->

---------

Co-authored-by: Michał Olender <92638966+TC-MO@users.noreply.github.com>
@apify-service-account
Copy link

Preview for this PR was built for commit 71640cec and is ready at https://pr-1927.preview.docs.apify.com!

Copy link
Contributor

@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 did a quick pass, looks good to me. Thanks!

@TC-MO
Copy link
Contributor Author

TC-MO commented Oct 1, 2025

let's merge away then!

@TC-MO TC-MO merged commit 4b8bb6e into master Oct 1, 2025
11 checks passed
@TC-MO TC-MO deleted the mcp-restructure branch October 1, 2025 12:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation. t-docs Issues owned by technical writing team.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants