Alternatives
Products that do what Apify: MCP connectors does
Apify's built-in credential layer for third-party tools
- 1
- 2
- 3
Give AI agents access to real-time data across 200+ apps
May 2026 · apideck.com
- 4
- 5
- 6SC
Our team lives in Slack, but we don’t have access to the Slack MCP and couldn’t find anything out there that worked for us, so we coded our own agent-slack CLI * Can paste in Slack URLs * Token efficient * Zero-config (auto auth if you use Slack Desktop) Auto downloads files/snippets. Also can read Slack canvases as markdown! MIT License
Feb 2026 · github.com
- 7
- 8
- 9
- 10WM
2025 · npmjs.com
- 11
- 12
Work across 20+ apps in Slack with multiplayer collaboration
Jun 2026 · slack.com
- 13
- 14
- 15
- 16OS
Hello HN, I built this because I wanted to give Claude Desktop access to my Notion workspace without running a flaky local Python script via stdio. This is a Node.js/Express implementation of the Model Context Protocol (MCP) that uses SSE (Server-Sent Events) for transport. It’s designed to be stateless and deployable as a container (I'm hosting it on Apify, but it works anywhere with Node). The Stack: TypeScript + Express @modelcontextprotocol/sdk Zod for input validation Bearer Auth for security (since it exposes an HTTP endpoint) Capabilities: It allows the LLM to search pages,…
Dec 2025 · github.com
- 17
- 18
- 19
- 20PA
Hi HN! We’re Theodore and Louis, founders of Armature (YC P26). We reconstruct the entire session behind the MCP tool calls you receive, including what the user asked their agent to do and what the agent thought. You wrap your MCP in 3 lines of code (our SDK is available in Typescript, Python and Go) and start seeing in your dashboard: - All sessions reconstructed: it’s like reading the real conversation the user had inside Claude or ChatGPT! - A ranking of your MCP most popular use cases, built from sessions clustering - The most frequent issues your users’ agents encounter so you can fix…
Aug 2026 · armature.tech
- 21
- 22KC
We built the Kontext CLI because AI coding agents need access to GitHub, Stripe, databases, and dozens of other services — and right now most teams handle this by copy-pasting long-lived API keys into .env files, or the actual chat interface, whilst hoping for the best. The problem isn't just secret sprawl. It's that there's no lineage of access. You don't know which developer launched which agent, what it accessed, or whether it should have been allowed to. The moment you hand raw credentials to a process, you've lost the ability to enforce policy, audit access, or rotate without pain. The…
Apr 2026 · github.com
- 23
- 24
Ranked by how close each launch is in meaning, then by votes. Refine with a description →