url.extract — api MCP Tool
url.extract
(url extract) is one of 22 tools on the
api
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call url.extract from your client
- Claude Code api url.extract run in your project directory
- Claude Desktop api url.extract ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor api url.extract ~/.cursor/mcp.json
- VS Code api url.extract .vscode/mcp.json
- Zed api url.extract ~/.config/zed/settings.json
- Windsurf api url.extract ~/.codeium/windsurf/mcp_config.json
- Cline api url.extract ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI api url.extract ~/.gemini/settings.json
- Grok api url.extract .mcp.json (in your project root)
- ChatGPT api url.extract Settings → Connectors → Advanced → Developer mode
- Claude.ai api url.extract Settings → Connectors → Add custom connector
- LangChain api url.extract pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http api https://api.docimprint.com/mcpOther tools on this server
- document.extract_text
- document.extract_tables
- document.parse_invoice
- document.check_claims
- document.extract_structured
- document.summarize
- bundle.verify
- collection.create
- collection.search
- collection.ask
- url.summarize
- url.qa
- url.translate
- bundle.get
- bundle.notarize
- receipt.verify
- receipt.list
- job.status
- collection.list
- collection.add_document
- account.quota
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.