Your agent's data, without the dump.
Caveman Connect gives an agent token-efficient access to 850+ connectors — OAuth apps, MCP servers, REST APIs and your own functions — as one tool on the wire instead of a catalog in the prompt.
git clone https://github.com/JuliusBrussee/agent-sdk.git- reach
- 850+ connectors through Caveman Connect
- kinds
- OAuth apps, MCP servers, REST APIs, your own functions
- on the wire
- one bounded tool, not the catalog
- every call
- typed, capped, metered, abortable
- after the run
- one receipt: calls, cost basis, stop reason, resume state
@caveman-ai/agent v0.2 documents current main and is not on npm yet — clone the repo to test it.
Retrieval answers by the pound. You pay for every token.
Recall improves as the pile grows, so the pile grows — and it all rides in the prompt.
Every turn after the fetch carries all of it forward again, at full price.
Neighbouring chunks, repeated headers, whole documents fetched for a single field.
Anything in. One schema on the wire, one tool out.
- 850+ connectors
- Caveman Connect reaches OAuth apps, MCP servers, REST APIs and your own functions from inside the Agent SDK. Anything in.
- one schema on the wire
- The catalog does not ride in the prompt. The model sees one bounded tool and reaches what it needs from inside it.
- typed and capped
- Every call is validated against its schema, budgeted, metered and abortable — the smaller wire is not a looser one.
- on the receipt
- Every run hands back one receipt: model calls, tool calls, subagents, catalog cost basis, stop reason and resume state.
The shape of it. Your tools, your keys, one tool out.
OAuth apps · MCP servers · REST APIs · your keys
your loop, exact-pinned adapters
850+ connectors are reachable through Caveman Connect. The marks above stand for the tools you already run and the keys you already hold — they are an illustration, not an endorsement or an integration claim.
What powers it.
Connect the data.
Skip the dump.
git clone https://github.com/JuliusBrussee/agent-sdk.git@caveman-ai/agent v0.2 documents current main and is not on npm yet, so clone the repo to test it. Token reductions from the local proxy are estimates labeled inferred, never verified savings.