What teams use Toolspoke for
Each of these has its own page that explains how it works.

Agents that work in your projects
Build an agent with instructions, toolkits and skills, install it into a project, then chat with it or give it a scheduled routine.
Read: Agents that work in your projectsAccess that follows your team
A project decides which of a toolkit's actions it allows, a connection key gets a slice of that, and both are checked when the call arrives.
Read: Access that follows your teamAccurate tool choice in a large catalog
Toolspoke sends a searchable index instead of every schema, so the model chooses from a shortlist it can reason about.
Read: Accurate tool choice in a large catalogA gateway on your own infrastructure
Docker Compose and PostgreSQL 17, two secrets to set, and no dependency on our servers once it is running.
Read: A gateway on your own infrastructureA record of every agent call
Every call writes a row: the person behind the key, the client, the arguments, the result, and where the time went.
Read: A record of every agent call
Coming from somewhere else?
Self-hosting, credential handling and the audit log, compared directly against Composio, Pipedream MCP, Smithery and Zapier MCP.
Try it on one job
If what you are trying to do is not one of these, the integration catalog and the documentation are the fastest way to find out whether it fits.