instruckt-mcp

instruckt-mcp

MCP server for instruckt visual annotations. Enables AI agents to retrieve pending annotations, view screenshots, and resolve annotations.

Category
Visit Server

README

instruckt-mcp

MCP server and API handlers for instruckt visual annotations. Stores annotations and screenshots to disk, and exposes them to your AI agent via MCP tools.

Install

npm install instruckt-mcp

Quick Start

Pick your setup below — each section is self-contained.

Setup Use when
Next.js App Router route handler
Ember.js 6+ Dev-server middleware via server/index.js
Custom backend Any Node.js framework

Next.js

Create a route handler at app/api/annotations/[[...slug]]/route.ts:

import { createHandlers } from 'instruckt-mcp/nextjs'

export const { GET, POST, PATCH } = createHandlers()

Then wire up the MCP server in your Claude/agent config:

{
  "mcpServers": {
    "instruckt": {
      "command": "npx",
      "args": ["instruckt-mcp"]
    }
  }
}

Ember.js 6+

Add the adapter to your Ember CLI dev-server in server/index.js:

const { createEmberMiddleware } = require('@tdwesten/instruckt-mcp/ember');

module.exports = createEmberMiddleware();

This registers GET, POST, and PATCH /api/annotations on the Ember CLI Express dev-server. Request bodies up to 10 MB are accepted (large enough for base64-encoded screenshots). Options:

Option Type Default Description
route string /api/annotations Base path for the endpoints (trailing slashes are trimmed)
dir string .instruckt Storage directory

Development only. Ember CLI's middleware runs during ember serve. For production, use the Custom backend setup with your own Node server.

Then wire up the MCP server in your Claude/agent config:

{
  "mcpServers": {
    "instruckt": {
      "command": "npx",
      "args": ["instruckt-mcp"]
    }
  }
}

Custom backend

Use createRequestHandlers with any Node.js framework:

import { InstrucktStorage, createRequestHandlers } from 'instruckt-mcp'

const storage = new InstrucktStorage('.instruckt')
const handlers = createRequestHandlers(storage)

// GET /annotations
app.get('/annotations', async (req, res) => {
  res.json(await handlers.getAnnotations())
})

// POST /annotations
app.post('/annotations', async (req, res) => {
  res.status(201).json(await handlers.createAnnotation(req.body))
})

// PATCH /annotations/:id
app.patch('/annotations/:id', async (req, res) => {
  res.json(await handlers.updateAnnotation(req.params.id, req.body))
})

MCP Tools

Once connected, your AI agent has three tools:

Tool Description
get_all_pending Returns all unresolved annotations — comment, element, page URL, severity
get_screenshot Returns the screenshot image for a specific annotation by ID
resolve Marks an annotation as resolved; the instruckt widget removes the marker on its next poll

How It Works

  1. instruckt runs in your app and captures annotations with optional screenshots
  2. Annotations are posted to your API endpoint and stored as JSON on disk
  3. Your AI agent connects via MCP and calls get_all_pending to see what needs fixing
  4. The agent reads the feedback, inspects screenshots with get_screenshot, and makes code changes
  5. When done, the agent calls resolve — the widget picks up the status change on its next poll and removes the marker

Storage

Annotations are stored in .instruckt/annotations.json. Screenshots go in .instruckt/screenshots/<id>.png. The directory is created automatically on first use.

import { InstrucktStorage } from 'instruckt-mcp'

const storage = new InstrucktStorage('.instruckt')

await storage.getAll()          // all annotations
await storage.getPending()      // unresolved only
await storage.add(input)        // create annotation
await storage.update(id, input) // update annotation
await storage.resolve(id)       // mark as resolved
await storage.getScreenshot(id) // Buffer | null

License

MIT

Recommended Servers

playwright-mcp

playwright-mcp

A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.

Official
Featured
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.

Official
Featured
Local
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.

Official
Featured
Local
TypeScript
VeyraX MCP

VeyraX MCP

Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.

Official
Featured
Local
graphlit-mcp-server

graphlit-mcp-server

The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.

Official
Featured
TypeScript
Kagi MCP Server

Kagi MCP Server

An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.

Official
Featured
Python
E2B

E2B

Using MCP to run code via e2b.

Official
Featured
Neon Database

Neon Database

MCP server for interacting with Neon Management API and databases

Official
Featured
Exa Search

Exa Search

A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.

Official
Featured
Qdrant Server

Qdrant Server

This repository is an example of how to create a MCP server for Qdrant, a vector search engine.

Official
Featured