Common setup

UserJot does not require a local MCP package. You connect your client directly to the remote UserJot MCP server using the server URL and an API token.

What you will need

You need two values:

Server URL: https://api.userjot.com/v1/mcp
Authorization: Bearer YOUR_USERJOT_API_TOKEN

Create the token in UserJot under Settings → API Tokens.

Generic remote MCP shape

Most MCP clients that support remote HTTP servers use a configuration that looks roughly like this:

{
  "mcpServers": {
    "userjot": {
      "url": "https://api.userjot.com/v1/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_USERJOT_API_TOKEN"
      }
    }
  }
}

The exact file path and field names vary by client, which is why the rest of this section has separate setup pages for Claude Code, Cursor, Codex, ChatGPT, and Windsurf.

Verify the connection

After setup, open your MCP-aware client and ask it to inspect the connected UserJot server or list available tools.

If the connection is working, the client should discover the UserJot MCP server without additional local setup.

Troubleshooting

If the connection fails, check these first:

the token is valid and has not been revoked
the Authorization header starts with Bearer
your client supports remote HTTP MCP servers
your config file is in the correct location for that client
you restarted the client after editing the config

Notes on other MCP clients

Remote MCP support is still moving quickly across clients.

If your preferred tool is not listed here, use the same server URL and bearer token, then adapt them to that client's remote MCP configuration format.