mcpscraper-memory-sdk

Official TypeScript/JavaScript clients for all 159 tools at mcpscraper.dev plus the direct 87-tool memory.mcpscraper.dev API.

These are thin clients: MemoryClient calls the direct memory MCP with a memory Bearer key, while McpToolsClient calls the unified MCP with a scraper API key. No product logic lives in this package.

Install

npm install mcpscraper-memory-sdk

For the complete unified surface, use the same McpToolsClient exported by every SDK package:

import { McpToolsClient } from 'mcpscraper-memory-sdk'

const tools = new McpToolsClient({ apiKey: process.env.MCP_SCRAPER_API_KEY! })
await tools.browser.listSessions()
await tools.memory.search({ query: 'q3 roadmap decisions' })
await tools.connections.exportConnectedServiceData({ connectionId: 'conn_123', lastDays: 7 })

The unified connection namespace includes permission-aware provider inventory and meta_ads_insights bulk exports for daily account, campaign, ad-set, and ad reporting, with large results delivered as private artifacts.

OAuth connect/reconnect and direct connected-service operations do not currently have an extra connection-operation debit beyond the required paid plan. Scheduled Actions use the shared MCP Scraper balance at 75 Credits per started occurrence; agent-mode runs add 1.5 times OpenRouter's actual reported model cost. Read the live contract with await tools.schedule.getScheduleStatus().

Quickstart

import { MemoryClient, MemoryApiError } from 'mcpscraper-memory-sdk'

const client = new MemoryClient({ apiKey: process.env.MCP_MEMORY_API_KEY! })

try {
  const results = await client.memory.search({ query: 'q3 roadmap decisions' })
  console.log(results.results)

  const note = await client.memory.get({ path: 'projects/q3-plan' })
  console.log(note)
} catch (err) {
  if (err instanceof MemoryApiError) {
    console.error('memory API error:', err.message, err.rpcCode, err.httpStatus)
  } else {
    throw err
  }
}

Namespaces

MemoryClient retains the direct 87-tool memory namespaces. McpToolsClient is generated from contracts/mcp.tools.json and contains all 159 tools — 72 MCP Scraper tools plus 87 mirrored memory tools — across its generated namespaces.

Use client.callToolResult(name, args) when a tool can return native MCP image, audio, or resource content. It preserves the complete content, structuredContent, and isError result. The existing callTool method remains the convenient parsed JSON/text path.

Every method's input/output types are generated from the live tool schemas (see src/generated/, produced by npm run generate at the repo root from contracts/memory.tools.json) — no hand-maintained duplicate types to drift out of sync.

Getting an API key

Issue one via the access-issue-key tool (or client.access.issueKey(...) once you have an initial key), or through the memory dashboard.

Errors

All failures — HTTP-level, JSON-RPC-level, and MCP tool-level (isError: true) — surface as a single MemoryApiError with httpStatus, rpcCode, and data/toolError fields depending on where the failure occurred.

See also

Repo README (multi-language examples with real sample output) · mcpscraper-sdk (Node, also reaches these 87 tools via client.memoryTools using only a scraper key) · mcpscraper-memory-sdk Python source package · mcpscraper-cli