krs-poland

The KRS Poland MCP Server provides two MCP-compatible tools for accessing the Polish National Court Register (KRS) public API: get-krs-current-extract and get-krs-full-extract. The get-krs-current-extract tool returns the current status and key details for a given KRS entity, while get-krs-full-extract retrieves the complete historical record for that entity. The server is designed to run via npx, enabling you to use it as a tool provider for LLM clients without a global installation. When integrated with an MCP client, the server can be spawned as a background process and wrapped with the MCP protocol for request/response handling.

To use with an MCP client, configure the client to start the server using the provided command and arguments (npx -y krs-poland-mcp-server). Once started, the client can issue MCP requests to the two available endpoints, such as get-krs-current-extract and get-krs-full-extract, to fetch KRS data for specific entities. The server handles authentication as needed by the underlying KRS public API and returns structured results suitable for downstream processing by language models or other automation tools.

Prerequisites:

• Node.js and npm installed on your system (Node.js 14+ recommended).
• Internet access to fetch the MCP server package via npx.

Installation steps:

1. Clone or download the repository to your local machine:

git clone https://github.com/kolawa/kolawa-mcp-servers.git
cd kolawa-mcp-servers/krs-poland

2. Install dependencies (optional when using npx, but useful for local development):

npm install

3. Build the project if a build step exists in the repository (as per development notes):

npm run build

4. Start the server directly via npx (no global installation required):

npx -y krs-poland-mcp-server

5. For development or manual testing, you can run the server locally with npm start if a start script is provided:

npm start

Prerequisites recap: install Node.js (which includes npm), ensure you have network access to fetch the MCP package, and follow the project’s build/start scripts as applicable.

Notes and tips:

• The server is intended to be used as an MCP tool provider via npx, which avoids a global installation.
• When integrating with MCP clients (e.g., LM Studio), use the provided configuration example to spawn the server process with npx and the package name.
• Available tools include get-krs-current-extract and get-krs-full-extract; ensure you provide the appropriate KRS entity identifier in your MCP requests.
• If you encounter rate limits or API changes from the KRS public API, consider implementing request throttling in your MCP client or caching frequently requested records.
• If you customize environment-specific settings (e.g., API endpoints or keys), document them in the client’s environment or the server’s env configuration as needed.