docspeed-ai/docspeed-agent-tools

Connect Codex or Claude Code to Docspeed's hosted document tools and install the companion docspeed-documents skill. Use your existing agent to extract fields, read documents, answer cited questions, compare document values, or build a reusable Docster workflow.
This MIT-licensed repository contains client integration assets, not the Docspeed server or a local/offline document engine. Public setup guide · API documentation · Recorded examples
Connect with an installed client
The public guide now provides direct setup without downloading this repository or installing Python. Use a macOS or Linux terminal with Bash or zsh, in your document project. Choose this route **or** the repository installer below. If you already customized the companion skill, use the repository installer's conflict checks instead of overwriting it with these download commands.
With your account API key ready, read it at the hidden prompt in the same terminal that will install and launch the client:
The key stays in the terminal environment; it is not saved in command history or client configuration. A separately launched desktop app does not inherit it automatically.
For **Codex**, add the native connection and download the companion skill and upload helper:
This registers the server in your user configuration and the skill in the current project. Start a fresh session from the same terminal:
For **Claude Code**, register the connection and skill in the current project:
Keep the single quotes around the header so the configuration stores the environment variable name, not its value. Launch from the same terminal:
Follow the client's normal project trust and MCP approval prompts, then inspect /mcp inside the session. These commands configure the connection; they do not bypass permission prompts, upload a document, prove model entitlement, or guarantee tool selection. Python is only needed for the optional direct-upload helper and repository installer described below.
Install from this repository
You need Python 3.10 or later, an installed Codex or Claude Code client, and a Docspeed API key from your account dashboard. Make DOCSPEED_API_KEY available to the process that launches your client. Do not paste the key into chat, commit it, or pass it as a command argument. A desktop client must receive the environment variable too.
Download or clone this repository, then open a terminal in its root directory. Python 3.11+ needs no additional package. On Python 3.10 only:
Install the connection and skill into an **existing** project, replacing the example path:
For Claude Code, use --client claude. This local install does not upload or process documents. It preserves other configured servers and client approval settings; conflicting Docspeed configuration or a modified skill stops the install for manual review.
Start a new agent session in that project, complete the client's normal project/MCP trust prompts, and inspect /mcp. Installation alone does not inject tools into an already-running conversation or guarantee tool selection.
With your key set, check the real connection:
The check initializes MCP and lists its tools; it makes no document-processing or model call. Success proves connection and discovery of the checker's required core tools, not every operation, sufficient balance, output quality, or completed workflows. For the four Docster tools specifically:
The canonical MCP endpoint is https://api.docspeed.ai/mcp/, including the trailing slash. The checker rejects redirects rather than forwarding credentials to another origin. It reports errors explicitly and does not switch providers.
Try a document task
Use a document you are authorized to send to Docspeed: