Connect Cursor to Jasning

Cursor speaks MCP. If you live in Cursor for development work, adding Jasning means you can dispatch jobs without changing windows.

What you'll need

• A Jasning account
• Cursor 0.40 or newer (custom MCP servers via streamable HTTP)
• A few minutes

Steps

1. Open Cursor's MCP settings

In Cursor: Settings → MCP → Add new MCP server.

2. Configure the connection

Pick streamable HTTP as the transport. Paste the URL:

https://jasning.com/mcp

Auth: OAuth 2.1 (PKCE). Cursor handles the flow automatically.

3. Authorize

Cursor opens the Jasning consent page in your browser. Log in, review what the connector can do, click Grant access. The token lands back in Cursor.

4. Use it

In any Cursor chat:

Use the jasning MCP to show me today's dispatch.

The first prompt usually needs the explicit "use the jasning MCP" hint. After that Cursor picks up the tools automatically.

Why you'd use Cursor for this

The honest answer: most dispatchers won't. Cursor is built for code, not field service. But if you're a technical founder running a small crew yourself, or you're building automations that touch Jasning, having the same interface for both is a real time-saver.

Examples that work well from Cursor:

• Pull every appointment from last month and summarize as CSV in this file.
• Compare the queue size today vs a week ago.
• Draft a status update for the team based on today's completed jobs.

Each call goes through the MCP server, returns structured data, and Cursor can pipe the result into the file or chat you're working in.

Limits

• Cursor uses MCP within a single chat session. Long chats may evict tools. Start a fresh session for a new dispatch task.
• The free Cursor tier limits MCP usage. Check your plan if calls start failing without a clear error.

Revoking access

• In Cursor: Settings → MCP → remove the Jasning server.
• In Jasning: Settings → Tokens, revoke the entry.

Either kills the connection immediately.