Free TypeScript SDK for building agentic AI apps — with instant access to MCP servers. Use Cases: Connect your AI agents and automation workflow apps with over 5000 MCP servers and AI tools, all in just one line of code.
👋 Hello World, I’m Kelly, maker of ToolSDK.ai - a free TypeScript SDK for connecting MCP servers to your agentic AI apps.
If you’re a developer of AI agents or automation apps, you’ve probably felt the pain of integrating and managing multiple MCP servers.
It’s messy, hard to deploy, and doesn’t scale easily.
ToolSDK.ai makes it simple — connect to over 5,000 MCP servers and AI tools with just one line of code.
Here’s what you can do with ToolSDK.ai:
⚡ Access running MCP server with OpenAI SDK or Vercel AI SDK in single line of code
🤖 Build AI agents that tap into a 10k+ MCP server ecosystem in just one day
🛠 Create automation workflows apps (like Zapier, n8n, or Make.com) with forms powered by MCP ecosystem.
You can also add your own MCP servers through the GitHub registry: https://github.com/toolsdk-ai/aw...
Would love your feedback — and excited to see what you build! 🚀
@masump Yes! In addition to MCP Tools, we've also built a UI Form system based on the MCP schema and fields — so you can create Zapier- or n8n-style automation forms directly, powered by the MCP ecosystem.
Wow! This is super useful. Curious how ToolSDK manages tool discovery and compatibility across 5,000+ MCP servers. Is there a unified schema or standard each tool must follow for inputs/outputs, or do developers have to write adapters to ensure their agents can interact smoothly with different services?
@lak7 Thanks for the question! Instead of a unified schema, each MCP server is standalone and use its own unique key—similar to how Zapier works. This way, you can connect directly to each server using its specific identifiers, keeping things flexible while maintaining compatibility across the ecosystem. Let me know if you'd like more details! 😊
ToolSDK.ai
@mrkelly This could drastically cut down build time for automation platforms
ToolSDK.ai
@masump Yes! In addition to MCP Tools, we've also built a UI Form system based on the MCP schema and fields — so you can create Zapier- or n8n-style automation forms directly, powered by the MCP ecosystem.
Wow! This is super useful.
Curious how ToolSDK manages tool discovery and compatibility across 5,000+ MCP servers. Is there a unified schema or standard each tool must follow for inputs/outputs, or do developers have to write adapters to ensure their agents can interact smoothly with different services?
ToolSDK.ai
@lak7 Thanks for the question! Instead of a unified schema, each MCP server is standalone and use its own unique key—similar to how Zapier works. This way, you can connect directly to each server using its specific identifiers, keeping things flexible while maintaining compatibility across the ecosystem. Let me know if you'd like more details! 😊
Adsby
I’ll definitely take a detailed look at this, it looks great!
ToolSDK.ai
@cem_ozcelik Appreciate it, Cem! Hope you find it useful — feel free to reach out if you run into anything or have ideas to share! 🚀