lindas.resolve_label — OpenHelvetia Gateway MCP Tool
lindas.resolve_label
(lindas resolve label) is one of 65 tools on the
OpenHelvetia Gateway
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call lindas.resolve_label from your client
- Claude Code OpenHelvetia Gateway lindas.resolve_label run in your project directory
- Claude Desktop OpenHelvetia Gateway lindas.resolve_label ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor OpenHelvetia Gateway lindas.resolve_label ~/.cursor/mcp.json
- VS Code OpenHelvetia Gateway lindas.resolve_label .vscode/mcp.json
- Zed OpenHelvetia Gateway lindas.resolve_label ~/.config/zed/settings.json
- Windsurf OpenHelvetia Gateway lindas.resolve_label ~/.codeium/windsurf/mcp_config.json
- Cline OpenHelvetia Gateway lindas.resolve_label ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI OpenHelvetia Gateway lindas.resolve_label ~/.gemini/settings.json
- Grok OpenHelvetia Gateway lindas.resolve_label .mcp.json (in your project root)
- ChatGPT OpenHelvetia Gateway lindas.resolve_label Settings → Connectors → Advanced → Developer mode
- Claude.ai OpenHelvetia Gateway lindas.resolve_label Settings → Connectors → Add custom connector
- LangChain OpenHelvetia Gateway lindas.resolve_label pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http gateway https://mcp.openhelvetia.swiss/mcpOther tools on this server
- directory.get
- facts.badge
- facts.latest
- fedlex.check_in_force
- fedlex.check_quote
- fedlex.cite
- fedlex.compare_versions
- fedlex.detect_foreign_content
- fedlex.explore_node
- fedlex.extract_tables
- fedlex.find_related_topic
- fedlex.find_treaties
- fedlex.get_article_history
- fedlex.get_citations
- fedlex.get_consultation_documents
- fedlex.get_consultations
- fedlex.get_drafts
- fedlex.get_fga_documents
- fedlex.get_law_metadata
- fedlex.get_memorial
- fedlex.get_modifications
- fedlex.get_oc_act
- fedlex.get_references
- fedlex.get_structure
- fedlex.get_subdivisions
- fedlex.get_taxonomy
- fedlex.get_treaty_info
- fedlex.list_annexes
- fedlex.list_expressions
- fedlex.list_versions
- fedlex.parse_reference
- fedlex.read_article
- fedlex.read_document
- fedlex.resolve_consolidation_at
- fedlex.resolve_sr
- fedlex.resolve_vocabulary_label
- fedlex.search_law
- fedlex.search_text
- i14y.api_status
- i14y.get_concept
- i14y.get_data_service
- i14y.get_dataset
- i14y.get_dataset_distributions
- i14y.list_catalogs
- i14y.list_concepts
- i14y.list_data_services
- i14y.list_datasets
- i14y.list_public_services
- i14y.list_publishers
- i14y.search_catalog
- i14y.search_codelist_entries
- lindas.describe
- lindas.describe_cube
- lindas.dimension_values
- lindas.find_cube
- lindas.list_cubes
- lindas.list_versions
- lindas.observations
- manifest.get
- meta.capabilities
- meta.schemas
- meta.tools
- publish.info
- standard.artifacts
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.