Connecting AI to Your Vibe

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://you--my-vibe.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)

1. Open Settings → Connectors.
2. Click Add custom connector.
3. Enter a name and paste your vibe's /mcp URL.
4. 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

If you built the vibe with the vibe CLI, run this in its folder:

vibe connect

It creates a token that can only call this vibe's tools, and runs claude mcp add for you, so the vibe is available in all your Claude Code projects. There's no browser step. The tools load in your next Claude Code session, and claude mcp list shows it as connected. The token lasts until your CLI login expires (30 days after vibe login). Run vibe connect again to renew it, which also revokes the old one. vibe connect --revoke removes access, and vibe connect --print shows the command without running it.

To connect a vibe you didn't build, or without the CLI, add it from the command line and sign in once:

claude mcp add --transport http my-vibe \
  https://you--my-vibe.vibe-coded.ai/mcp

Or declare it in your project's .mcp.json:

{
  "mcpServers": {
    "my-vibe": {
      "type": "http",
      "url": "https://you--my-vibe.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.

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. Clients that only speak the older SSE transport are not supported.

Transport	Endpoint	Best for
Streamable HTTP	/mcp	All current clients

The older SSE transport (/mcp/sse) is retired and answers 410 Gone. Point the client at /mcp instead.

Test the endpoint with curl

An MCP request is a JSON-RPC POST to /mcp. Without signing in, this works only on a vibe whose interaction policy is “Anyone can read; only invited people can edit” or “Anyone”; otherwise add -H "Authorization: Bearer <token>" from an OAuth sign-in. List the tools:

curl -s -X POST https://you--my-vibe.vibe-coded.ai/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -H 'MCP-Protocol-Version: 2026-07-28' \
  -H 'Mcp-Method: tools/list' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{"_meta":{"io.modelcontextprotocol/protocolVersion":"2026-07-28"}}}'

Call one (the Mcp-Name header repeats the tool name):

curl -s -X POST https://you--my-vibe.vibe-coded.ai/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -H 'MCP-Protocol-Version: 2026-07-28' \
  -H 'Mcp-Method: tools/call' -H 'Mcp-Name: list_notes' \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"_meta":{"io.modelcontextprotocol/protocolVersion":"2026-07-28"},"name":"list_notes","arguments":{}}}'

The response comes back as server-sent events: an event: message line, then a data: line holding the JSON-RPC result. The tool's own output is the text in result.content[0].text. As the owner, vibe call list_notes does the same thing in one line.

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"