Overview

The UserJot MCP integration lets AI tools connect directly to your UserJot workspace through a remote MCP server.

If your editor or assistant supports remote MCP servers, you can connect it to UserJot without installing a local package or running your own bridge process.

Server URL

UserJot exposes a single remote MCP endpoint:

https://api.userjot.com/v1/mcp

This is a remote HTTP MCP server, so your client needs to support remote MCP connections and custom headers.

Authentication

Authenticate requests with a UserJot API token:

Authorization: Bearer YOUR_USERJOT_API_TOKEN

Create the token in your UserJot dashboard under Settings → API Tokens.

When to use MCP

Use the MCP server when you want an AI assistant to work with UserJot directly from a supported client like Claude Code, Cursor, or Windsurf.

MCP is a good fit when you want to:

pull UserJot context into an AI workflow
let an assistant inspect workspace data without building a custom integration
connect UserJot to an MCP-aware coding or research tool

MCP vs REST API

Use MCP when the integration target is an AI client that already understands the Model Context Protocol.

Use the UserJot REST API when you are building your own backend integration, automation, or application code and want full control over requests and responses.

What you need

Before setting up a client, make sure you have:

a UserJot workspace with API access enabled
a UserJot API token from Settings → API Tokens
an MCP-compatible client that supports remote HTTP servers

Token handling

Treat your UserJot API token like any other secret:

do not hardcode it into committed config files
prefer environment variables or a local secrets manager when your client supports them
use separate tokens for different environments or teammates when possible
revoke tokens you no longer need from the UserJot dashboard