Skip to content

feat(mcp): Adding Apify MCP server - #21

Open
drobnikj wants to merge 2 commits into
mainfrom
feat/apify-mcp
Open

feat(mcp): Adding Apify MCP server#21
drobnikj wants to merge 2 commits into
mainfrom
feat/apify-mcp

Conversation

@drobnikj

@drobnikj drobnikj commented Sep 8, 2026

Copy link
Copy Markdown
Member

What does this PR do?

Adds Apify's hosted MCP server to the optional catalog, using existing MCP support—no new core tools or local server to manage.

Related Issue

No linked issue.

Type of Change

  • ✨ New feature (non-breaking)

Changes Made

  • Add optional-mcps/apify/manifest.yaml with hosted Streamable HTTP, browser OAuth, and optional tool/client telemetry disabled by default.
  • Add Apify discovery hints and setup guidance for login, tool selection, and a new session.
  • Explain Actor pricing: runs can consume Apify credits; setup does not run Actors.

How to Test

  1. Install Apify from the MCP catalog and authenticate in the browser. If needed, run hermes mcp login apify.
  2. Start a new Hermes session and ask: “Find Apify Actors for extracting product data. Do not run them.” Verify discovery returns results.
  3. Search Apify documentation, then use hermes mcp configure apify to verify tool selection works.

These are manual verification steps, not a claim of completed end-to-end testing. Actor execution is optional and should only be tested after reviewing pricing and inputs.

Checklist

Code

  • Contributing Guide reviewed.
  • Commit follows Conventional Commits (feat: Adding Apify MCP server).
  • Existing PRs searched; related approaches linked above.
  • Scope limited to the Apify catalog manifest.
  • Full test suite passed — not confirmed; Python tests were still pending at review time. Local command: scripts/run_tests.sh.
  • New tests added — none in this manifest-only PR.
  • Manual platform/E2E testing — not yet confirmed.

Documentation & Housekeeping

  • Setup, authentication, tool configuration, and pricing guidance included in the manifest.
  • Config example changes: N/A; no new config keys.
  • Architecture/workflow documentation changes: N/A; existing MCP catalog path.
  • Cross-platform impact considered: hosted HTTP/OAuth; no local commands or platform-specific dependencies added.
  • Tool schema changes: N/A; tools supplied by the remote MCP server.

Screenshots / Logs

No manual screenshots or logs supplied. CI run: Python lint, E2E, and macOS jobs passed at review time; Python and Windows tests were pending. Contributor attribution needs mapping, and the MCP catalog requires maintainer security review plus the ci-reviewed label.

@drobnikj drobnikj changed the title feat: Adding Apify MCP server feat(mcp): Adding Apify MCP server Sep 8, 2026
@github-actions

github-actions Bot commented Sep 8, 2026

Copy link
Copy Markdown

૮ >ﻌ< ა ci review

ran on cb027c4 — fix: missing contributor

❌ Job failures

Review label gate / Review label gate · View job

Job Review label gate / Review label gate failed.


debug info

CI timings

CI timings · View report · View job

Wall time 1440m15s (no baseline yet).

@drobnikj
drobnikj requested a review from MQ37 September 8, 2026 14:21

@MQ37 MQ37 left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

LGTM. I would maybe expand the keywords for scraping etc. but in general it's ok

@jirispilka jirispilka left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Looks good, I just left a couple of comments. Thanks

manifest_version: 1

name: apify
description: Discover and run Apify Actors for web scraping, data extraction, and automation, and search Apify documentation.

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Suggested change
description: Discover and run Apify Actors for web scraping, data extraction, and automation, and search Apify documentation.
description: Extract data from any website with thousands of scrapers, crawlers, and automations on Apify Store.


name: apify
description: Discover and run Apify Actors for web scraping, data extraction, and automation, and search Apify documentation.
source: https://docs.apify.com/platform/integrations/mcp

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Suggested change
source: https://docs.apify.com/platform/integrations/mcp
source: https://docs.apify.com/integrations/mcp

# Hosted Streamable HTTP; disable optional tool/client telemetry by default.
transport:
type: http
url: https://mcp.apify.com/?telemetry-enabled=false

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

do we really want to disable telemetry?

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