Design
vikka.studio
Helps users explore Vikka’s website design services and completed work, then draft a project brief with contact links for review.
ENDPOINT 1
https://www.vikka.studio/.well-known/mcp
MCP server metadata
- Name
- vikka
- Version
- 1.0.0
Use Vikka for custom website projects in Latin America. Read services and selected work before preparing a brief. Never invent prices, dates, availability, guarantees, or results. prepare_project_brief only drafts contact material; it never sends a message.
Known tools 3
get_servicesList the website project types Vikka offers and the situations each one fits.
Inferred read-onlyget_selected_workReturn the public projects Vikka is allowed to present as completed work.
Inferred read-onlyprepare_project_briefDraft a concise website project brief plus email and WhatsApp links for user review.
Potential side effectsCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.vikka]
url = "https://www.vikka.studio/.well-known/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"vikka": {
"type": "http",
"url": "https://www.vikka.studio/.well-known/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: vikka
Remote MCP URL: https://www.vikka.studio/.well-known/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"vikka": {
"url": "https://www.vikka.studio/.well-known/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"vikka": {
"type": "http",
"url": "https://www.vikka.studio/.well-known/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "vikka",
"transport": "streamable-http",
"url": "https://www.vikka.studio/.well-known/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.