Connector setup and reference
This is the reference: the address, the steps and every tool. What the connector is for, with examples, is on Publish from Claude and ChatGPT. Solta's connector is a remote Model Context Protocol (MCP) server that lets Claude and ChatGPT publish, update and share sites on Solta from inside a conversation. Once it is added, you can say “put this on Solta” and get a link back, without copying anything anywhere.
1. Add the connector
It needs one thing, the server's address:
- Server URL
- https://mcp.solta.now/mcp
- Claude (web and desktop): Settings → Connectors → Add custom connector, then paste the address (Anthropic's steps).
- ChatGPT: turn on Developer mode (in Settings, under Apps & Connectors → Advanced), then create a connector and paste the address. Which ChatGPT plans allow custom connectors is OpenAI's to say, in their developer docs.
- Claude Code: run the line below, then
/mcpinside Claude Code to sign in.
claude mcp add --transport http solta https://mcp.solta.now/mcpThere is no key to paste. The client registers itself, sends you here to sign in, and you press Allow — the ordinary connector flow. What it is asking for is listed on that screen before you agree to it.
2. Say what you want
Things that work:
- “Publish this to Solta and give me the link.”
- “Update my pricing calculator with this version.”
- “What's in my Solta library?”
- “Has anyone commented on the invoice tool?”
Everything it can do
The model picks these itself from what you ask. Each is something you could do in Solta by hand, with the same permissions.
| Name | What it does |
|---|---|
| create_site | Publishes a file as a new site, with its own link, in your library or a workspace's. |
| get_source | Reads a site's code, so the model can change it. |
| update_site | Adds a new version to a site, as a draft; the link keeps serving the old one. |
| publish | Puts a version live at the same link. |
| request_review | Sends a version to an approver. |
| approve | Approves a version and puts it live. |
| list_sites | Lists the sites in your library or a workspace's, or the ones matching a search. |
| list_versions | Lists a site's versions and which one is live. |
| diff | Shows the source of two versions side by side. |
| get_comments | Reads what people said on one version: the live one, or a draft by its number. |
| get_analytics | Reads how a site was viewed: views, visitors, countries, devices, pages and referrers. |
| reply_comment | Replies to a comment, on the version it was left on. |
| set_access | Changes who can open a site: public, unlisted, password, invited, team or private. |
| link_chat | Links a site to the conversation it was made in, so Solta can open it again. |
| set_visitor_ai | Lets visitors use their own AI through OpenRouter, paid by them. |
| set_installable | Lets people install a site as an app on their phone or computer. |
| get_embed | Gives the snippet that puts a site on your website. |
| remix | Copies a site into your library or a workspace's, with a new link: one somebody shared for remixing, or one of your own. |
| move_site | Moves a site to a workspace, or back to your personal library, keeping its link, versions and comments. |
| list_workspaces | Lists your personal library and the workspaces you belong to, with your role and plan in each. |
| export | Gives a link to download a version's files. |
| whoami | Says which Solta account the connector is signed in as, and which workspaces it is in. |
What it will and won't do
An update is a draft. When you ask for a change to an existing tool, the new version is saved but the link keeps serving what it served before. Nothing anyone has open changes until you say publish. That is deliberate: a link you have given to fifty people should not change because a model decided it was finished.
It will not make a second copy of your tool. If it cannot find the tool you named, it stops and asks rather than creating a new one with a new link.
It will not publish your secrets. Files are scanned for API keys and passwords before anything is stored, and a file that contains one is refused.
Taking it back
Settings → Connected apps lists everything you have allowed and when it was last used. Disconnecting takes effect immediately, on every token that app holds.
Without a connector
If your client cannot do the connector flow — or you are writing a script — create a key at Settings → API keys and send it as Authorization: Bearer …. It is shown once.
Either way it is the ordinary Solta API. There is no separate agent-only path into your account, which is the point — an agent cannot reach anything you could not reach yourself.