iA Document Management

You can deploy this MCP server to interact with WingArc's iA Document Management System. It provides a lightweight, scriptable bridge that lets you login, search documents, and logout, all through standardized MCP tools that you can invoke from your MCP client.

How to use

You will use this server through an MCP client to perform three primary actions: authenticate, search documents by free text, and terminate your session. Start by logging in with your user credentials to receive session and CSRF tokens. Then you can perform free-word searches within specified folders, optionally including subfolders, and finally log out to end the session. Ensure you pass the session cookies and CSRF tokens in subsequent requests to keep your session valid.

Typical usage flow you can implement in your MCP client: log in with your username and password, then request a document search by a word like “invoice” within a given folder, and finally log out. Use the session cookie and CSRF token obtained during login for all subsequent requests to the API. Remember to handle token expiration by re-authenticating when needed.

How to install

Prerequisites: Node.js and npm must be installed on your system.

Clone or download the MCP server package and install dependencies, then build the project.

npm install
npm run build

Configuration

Configure the base URL for your iA Document Management System. You can set it as an environment variable when you run the server, or pass it as a parameter to the tools.

export IA_BASE_URL="https://wat-cloud-div.spa-cloud.com"

Usage with Claude Desktop

If you use Claude Desktop, integrate the MCP server by configuring it to run the local Node.js script and providing the base URL as an environment variable.

{
  "mcpServers": {
    "ia-document-management": {
      "command": "node",
      "args": [
        "/Users/sakiko/Applications/iA文書管理MCP/dist/index.js"
      ],
      "env": {
        "IA_BASE_URL": "https://wat-cloud-div.spa-cloud.com"
      }
    }
  }
}

Security notes

The system uses CSRF tokens to protect requests. You receive an XSRF token and session cookie from login, and you should include CSRF headers for non-GET requests. Ensure you provide the XSRF token when performing actions that modify state, and store session credentials securely.

Session management relies on the JSESSIONID cookie. Sessions expire after inactivity, and a new login is required to re-establish a session. Logout requires proper CSRF headers to end the session cleanly.

Example workflow

1. Login with your username and password to obtain session and CSRF tokens.

2. Perform a document search by providing a free word like “invoice” and the target folder IDs.

3. Logout to terminate your session and invalidate tokens.

Troubleshooting and notes

If you encounter CSRF or session issues, ensure you are including the correct CSRF headers and that you are using the valid tokens obtained during login. Incorrect CSRF tokens can invalidate the session and require a new login.

Store credentials securely and avoid committing them to version control. If tokens expire, re-authenticate to obtain fresh tokens.

Available tools

ia_login

Authenticate with the iA Document Management System and retrieve session and CSRF tokens for subsequent requests.

ia_search_documents

Search for documents using a free word search within specified folders, with options for recursion and property retrieval.

ia_logout

Logout from the iA Document Management System, ending the session and invalidating tokens.