define_term — Lexiara MCP Tool
define_term
(define term) is one of 25 tools on the
Lexiara
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call define_term from your client
- Claude Code Lexiara define_term run in your project directory
- Claude Desktop Lexiara define_term ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Lexiara define_term ~/.cursor/mcp.json
- VS Code Lexiara define_term .vscode/mcp.json
- Zed Lexiara define_term ~/.config/zed/settings.json
- Windsurf Lexiara define_term ~/.codeium/windsurf/mcp_config.json
- Cline Lexiara define_term ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Lexiara define_term ~/.gemini/settings.json
- Grok Lexiara define_term .mcp.json (in your project root)
- ChatGPT Lexiara define_term Settings → Connectors → Advanced → Developer mode
- Claude.ai Lexiara define_term Settings → Connectors → Add custom connector
- LangChain Lexiara define_term pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http lexiara https://lexiara.org/mcpOther tools on this server
- search
- fetch
- lookup_provision
- search_legislation
- provision_context
- work_glossary
- term_languages
- provisions_by_concept
- related_works
- work_mentions
- provision_history
- find_national_implementations
- guidance_for_provision
- list_topics
- get_topic
- recent_changes
- list_review_queue
- list_follows
- follow_updates
- get_coverage
- request_ingestion
- list_ingestion_requests
- get_ingestion_request
- get_ingestion_result
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.