Two minutes. That’s all it takes to give your AI access to 100,000+ API operations.
Toolcoghttps://mcp.toolcog.comClaude will prompt you to sign in when it connects.
For other clients, see AI Clients.
Open a new conversation and try something:
“What GitHub operations are available for working with issues?”
Claude will use Toolcog to discover relevant operations—github/createIssue, github/updateIssue, github/listIssues, and more. No configuration. No API keys yet. Just ask.
Try another:
“Show me what parameters I need to create a Stripe customer.”
Claude discovers the operation, retrieves the interface, and shows you exactly what’s required. This works because discovery and learning don’t require authentication—AI is just reading API specifications.
Now ask Claude to actually do something:
“Create a GitHub issue in my repo called ‘Test from Toolcog’”
This time, Claude needs your GitHub credentials. Instead of failing, it responds with something like:
“I need authorization to access GitHub. Click here to connect: [authorization link]”
Click the link. You’ll be taken through GitHub’s OAuth flow. Grant permission, and you’re redirected back. Now try again—the issue gets created.
That’s it. You just gave AI the ability to discover, learn, and execute any API operation, with authentication that happens seamlessly when needed.
Behind the scenes, Claude used three API meta-tools:
find_api — Searched 100,000+ operations to find what you neededlearn_api — Retrieved the TypeScript interface for the operationcall_api — Executed the operation with your credentialsYou didn’t configure which APIs to use. You didn’t specify which operations were available. You asked Claude to do something, and the system figured out the rest.