Stocky vs Kagimcp — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Stocky vs Kagimcp
In-depth architectural comparison of the Stocky and Kagimcp MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Stocky
Search & Data Extraction · Local stdio
Quality: 55/100 (Good) | Auth: API Key required
Kagimcp
Search & Data Extraction · Local stdio
Quality: 82/100 (Excellent) | Auth: API Key required
Verdict Summary: Choose Stocky if you need specialized Search & Data Extraction tools running via a local process. Choose Kagimcp if your workspace requires Search & Data Extraction integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Stocky when:
You need dedicated capabilities in the Search & Data Extraction domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
You have access to required keys: PEXELS_API_KEY, UNSPLASH_ACCESS_KEY, ENABLE_ATTRIBUTION_LINKS, STOCKY_CACHE_TTL, STOCKY_HTTP_TIMEOUT, STOCKY_MAX_DOWNLOAD_BYTES, STOCKY_DOWNLOAD_ROOT, STOCKY_LOG_LEVEL.
Primary tools included: Concurrent multi-provider search (Pexels and Unsplash), Rich metadata including image sizes, photographer, tags, License-aware attribution generation per provider requirements.
An MCP server for searching and downloading royalty-free stock photography from Pexels and Unsplash. Features multi-provider search, rich metadata, pagination support, and async performance for AI assistants to find and access high-quality images.
The Official Model Context Protocol (MCP) server for Kagi Search & other tools.
Category & Scope
Tools & Capabilities Breakdown
Stocky Tools (6)
Concurrent multi-provider search (Pexels and Unsplash)
Rich metadata including image sizes, photographer, tags
License-aware attribution generation per provider requirements
Search result caching with configurable TTL
Filters for orientation, color, and sorting (provider-specific)
Error reporting for failing providers instead of silent empty results
Kagimcp Tools (2)
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Stocky is categorized under Search & Data Extraction and uses a local stdio subprocess. In contrast, Kagimcp belongs to Search & Data Extraction using local stdio subprocess. Select Stocky when you need capabilities focused on search & data extraction and Kagimcp when you require tools for search & data extraction.
Fetch web results for a query using the Kagi Search API. Use for general search and when the user explicitly tells you to 'fetch' results/information. Results are numbered so that a user may refer to a result by a specific number.
kagi_extract
Extract the content of a web page as markdown using the Kagi Extract API. Use this to read the full content of a page when needed.