MCP Setup

Connect Jiro to your AI coding tools via Model Context Protocol.

Supported Clients

Jiro provides an MCP (Model Context Protocol) server that works with all major AI coding tools. The MCP server exposes 16 tools including search, scrape, AI search, hybrid search, structured extraction, social scraping, social search, batch processing, smart search, intent classification, engine comparison, monitoring, health checks, cache stats, and platform discovery.

All clients connect via stdio transport using the jiro mcp serve command.

MCP Clients

NameTypeDescription
Claude Desktop
stdioAnthropic's desktop app. Config path: `~/Library/Application Support/Claude/claude_desktop_config.json` (macOS) or `%APPDATA%\Claude\claude_desktop_config.json` (Windows).
Cursor
stdioAI code editor. Config path: `~/.cursor/mcp.json`. Supports both global and project-level MCP configuration.
OpenCode
stdioOpen-source CLI. Config path: `~/.config/opencode/opencode.json`. Auto-detected when Jiro is installed.
Codex CLI
stdioOpenAI's CLI tool. Config path: `~/.codex/config.json`. Uses stdio transport for MCP communication.
Continue.dev
stdioVS Code and JetBrains extension. Config path: `~/.continue/config.json`. Add Jiro as an MCP server in the `mcpServers` section.
Zed
stdioRust-based editor. Config path: `~/.config/zed/settings.json`. Add to the `context_servers` section.

Setup Wizard

Jiro includes a built-in setup wizard that automatically configures your MCP client. The wizard detects installed clients and writes the correct configuration.

The wizard will: 1. Detect which MCP clients are installed 2. Ask you to select a client (if multiple are found) 3. Generate the correct configuration JSON 4. Write it to the client's config file 5. Verify the configuration is valid

bash

Manual Configuration — Claude Desktop

Add the following to your Claude Desktop config file:

json

Manual Configuration — Cursor

Add the following to your Cursor MCP config file:

json

Manual Configuration — OpenCode

Add the following to your OpenCode config file:

json

Manual Configuration — Continue.dev

Add the following to your Continue config file:

json

Manual Configuration — Zed

Add the following to your Zed settings.json:

json

Available MCP Tools

Once connected, the following tools are available to your AI agent:

MCP Tools

NameTypeDescription
search
FreeWeb search across 9 engines (Google, Bing, Brave, DuckDuckGo, YouTube, Amazon, eBay, Yandex, Baidu). Returns structured SERP results with titles, URLs, snippets, and metadata.
scrape
FreeScrape any URL and extract readable content as markdown, text, HTML, or JSON. Returns page title, main content, metadata, links, and images.
ai_search
FreeAnswer a research question by searching the web, reading multiple sources, and synthesizing a comprehensive answer with citations.
search_hybrid
FreeHybrid search combining keyword, semantic, and freshness signals for enhanced relevance. Better than plain search for ambiguous or time-sensitive queries.
search_structured
FreeExtract structured data from search results using a JSON Schema. Returns data conforming exactly to the provided schema.
social_scrape
FreeScrape a social media post or profile from any supported platform. Auto-detects platform from URL. Returns normalized data including author, content, engagement, and media.
social_search
FreeSearch for posts across multiple social platforms simultaneously. Returns normalized results ranked by relevance and engagement.
social_batch
FreeBatch scrape multiple social media URLs in parallel (up to 10). Returns per-URL results with status, data, or errors.
smart_search
FreeIntelligent search with automatic intent detection and routing. Classifies the query intent and automatically routes to the best handler.
smart_classify
FreeClassify the intent of a search query without executing it. Returns intent category, target handler, confidence score, and suggested schema.
compare_engines
FreeCompare search results across multiple engines side by side. Returns result counts, first results, and engine-specific metadata.
monitor_status
FreeGet comprehensive server status including engine health, cache stats, social platform status, and MCP tool count.
health_check
FreeQuick health check for all services and dependencies. Returns overall status and per-service health details.
cache_stats
FreeGet cache hit/miss statistics, TTL, and configuration. Use to understand caching behavior and debug stale results.
list_engines
FreeList all available search engines with supported types (web, images, news, videos, shopping, places) and capabilities.
list_social_platforms
FreeList all supported social media platforms with their capabilities (scrape, search, profile, timeline, etc.) and base URLs.

Troubleshooting

MCP server fails to start - Verify Jiro is installed: jiro --version - Verify Redis is running: redis-cli ping - Check logs: jiro mcp serve --verbose

Client cannot connect - Ensure the command field points to the correct jiro binary path - Check that JIRO_BASE_URL matches your running server address - Verify no firewall is blocking the connection

Tools not appearing - Restart your MCP client after configuration changes - Verify the config file is valid JSON (no trailing commas) - Check that the MCP server starts without errors: jiro mcp serve

Enterprise tools missing - Verify your license token is set: jiro status - Ensure the token is valid and not expired - Check that enterprise features are enabled in your config

Need help?

Check our error codes or reach out to the team.