AILANG Parse MCP Server

Deterministic DOCX/PPTX/XLSX/PDF parser: track changes, comments, headers, footers, merged cells.

Tools

Last Updated

Jun 14, 2026

What is the AILANG Parse MCP Server?

The AILANG Parse MCP server gives AI agents structured, permission-aware access to AILANG Parse through the Model Context Protocol. With 31 pre-built actions, agents can read, create, and update AILANG Parse data on behalf of authorized users.

Willow ships the AILANG Parse MCP server as part of an enterprise control plane. Every call runs behind SSO (Okta, Azure AD), enforces RBAC and least-privilege at runtime, writes to a full audit trail, and integrates with Splunk and Loki for SIEM visibility. Connect from Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code, n8n, or any custom agent. Install once, distribute org-wide, and see exactly how AILANG Parse is being used by every AI agent in your stack.

Tools

agentCard

A2A Agent Card for agent-to-agent discovery. Returns a hand-crafted Agent Card with AILANG Parse-specific skills, supported formats, and capability descriptions. @raw: return raw JSON (no {result:..., elapsed_ms:N} envelope) for A2A compliance. Switch to @nowrap once available (lighter than @raw). If using --a2a flag, the built-in route takes precedence (collision guard skips this).

apiSamples

Sample files inventory — delegates to the upstream package. Package @route annotations don't auto-register with serve-api, so we provide a local wrapper here.

apiTools

Tool definitions for Claude, OpenAI, MCP, and A2A agent frameworks. Delegates to the upstream package.

capabilities

capabilities(() -> string ! {Env}) [pure]

deviceAuthApprove

Approve a device authorization request. Called by the browser approval page after user signs in and confirms. Verifies Firebase ID token from Authorization header to ensure the caller is a real authenticated user. Extracts uid from the verified token. Dev mode: ALLOW_SELF_APPROVE=true skips Firebase verification (for testing).

deviceAuthInspect

Look up a pending device code by user_code and return its provenance. No authentication required — possession of the user_code is the proof. The dashboard /approve.html page calls this BEFORE showing the approve UI so the user can see where the request came from (IP, User-Agent, Referer, age) and decide whether to trust it. Returns 404 if the user_code does not match any pending device_codes doc. Already-approved or expired codes return as INPUT_NOT_FOUND too — there is nothing to inspect after the fact.

deviceAuthPoll

Poll for device authorization approval. Returns AUTHORIZATION_PENDING if user hasn't approved yet. Returns DEVICE_CODE_EXPIRED if the code has timed out. Returns approved status with API key on success.

deviceAuthRequest

Request a device authorization code. Returns device_code, user_code, and verification URL. The agent should display the verification_url to the user.

editDocument

Parse a document, apply JSON edit deltas, and return the modified blocks as JSON (same format as POST /api/v1/parse with outputFormat=blocks). filepath: uploaded file path (multipart upload). deltas: JSON array of edit operations — see edit_apply.ail for format. Empty array or "" → round-trip (parse + return unchanged blocks). apiKey: dp_ API key. Response: modified blocks JSON. Use the AILANG SDK or CLI to generate a file from the returned blocks (e.g. ailang run ... --convert output.docx). Only deterministic office formats are supported (docx, pptx, xlsx, odt, odp, ods). AI-required formats (pdf, image, audio, video) are rejected.

estimate

estimate((string, string) -> string ! {Clock, FS}) [pure]

1 2 3 4

1–10 of 31 tools

Customize Tools

Edit descriptions, modify arguments, select tools, or add new ones

Set Up Your AILANG Parse MCP Server in Minutes

Add the following configuration to your MCP client. Authentication is handled via OAuth. Compatible with Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code, n8n, and any MCP-compatible agent.

Claude Desktop

claude_desktop_config.json

{
  "mcpServers": {
    "willow-ailang-parse": {
      "type": "http",
      "url": "https://<org>.mcp-s.com/mcp/mcp/ailang-parse"
    }
  }
}

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "willow-ailang-parse": {
      "type": "http",
      "url": "https://<org>.mcp-s.com/mcp/mcp/ailang-parse"
    }
  }
}

Claude Code

CLI

claude mcp add willow-ailang-parse --transport http https://<org>.mcp-s.com/mcp/mcp/ailang-parse

n8n

HTTP Request Node

{
  "url": "https://<org>.mcp-s.com/mcp/mcp/ailang-parse",
  "method": "POST"
}

Or click "Install with Willow" above to set up automatically with SSO and RBAC preconfigured.

Enterprise Governance for AILANG Parse

Willow adds the layer AILANG Parse and every other SaaS doesn't ship out of the box: every call runs behind SSO (Okta, Azure AD), enforces RBAC and least-privilege at runtime, writes to full audit logs, and detects shadow AI usage across your stack. One MCP gateway. Any agent. Every tool.

AILANG Parse MCP Server FAQ

What is the AILANG Parse MCP server?

The AILANG Parse MCP server is a Model Context Protocol implementation that lets AI agents like Claude, Cursor, and ChatGPT read and write AILANG Parse data through a standardized interface. Willow hosts and governs this server so enterprises can roll it out without a security review backlog.

How is Willow's AILANG Parse MCP server different from the official one?

The official AILANG Parse MCP server is scoped to a single user's account and does not include enterprise governance. Willow's version adds SSO, RBAC, audit logging, shadow AI detection, and centralized control over which actions agents can take across the entire org.

Which AI clients work with the AILANG Parse MCP server?

Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code with MCP support, n8n, and any custom agent built with OpenAI Agents SDK, LangChain, Vercel AI SDK, or Anthropic SDK.

Is the AILANG Parse MCP server secure? How does Willow handle authentication?

Every call runs behind your existing SSO (Okta, Azure AD). Per-user OAuth scopes the agent to exactly what that user can do in AILANG Parse, nothing more. No credentials reach the LLM. Every action writes to an audit trail.

Can I limit which AILANG Parse actions agents can take?

Yes. Willow lets you scope agents to specific actions, specific projects, or specific environments. Toggle actions on or off in the dashboard, or enforce policy via infrastructure-as-code through GitHub.

How do I detect shadow AILANG Parse MCP servers in my org?

Willow's browser extension and discovery service surface unmanaged MCP servers, skills, and AI agents across the org. If a developer installed an unapproved AILANG Parse MCP locally, you'll see it.

What does the AILANG Parse MCP server cost?

Pricing depends on org size and deployment model (SaaS, dedicated cloud, self-host). See withwillow.ai/pricing or contact sales for a quote.

How do I install the AILANG Parse MCP server with Willow?

Install via the Willow Connect Panel in one click, or paste the JSON snippet above into your Claude Desktop, Cursor, or Claude Code config. SSO and RBAC inherit from your existing Willow setup.