Skip to content
FeaturesAPIDocs
Docs

Ground your agents.
Search your workspace.

Authenticated REST tools give agents access to workspace retrieval. Set DOCSLURP_URL to your service origin and DOCSLURP_API_KEY to a service key from API keys.

Discover available tools

curl "$DOCSLURP_URL/v1/mcp/tools" \
  -H "Authorization: Bearer $DOCSLURP_API_KEY"

Search workspace documents

curl -X POST "$DOCSLURP_URL/v1/mcp/tools/workspace.search" \
  -H "Authorization: Bearer $DOCSLURP_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"workspaceId":"workspace-id","q":"auto renewal clause"}'

workspace.search accepts workspaceId, q, and an optional limit. It requires a key with search scope and returns tool, sessionId, and results. The REST paths retain /v1/mcp naming; they are HTTP tool endpoints rather than a hosted MCP transport URL.

Experimental CLI bridge

The repository CLI includes a stdio MCP bridge for local agent integrations. Build the CLI package and run its docslurp command with DOCSLURP_API_KEY in the environment. This bridge is experimental; a hosted MCP endpoint is not available.

docslurp mcp-server --api-url "$DOCSLURP_URL"

For an existing chat client, use OpenAI-compatible workspace chat. For document upload and retrieval, see the SDK quickstart.