Parsewise MCP

Connect AI agents and assistants to Parsewise via the Model Context Protocol (MCP).

Table of contents

Claude setup

Watch this quick walkthrough to connect Claude to the Parsewise MCP server:

Overview

Parsewise hosts a remote MCP server that exposes the platform as a set of tools: an MCP-capable client (Cursor, VS Code, Claude, or your own agent) can create projects, upload documents, define and launch extraction agents, and read results with citations — the same workflows as the app and the REST API.

What you can do with MCP

MCP lets your AI assistant work with Parsewise directly, so you can ask for outcomes instead of switching between tools:

  • Set up a document review project from a plain-language request.
  • Upload and organise documents so they are ready for extraction.
  • Define the information you need — for example key dates, renewal terms, revenue figures, clauses, policy limits, or counterparty names.
  • Run extraction and monitor progress without manually checking each page in the app.
  • Read structured answers with citations so you can trace each value back to the source document.
  • Iterate on the setup by asking the assistant to adjust fields, add dimensions, or re-run extraction when new documents arrive.

The server also includes built-in guidance for MCP clients, so assistants can look up the recommended workflow, dimension setup, agent iteration, and troubleshooting steps while they work.

Server URL 

https://api.parsewise.ai/mcp

The server uses the streamable HTTP transport, so any client that supports remote MCP servers can connect with just this URL.

Authentication

The recommended way to authenticate is OAuth. MCP clients that support OAuth discovery can connect with the server URL alone:

https://api.parsewise.ai/mcp

The server advertises protected-resource metadata and walks the client through an Auth0 login for your Parsewise organisation. Use OAuth when you want user-scoped access without managing API keys.

API keys are also supported as an alternative for clients or automation that need header-based authentication. Send a Parsewise API key in the X-API-Key header:

X-API-Key: pw_live_...
  • Keys are prefixed pw_live_ and scoped to one organisation — the same keys used for the REST API.
  • Create and manage keys on the Developer page.
  • Treat keys as secrets. Prefer environment-variable references in client configs over pasting the raw key.

Under the hood the server promotes X-API-Key to the bearer credential used by the MCP transport. If both an API key and an OAuth token are present, the API key takes precedence.

Client configuration

Cursor

Add to ~/.cursor/mcp.json (or .cursor/mcp.json in a project):

{
  "mcpServers": {
    "parsewise": {
      "url": "https://api.parsewise.ai/mcp"
    }
  }
}

VS Code

Add to .vscode/mcp.json (or via MCP: Add Server):

{
  "servers": {
    "parsewise": {
      "type": "http",
      "url": "https://api.parsewise.ai/mcp"
    }
  }
}

API key alternative

For clients that do not support OAuth, export your key once:

export PARSEWISE_API_KEY=pw_live_...

Then add the X-API-Key header to the client config.

Cursor:

{
  "mcpServers": {
    "parsewise": {
      "url": "https://api.parsewise.ai/mcp",
      "headers": {
        "X-API-Key": "${env:PARSEWISE_API_KEY}"
      }
    }
  }
}

VS Code:

{
  "servers": {
    "parsewise": {
      "type": "http",
      "url": "https://api.parsewise.ai/mcp",
      "headers": {
        "X-API-Key": "${env:PARSEWISE_API_KEY}"
      }
    }
  }
}

Other clients

For OAuth-capable clients, point them at https://api.parsewise.ai/mcp and complete the login prompt. For header-based clients, provide the same URL plus an X-API-Key request header.

Support