council_licensing — Lettance MCP Tool
council_licensing
(council licensing) is one of 4 tools on the
Lettance
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call council_licensing from your client
- Claude Code Lettance council_licensing run in your project directory
- Claude Desktop Lettance council_licensing ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Lettance council_licensing ~/.cursor/mcp.json
- VS Code Lettance council_licensing .vscode/mcp.json
- Zed Lettance council_licensing ~/.config/zed/settings.json
- Windsurf Lettance council_licensing ~/.codeium/windsurf/mcp_config.json
- Cline Lettance council_licensing ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Lettance council_licensing ~/.gemini/settings.json
- Grok Lettance council_licensing .mcp.json (in your project root)
- ChatGPT Lettance council_licensing Settings → Connectors → Advanced → Developer mode
- Claude.ai Lettance council_licensing Settings → Connectors → Add custom connector
- LangChain Lettance council_licensing pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http rules https://lettance.com/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 14 October 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.