DocsMCP server

Connect your editor.
Ship from inside it.

ShareBase runs an MCP server, so the agent that wrote the app can also put it on the internet, name who may open it, and roll a bad deploy back — without you opening another tab.

Claude Code

Cursor

VS Code

Codex

Zed

ShareBase MCPConnected

One URL. The client reads it, sends you to a consent screen, and the tools appear.

https://api.sharebases.com/mcp

Live at its own addressOpened by the people you named

Your agent already writes the app.
Now it can hand it over.

Building was never the hard part. What follows it is: somewhere to run, an address, a login, and the decision about who may open it. Connected over MCP, all of that is something your agent can just do.

You ask, in the editor

“Deploy this and give Priya access.”

The agent calls the tools

Builds it, hosts it, names the people.

You get a URL back

Behind your team’s login, ready to send.

It runs as you, and nothing more

An agent connected to ShareBase reaches exactly what you can reach and nothing else, and every action it takes shows up in your activity log like any other. You need an account in a workspace first — connecting before that authorizes fine and then finds nothing to work on.

Your apps and their sourceGiven

Deploys, versions and rollbacksGiven

Sharing, folders and invitesGiven

The org-wide overviewAdmins only

A data domain no policy coversDenied

Connect the client you already open

A client that speaks OAuth needs nothing but the URL: it reads the discovery document, registers itself, and sends you to the consent screen. Nothing is copied into a config file, and nothing runs on your machine.

Claude Code

Run this anywhere, then /mcp → sharebases → Authenticate. Add -s user to make it available in every project.

terminal

claude mcp add --transport http sharebases https://api.sharebases.com/mcp

Cursor

Add the server to ~/.cursor/mcp.json. Cursor opens the browser for you the first time.

~/.cursor/mcp.json

{
  "mcpServers": {
    "sharebases": {
      "url": "https://api.sharebases.com/mcp"
    }
  }
}

VS Code

Same shape, different key — VS Code calls them servers.

.vscode/mcp.json

{
  "servers": {
    "sharebases": {
      "type": "http",
      "url": "https://api.sharebases.com/mcp"
    }
  }
}

Antigravity

It sends a header rather than opening a browser, so it needs a token from Settings → Script tokens.

mcp_config.json

{
  "mcpServers": {
    "sharebases": {
      "serverUrl": "https://api.sharebases.com/mcp",
      "headers": {
        "Authorization": "Bearer crt_your_token_here"
      }
    }
  }
}

Anything else

Server URL https://api.sharebases.com/mcp, transport Streamable HTTP (not SSE, not stdio). The server is its own authorization server — discovery at https://api.sharebases.com/.well-known/oauth-protected-resource/mcp, dynamic client registration supported, one scope: workspace. Or send Authorization: Bearer crt_….

Scripts and CI get their own token

Where there is no browser to open, create a token in Settings → Script tokens and send it as a bearer header. Only a hash is stored, so copy it before you close the panel — and if you lose it, revoke it and make another. Revocation is immediate.

Check it from a terminal

A healthy server answers with its tool list. A 401 means the token is wrong, revoked, or missing.