Connecting AI to Your Vibe
Give any MCP client access to your vibe's tools
Last updated: August 2026
What is MCP?
The Model Context Protocol (MCP) is an open standard that lets AI assistants discover and use tools exposed by external services. When your vibe has a backend, its annotated functions are automatically registered as MCP tools — any compatible client can connect and interact with your vibe's data.
Finding your MCP endpoint
Every full-stack vibe serves MCP at:
https://{your-username}--{vibe-name}.vibe-coded.ai/mcp
For example:
https://alice--recipe-book.vibe-coded.ai/mcp
This endpoint speaks Streamable HTTP, the current MCP transport — it's the URL to use in every client below.
claude.ai (web and mobile)
- Open Settings → Connectors.
- Click Add custom connector.
- Enter a name and paste your vibe's
/mcpURL. - If the vibe requires login, your browser opens an approval page — sign in with your vibe-coded.ai account and approve.
Your vibe's tools appear in the tools menu for new chats. If you change your vibe's tools, disconnect and reconnect the connector to refresh the list.
Claude Desktop
Claude Desktop uses the same Connectors UI: Settings → Connectors → Add custom connector, then paste the /mcp URL. Private vibes trigger the same browser-based OAuth approval.
Claude Code
Add your vibe from the command line:
claude mcp add --transport http recipe-book \
https://alice--recipe-book.vibe-coded.ai/mcp
Or declare it in your project's .mcp.json:
{
"mcpServers": {
"recipe-book": {
"type": "http",
"url": "https://alice--recipe-book.vibe-coded.ai/mcp"
}
}
}
Check the connection with claude mcp list. If the vibe requires login it shows Needs authentication — run /mcp inside a Claude Code session to complete the OAuth flow.
Authentication: Public vibes connect without an account. Private and login-required vibes walk you through an OAuth approval in your browser the first time you connect. What the AI can then do follows your role on the vibe — owners, admins, and writers get write tools; viewers get read-only. See OAuth for MCP.
Other MCP clients
Any client that supports remote MCP servers over Streamable HTTP can connect with the same /mcp URL — in Cursor, for example, add it under mcpServers in ~/.cursor/mcp.json with a "url" key. Older clients that only speak the SSE transport can use /mcp/sse.
| Transport | Endpoint | Best for |
|---|---|---|
| Streamable HTTP | /mcp |
All current clients (recommended) |
| SSE | /mcp/sse |
Legacy clients that predate Streamable HTTP |
Using AI with your vibe's data
Once connected, your AI assistant can interact with your vibe's data in powerful ways. Here are some examples of what you can do:
Data entry and updates
Add data to your vibe through natural conversation:
"Add a new contact: Jane Smith, jane@example.com,
VP of Engineering at Acme Corp"
"Update the status of the 'Website Redesign' project
to 'In Progress' and set the due date to next Friday"
Querying and analysis
Ask questions about your data and get insights:
"What are my overdue tasks this week?"
"Show me all leads in the pipeline that haven't been
contacted in the last 30 days"
"Summarize the inventory items that are running low"
Working with images and documents
If your AI client supports vision (like Claude), combine it with your vibe's tools:
"Here's a photo of a business card [image]. Add this
person as a new contact in my CRM."
"I'm looking at this receipt [image]. Log the expense
in my tracker with the date and amount."
Downstream actions
Use insights from your vibe's data to take action elsewhere:
"Look at my overdue tasks and draft a status update
email to my team summarizing what's behind schedule"
"Check my event RSVPs and create a seating chart
based on the guest list and dietary preferences"
"Review this week's sales pipeline and suggest which
leads I should follow up with first"
Key idea: Your vibe's data becomes a building block. AI can read from it, write to it, and combine it with other tools and context to accomplish complex tasks.