BYOC
Bring your own credentials. One MCP server for every SaaS.
https://byo.dev/Connect straight to this server’s public endpoint.
https://mcp.byo.dev/We add this server to your workspace, walk through sign-in once, then open Studio with tools ready to run.
Last probed Sep 14, 2026 · mcp.byo.dev
Get your MCP into directories
A working endpoint is step one. Directory coverage is the coordinated launch across ChatGPT, Claude, Cursor, the MCP Registry, and community indexes.
Directory coverage for brandsBring your own credentials. One MCP server for every SaaS.
Use the remote MCP URL on this page in your MCP client (Claude, Cursor, VS Code, and more). Copy the endpoint if your client needs a manual entry, then complete provider sign-in when your client connects — tools appear after authentication.
This endpoint requires provider sign-in, so MCPBundles could not list tools anonymously during the last probe. After you connect and authenticate in your MCP client, your session should receive the live tool list from the provider.
BYOC may require signing in to the provider before tools can run. Connect through MCPBundles or your MCP client and complete any provider login when prompted.
Operate BYOC? Verify ownership to take over this directory entry.
This server appears in the MCPBundles directory. Verify you operate it to take over the listing — name, description, logo, contact email, and skill content. We email a 6-digit code to a maintainer address your server publishes in /.well-known/security.txt or /.well-known/mcpbundles.json. Free, takes about a minute.
MCPBundles is an independent platform built on the open Model Context Protocol standard. Not affiliated with Anthropic PBC or Claude.