Local MCP server/Development

I14Y Catalogue OH MCP server

Local MCP server

I14Y Catalogue OH gives an agent a way to query the Swiss national I14Y data catalogue for datasets, APIs and license terms from public bodies. The provider ships a Rust MCP server that speaks stdio and is started by the client as a local process; the repository documents cloning, testing and a cargo-based client config. There is no provider-published hosted endpoint, so the former mcp.openhelvetia.swiss URL has been removed.

None (local stdio process) Source checked Nov 12, 2026 Local install path Reviewed 2026-11-16
About

Where it fits

Swiss public-sector and open-data developers who want catalogue queries inside a local MCP client.

  • Find datasets published by a Swiss public body.
  • Check the license terms for a catalogue dataset.
  • Locate an API linked to a national dataset.

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Install

Build and run the I14Y server

The server speaks MCP over stdio and is started by the client as a local Rust process. There is no provider-published hosted endpoint. Clone the repository first and run the tests with cargo test --locked --manifest-path mcp/servers/i14y/Cargo.toml.

cargo run --quiet --locked --manifest-path <ABS>/mcp/servers/i14y/Cargo.toml

This is a local install path. Install and run it first, then add the local command or URL to OpenCode, VS Code, or another compatible client. The provider controls the package, required keys, and runtime.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • The server connects but no tools appear. Confirm the URL and transport, then restart the client.
  • The first tool call times out. Try a smaller request and check the provider's status or rate limits.
  • The client cannot find the vomo command. Confirm the global CLI install and that the executable is on PATH.
  • The process starts but no tools appear. Sign in to the provider CLI, restart the client, and check the local command output for errors.
Safety

Before you connect

Local process, your machine
  • The MCP server process runs on your machine, not on a provider host.
  • Data leaves only through the model provider and any MCP servers you attach.
  • Review the local command, package, and files it can reach before running it.
  • Stop the process or remove the client entry when you no longer need it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.

Reference

Provider source

Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.

I14Y Catalogue OH repositoryhttps://github.com/openhelvetia/mcp-i14y-catalogue-oh