Skip to content

Connect Solorva to Claude and other assistants

Add Solorva to Claude, Cursor or any MCP client by signing in and approving, or with an API key.

Solorva has an MCP server, so an AI assistant can use it directly: list your brands, write on-brand posts, make images and decks, and check your credits, from inside the conversation. Anything that speaks MCP over HTTP can connect to it, including Claude, Cursor and n8n. The address of the server is: https://api.solorva.com/api/mcp Everything an assistant does through it is done as you: it uses your plan and your credits, and it is held to the same limits and spend cap as the dashboard. Connecting by signing in (recommended) Add the address above to the assistant with no key. The assistant opens a Solorva page where you sign in, see what it is asking for, choose the one workspace it may use, and approve. Nothing is shared until you do, and you can say no. The page tells you which app is asking and where its answers will be sent. If that is not the app you just added, deny it. A connection made this way works in one workspace only. To use another workspace, connect again and choose it. A connection made by signing in writes posts, ads, articles, research and decks, but does not make images: generating or editing pictures is not offered to connected apps. Make images in Solorva itself, or connect with an API key, which can. Claude In Claude, go to Customize → Connectors, select "+ Add", then "Add custom connector". Give it a name (for example Solorva), paste https://api.solorva.com/api/mcp as the server URL, and continue. Leave the request headers empty and choose to sign in; Claude then opens the Solorva approval page described above. Custom connectors are available on Claude's Free plan (one connector), and on Pro, Max, Team and Enterprise. On a Team or Enterprise plan an organisation owner adds the connector, and then each member connects it for themselves under Customize → Connectors. Solorva is not listed in Claude's connector directory, so add it as a custom connector as described here. Connecting with an API key instead Create a key in Solorva under Settings → API. It is shown once, so copy it when you make it. Tick "Start generations" only if the assistant should be able to spend credits; without it, it can read your brands and credits but not generate. The assistant sends the key with every request as a header: Authorization: Bearer sv_live_… A key works in every workspace on your account until you revoke it. Cursor, Claude Code and other MCP clients Cursor: add Solorva to ~/.cursor/mcp.json (or the project's .cursor/mcp.json) as a server with "url": "https://api.solorva.com/api/mcp", and Cursor offers to sign you in; or add "headers": { "Authorization": "Bearer sv_live_…" } to use a key. Claude Code: claude mcp add --transport http solorva https://api.solorva.com/api/mcp and then run /mcp to sign in; or add --header "Authorization: Bearer sv_live_…" to use a key. Any other client: use the server's address as a Streamable HTTP MCP endpoint. A client that supports MCP authorization finds Solorva's sign-in by itself; one that does not can send an API key in the Authorization header. Claude Desktop and clients that only start local servers: run Solorva's local server with the command npx -y solorva-mcp (Node.js 20 or later) and your API key in the SOLORVA_API_KEY environment variable. The package is solorva-mcp on npm. What a connection can do You choose, when you approve a connection or create a key: See brand profile and assets: read what Solorva knows about a brand.Change brand assets and branding: upload assets and set the header and footer on new graphics. Spends nothing.See generations and decks: collect finished work.Generate content: write posts, research and decks, and make images (with an API key only). This is the one that spends credits.See remaining credits. A connection never gets more than you approved, and it cannot add permissions later; it has to be connected again. Disconnecting In Solorva, Settings → API → Connected apps lists every app you connected by signing in: its name, where its answers go, the workspace, what it may do, when you connected it and when it was last used. Disconnect stops it at once. You can also remove the connector in the app itself (in Claude, Customize → Connectors, then Remove). Resetting your password disconnects every app connected by signing in, and so does an account being deactivated. API keys are not affected by either; revoke a key under Settings → API. Deleting your account removes all of them. If it does not work "Couldn't connect" or no tools appear: check the address is exactly https://api.solorva.com/api/mcp, with https and no trailing slash. Claude connects from Anthropic's servers, not from your computer, so this address works for it and a local or private address would not. The approval page says the request expired or was already answered: start again from the app. A request lasts 15 minutes and can be answered once. "Invalid API key" or "revoked": the key was mistyped, or was revoked. Create a new one; a key cannot be shown again. "Insufficient scope": the connection was not given the permission that action needs. Disconnect and connect again, granting it; permissions cannot be added afterwards. Out of credits, no plan, or the spend cap reached: the assistant reports the same message the dashboard would. Check Billing. A generation takes longer than the assistant waits: it carries on regardless. Ask the assistant to list your generations and collect it; nothing is charged twice. Administrator accounts cannot connect apps on Solorva itself. Use an ordinary account. Still stuck? Open a request under Support with the app's name and the exact message.