Website templates with tested build prompts for Claude Code, Codex and Cursor.
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Bearer vs_... access key, shown after signing in at vibesignet.com. Only get_prompt needs it.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
The full build prompt for one component. Needs the access key of a paid Vibesignet plan (Monthly, Yearly or Founders), sent as the Authorization header or as access_key. Components have their own allowance (15 new in any 30 days on Monthly) and never use a template unlock; fetching one again is free.
The component id from search_components, for example "ripple".
The user's access key (starts with vs_), if it was not set on the connection.
This tool isn't marked read-only, so it may change something on the server or in an account you connected.
Pick your client. Values in capitals, like YOUR_TOKEN, are yours to fill in.
Run in a terminal
claude mcp add --transport http templates https://vibesignet.com/api/mcp
Headers
Authorization (optional, not in the config above): Bearer vs_... access key, shown after signing in at vibesignet.com. Only get_prompt needs it.The full build prompt for one component. Needs the access key of a paid Vibesignet plan (Monthly, Yearly or Founders), sent as the Authorization header or as access_key. Components have their own allowance (15 new in any 30 days on Monthly) and never use a template unlock; fetching one again is free.
| Argument | Type | Description |
|---|---|---|
| id* | string | The component id from search_components, for example "ripple". |
| access_key | string | The user's access key (starts with vs_), if it was not set on the connection. |
{
"type": "object",
"required": [
"id"
],
"properties": {
"id": {
"type": "string",
"description": "The component id from search_components, for example \"ripple\"."
},
"access_key": {
"type": "string",
"description": "The user's access key (starts with vs_), if it was not set on the connection."
}
}
}The full build prompt for one template. Needs the user's Vibesignet access key, sent as the Authorization header of this connection or as the access_key argument. A free key unlocks 1 template of the user's choice; fetching it again is free.
| Argument | Type | Description |
|---|---|---|
| key* | string | The template key, for example "kestrel". |
| access_key | string | The user's access key (starts with vs_), if it was not set on the connection. |
{
"type": "object",
"required": [
"key"
],
"properties": {
"key": {
"type": "string",
"description": "The template key, for example \"kestrel\"."
},
"access_key": {
"type": "string",
"description": "The user's access key (starts with vs_), if it was not set on the connection."
}
}
}One template's public details: what it is for, its sections in order with a one-line summary each, how many photographs and films the build needs, and its page on vibesignet.com. No access key needed.
| Argument | Type | Description |
|---|---|---|
| key* | string | The template key from search_templates, for example "kestrel". |
{
"type": "object",
"required": [
"key"
],
"properties": {
"key": {
"type": "string",
"description": "The template key from search_templates, for example \"kestrel\"."
}
}
}Search the Vibesignet components: single scenes, backgrounds, interactions and sections, each one standalone, to drop into an existing site. Returns each component's id, kind and one line. No access key needed. Call with no arguments to list them all.
| Argument | Type | Description |
|---|---|---|
| query | string | Words to match against the name, kind and description, for example "ripple" or "scroll gallery". |
{
"type": "object",
"properties": {
"query": {
"type": "string",
"description": "Words to match against the name, kind and description, for example \"ripple\" or \"scroll gallery\"."
}
}
}Search the Vibesignet template library. Returns matching templates with their key, sector, look and a one-line description. No access key needed. Call with no arguments to list every template.
| Argument | Type | Description |
|---|---|---|
| look | string | Limit to light, mid-tone or dark templates. |
| query | string | Words to match against the name, sector, product and description, for example "flight school" or "watch". |
| sector | string | Limit to one sector, for example "Hospitality". |
{
"type": "object",
"properties": {
"look": {
"enum": [
"light",
"mid",
"dark"
],
"type": "string",
"description": "Limit to light, mid-tone or dark templates."
},
"query": {
"type": "string",
"description": "Words to match against the name, sector, product and description, for example \"flight school\" or \"watch\"."
},
"sector": {
"type": "string",
"description": "Limit to one sector, for example \"Hospitality\"."
}
}
}We read every tool's name, description and inputs the way the model will, looking for instructions hidden from you. A clean result means no warning signs, not a guarantee. Scanned Nov 16, 2026.
No readOnlyHint / destructiveHint annotations, so clients can't tell a read from a write without asking.
Fix: Add annotations to each tool, e.g. { readOnlyHint: true } for tools that only read.