extract_contract_from_url — transaction coordinator MCP Tool
extract_contract_from_url
(extract contract from url) is one of 11 tools on the
transaction coordinator
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call extract_contract_from_url from your client
- Claude Code transaction coordinator extract_contract_from_url run in your project directory
- Claude Desktop transaction coordinator extract_contract_from_url ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor transaction coordinator extract_contract_from_url ~/.cursor/mcp.json
- VS Code transaction coordinator extract_contract_from_url .vscode/mcp.json
- Zed transaction coordinator extract_contract_from_url ~/.config/zed/settings.json
- Windsurf transaction coordinator extract_contract_from_url ~/.codeium/windsurf/mcp_config.json
- Cline transaction coordinator extract_contract_from_url ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI transaction coordinator extract_contract_from_url ~/.gemini/settings.json
- Grok transaction coordinator extract_contract_from_url .mcp.json (in your project root)
- ChatGPT transaction coordinator extract_contract_from_url Settings → Connectors → Advanced → Developer mode
- Claude.ai transaction coordinator extract_contract_from_url Settings → Connectors → Add custom connector
- LangChain transaction coordinator extract_contract_from_url pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http transaction-coordinator https://primacoda.halinc.tech/mcpOther tools on this server
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.