Apify MCP Server
If you already use Actors, the actors mcp server is the piece that lets your assistant work with it directly. Apify MCP Server.
Here is an overview list of all the tools provided by the Apify MCP Server.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
actors — docssearch-actors — actorsfetch-actor-details — actorscall-actor — actorsget-actor-run — runsget-dataset-items — storageget-key-value-store-record — storageabort-actor-run — runssearch-apify-docs — docsfetch-apify-docs — docsreport-problem — devget-actor-run-list — runsConfiguration is passed through the environment: UI_MODE, APIFY_TOKEN, YOUR_SKYFIRE_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
Among the file and storage access options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Actors's toolset — actors, search-actors, fetch-actor-details and 11 more — is a fair guide to whether it matches your workflow. It is maintained by GitHub Actions; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| actors | docs |
| search-actors | actors |
| fetch-actor-details | actors |
| call-actor | actors |
| get-actor-run | runs |
| get-dataset-items | storage |
| get-key-value-store-record | storage |
| abort-actor-run | runs |
| search-apify-docs | docs |
| fetch-apify-docs | docs |
| report-problem | dev |
| get-actor-run-list | runs |
| get-actor-log | runs |
| get-dataset | storage |
{
"mcpServers": {
"skyfire": {
"url": "https://api.skyfire.xyz/mcp/sse",
"headers": {
"skyfire-api-key": "<YOUR_SKYFIRE_API_KEY>"
}
},
"apify": {
"url": "https://mcp.apify.com?payment=skyfire"
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| UI_MODE | Configuration value read at startup. | Optional |
| APIFY_TOKEN | Credential the server authenticates with. | Yes |
| YOUR_SKYFIRE_API_KEY | Credential the server authenticates with. | Yes |
Scoped local file access — read, write, search and reorganise files in directories you explicitly allow.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Build a programmable telecommunications stack for connecting telephony services with the Internet via a cloud-based utility.
Chat with your second brain — search, read and write vault notes through the Local REST API.
Connects AI models to an Obsidian knowledge base for direct access and manipulation of notes and folders.