Skip to main content
The Semji MCP server is hosted at:
https://mcp.semji.com/mcp
The first time you connect, your assistant opens a browser window to sign in to Semji. If your account belongs to more than one organization, you then choose which organization to grant access to. Access is scoped to that organization and to your existing workspace permissions. You need a Semji account with access to at least one workspace.
Semji is not (yet) available as a one-click app inside Claude or ChatGPT. You add it manually as a custom MCP server using the URL above. The steps below cover that.

Claude

Claude Code (CLI)

Add the server, then authenticate from inside Claude Code:
claude mcp add --transport http semji https://mcp.semji.com/mcp
Run /mcp in Claude Code and follow the browser sign-in. Once it shows connected, you can start prompting.

Claude Desktop and claude.ai

Add it as a custom connector:
1

Open connector settings

Go to Settings → Connectors and click Add custom connector.
2

Enter the server URL

Paste https://mcp.semji.com/mcp and confirm with Add.
3

Connect and sign in

Open the new connector, click Connect, and sign in to Semji in the browser window that opens.
Custom connectors are available on Free, Pro, Max, Team, and Enterprise plans (Free is limited to one custom connector). Claude reaches the server from Anthropic’s cloud rather than your machine — this works because mcp.semji.com is publicly reachable.

Other MCP clients

Most MCP-compatible tools (Cursor, VS Code, Windsurf, Zed, ChatGPT custom connectors, and others) let you register a server in a JSON config. Use one of the two patterns below depending on what your client supports.
{
  "mcpServers": {
    "semji": {
      "type": "http",
      "url": "https://mcp.semji.com/mcp"
    }
  }
}
Use the remote (HTTP) form if your client can talk to remote MCP servers directly. If your client only supports local (stdio) servers, the local bridge uses mcp-remote to forward the connection and handle the browser sign-in for you (Node.js required).

Troubleshooting

Trigger the auth flow explicitly: in Claude Code run /mcp, in other clients re-open or reconnect the server. With the local bridge, the browser opens on first use — make sure no other process is holding the redirect port and that pop-ups aren’t blocked.
Your session expired or was never completed. Reconnect and sign in again. In Claude Code, /mcp lets you re-authenticate an existing server.
Custom connectors in Claude and ChatGPT connect from the vendor’s cloud, so the server must be reachable over the public internet — mcp.semji.com is. If you are behind a corporate proxy or VPN that blocks it, the local bridge (which connects from your machine) is the workaround.
Make sure Node.js is installed so npx can run, and keep mcp-remote up to date (mcp-remote@latest, version 0.1.16 or newer). Restart the client after editing its config file.
The assistant is scoped to the Semji account and the organization you picked when signing in. To switch organization (or account), disconnect the server and reconnect, then sign in again and choose the other organization.