JigsawStack MCP Server

Created By
JigsawStacka year ago
Model Context Protocol Server that allows AI models to interact with JigsawStack models!
Overview

What is JigsawStack MCP Server?

JigsawStack MCP (Model Context Protocol) Server is a versatile platform designed to facilitate the integration and management of various tools, allowing AI models to interact with JigsawStack models.

How to use JigsawStack MCP Server?

To use the JigsawStack MCP Server, first obtain your JIGSAWSTACK_API_KEY from the JigsawStack website. Clone the repository, navigate to the project directory, install the necessary dependencies, and start the server. Access the server through your web browser at http://localhost:3000.

Key features of JigsawStack MCP Server?

  • Modular framework for integrating LLMs and managing tools.
  • Each tool is encapsulated within its own directory for easy management.
  • Supports multiple tools like AI web scraper, AI web search, and image generation.

Use cases of JigsawStack MCP Server?

  1. Automating web scraping tasks using AI.
  2. Performing complex searches powered by AI.
  3. Generating images from textual prompts.

FAQ from JigsawStack MCP Server?

  • What is MCP?

MCP stands for Model Context Protocol, a framework for integrating LLMs and managing tools.

  • How do I get my API key?

You can sign up for a free account at JigsawStacks to obtain your API key.

  • What technologies are used in JigsawStack MCP Server?

The server is built using Node.js and Express.js.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
JigsawStack
Star
18
Language
TypeScript
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago