API to MCP

Definitely adds a lot of value. How do you handle auth scopes when different agents should get different tool access, like read-only CRM vs write/update access?

This solves a real headache. Setting up MCP servers from scratch for every API is tedious, so being able to just point it at a REST or GraphQL API and have it generate the server automatically is a big time saver. Does it handle authentication flows like OAuth or API keys automatically too, or is that something you configure manually?

Can you pin a snapshot version for an agent so updates don’t change behavior mid workflow?

This is a really amazing use case. Can it support internal microservices spec like grpc?

The live vs forked MCP split is the right product question. I’d be curious how you want teams to carry policy with the fork: allowed actions, credential scope, approval rules, and a receipt after a write. Otherwise the fork solves setup, but production teams still have to prove what an agent changed.

One API for the whole WhatsApp Business stack, calls included, is exactly what I wished existed last time I built on WhatsApp. The hosted MCP server is a great touch for agents. Congrats on the launch!

Wrapping heterogeneous APIs behind a unified MCP layer is a smart abstraction. The hardest part isn't the HTTP adapter. It's auth propagation across OAuth, API keys, and custom schemes without leaking secrets into agent contexts. We've hit this friction proxying third-party integrations in multi-tenant setups. How do you handle token refresh when an OAuth TTL expires mid agent tool call?

This solves a real bottleneck: business systems already have APIs, but agents need a safer execution layer. Curious how you handle permission boundaries. Can an MCP server expose different actions by role, for example read-only CRM access for one agent and write/update access for another?

Hey! 👋Congrats on the launch of API to MCP! 🚀I really like how you're helping developers bridge existing APIs into the MCP ecosystem. With AI agents becoming more capable, reducing the friction between APIs and MCP tools feels incredibly timely and useful.We're also launching Blazly Backlinker today, helping marketers automate backlink discovery, outreach, and guest posting from a single workflow.Would love to hear your thoughts if you get a chance to check us out as well. Wishing you a fantastic launch day! 🎉

Congrats on the launch! 🎉 I gave API To MCP a try and was genuinely impressed. Setup was surprisingly simple, everything worked smoothly out of the box, and the overall experience was very polished. Turning APIs into MCP servers has never felt this easy. Great work to the whole team and wishing you a successful launch! 🚀

The forkable snapshots idea feels useful. Teams may want to try a live MCP quickly, but still need control over credentials, auth, and mappings before using it seriously.

Hey Product Hunt 👋I built API To MCP because AI agents are getting smarter, but connecting them to real business APIs is still too hard.Most teams already have valuable systems: CRMs, ERPs, support tools, finance dashboards, internal APIs, and SaaS platforms like Google, Meta, GitHub, Notion, Shopify, and Slack. But turning those APIs into something ChatGPT, Claude, Codex, Cursor, VS Code, Antigravity, or custom agents can actually use often requires custom engineering.API To MCP helps you turn REST or GraphQL APIs into hosted MCP servers.You can build visually from the dashboard, or connect the API To MCP Manager MCP to an AI coding agent and let it create, test, deploy, and update MCP servers from chat.Today it supports:- Hosted remote MCP URLs- REST and GraphQL APIs- API Key, Bearer, Basic Auth, OAuth2 Client Credentials, and per-user OAuth- Workflow tools and JMESPath response mapping- Live MCP servers and forkable snapshots- Public MCP directoryI’ve worked hard to make the product stable for launch day, but this is still an early version. If you run into any issues while trying it, I’d really appreciate your feedback.I’d love to hear:1. What API would you turn into an MCP server first?2. Would you rather use a live MCP directly, or fork a snapshot and add your own credentials?3. What would make this easier for non-technical users?As a launch thank-you, all paid plans are 30% off during the Product Hunt launch period.Thanks for checking it out. I’ll be here all day answering questions.