Connected apps

Use QSME from the assistant you already use

Already ask Claude or ChatGPT for help with your day? Connect it to QSME and it can read your projects, check the schedule, price up a schedule of quantities and draft a tender or contract for you to review. It works over MCP — the open standard the big AI apps use to connect to tools — so there is nothing to install.

Pick your app Manage connected apps

What it can do

Read your projects, schedules of quantities, tenders, contracts and schedule
Add and edit SOQ sections, jobs, material and labour lines
Draft a tender from SOQ jobs — you send it when you are ready
Draft a contract — you issue it when you are ready
Search across your projects and answer questions about them

What it can never do

Move money or record a payment
Send or publish a tender, or accept a bid
Issue, sign or cancel a contract
Change the schedule or delete a project

Those stay in QSME, behind your own login. The assistant drafts; you decide.

Pick your app

Two minutes each. Claude and ChatGPT sign in with your QSME account; coding tools can use a token from Settings instead.

Claude ChatGPT Claude Code Codex Cursor & others

Claude (web, desktop and phone)

Add QSME as a connector once and it is available in every chat, on every device you use Claude on.

1
In Claude, open Customize → Connectors and choose Add custom connector. On a Team or Enterprise plan an owner adds it under Organization settings → Connectors.
2
Name it QSME and paste this as the server URL. Leave the authentication and OAuth options on their defaults.
Remote MCP server URL
```
https://api.qsme.co.nz/mcp
```
3
Press Connect. A QSME sign-in page opens — sign in, read what it will be allowed to do, and press Allow.
4
In a chat, press + → Connectors and switch QSME on. Then just ask: "What's on my schedule this week?"

ChatGPT

Needs a paid ChatGPT plan (Plus, Pro, Business, Enterprise or Edu) with developer mode switched on.

1
In ChatGPT, open Settings, find Developer mode (under Apps & Connectors, or Security and login, depending on your version) and turn it on.
2
Add a new connector: name it QSME, paste the server URL, and choose OAuth for authentication.
MCP server URL
```
https://api.qsme.co.nz/mcp
```
3
Press Create. Sign in to QSME when asked and press Allow.
4
In a chat, press + and pick QSME from your connectors, then ask away.

Claude Code

One command in your terminal. Sign in through the browser, or use a token from Settings.

Add QSME as a remote server:

Terminal

claude mcp add --transport http qsme https://api.qsme.co.nz/mcp

2
Inside Claude Code, type /mcp, pick qsme and choose Authenticate. Sign in to QSME in the browser and press Allow.

Prefer a token? Create one under Settings → Connected apps and add the server with a header instead — no browser step:

Terminal

claude mcp add --transport http qsme https://api.qsme.co.nz/mcp --header "Authorization: Bearer YOUR_TOKEN"

Sharing a project with your team? Put it in .mcp.json and keep the token in an environment variable:

.mcp.json

{
  "mcpServers": {
    "qsme": {
      "type": "http",
      "url": "https://api.qsme.co.nz/mcp",
      "headers": { "Authorization": "Bearer ${QSME_TOKEN}" }
    }
  }
}

Codex

Works in the Codex CLI, the Codex app and the VS Code extension.

Add the server, then sign in:

Terminal

codex mcp add qsme --url https://api.qsme.co.nz/mcp
codex mcp login qsme

2
In the Codex app or VS Code extension, open MCP servers → Add server, choose Streamable HTTP, name it qsme and paste the URL. Restart Codex afterwards.
MCP server URL
```
https://api.qsme.co.nz/mcp
```
3
Prefer a token? Create one under Settings → Connected apps, export it as QSME_TOKEN, and add this to ~/.codex/config.toml:
~/.codex/config.toml
```
[mcp_servers.qsme]
url = "https://api.qsme.co.nz/mcp"
bearer_token_env_var = "QSME_TOKEN"
```

Cursor, Windsurf and other MCP clients

Anything that speaks MCP over HTTP can connect. Most take a URL plus a header.

1
Create a token under Settings → Connected apps.

Add a server named qsme with the URL below and the header Authorization: Bearer YOUR_TOKEN. In JSON-style configs it looks like this:

mcp.json

{
  "mcpServers": {
    "qsme": {
      "url": "https://api.qsme.co.nz/mcp",
      "headers": { "Authorization": "Bearer YOUR_TOKEN" }
    }
  }
}

3
If the app supports OAuth for remote servers, you can skip the token: add the URL on its own and sign in when prompted.

Things to try

“What's on my schedule this week, and who's turning up?”
“Add a labour line to the kitchen job: 2 people, 16 hours, $85 an hour.”
“Price up the SOQ for the Smith job and tell me what looks light.”
“Draft a tender for the plumbing and drainage jobs, private, closing next Friday.”
“Draft a fixed-price contract with Aroha Electrical for $12,400 excluding GST.”

Keeping it safe

You approve each app once. It sees only what your own login sees, and only within the access you allowed.
Money and commitments stay out. Payments, sending tenders, accepting bids and issuing contracts are not available to any connected app — they are not "off by default", they do not exist on this connection.
Everything is logged. Settings → Connected apps shows what each app did and when.
Disconnect any time. Remove an app or a token and it loses access straight away.
Treat tokens like passwords. Keep them in environment variables, not in files you share.

For developers

A standard remote MCP server — Streamable HTTP, protocol revisions 2026-07-28 back to 2025-03-26. Authorisation is OAuth 2.1 with PKCE, discovered from the server's protected-resource metadata; clients can register with a Client ID Metadata Document or Dynamic Client Registration. A personal access token in an Authorization: Bearer header works too.

Endpoint

https://api.qsme.co.nz/mcp

Resource metadata

https://api.qsme.co.nz/.well-known/oauth-protected-resource

Authorisation server

https://api.qsme.co.nz/.well-known/oauth-authorization-server

Scopes

read · write

Read tools

list_projects · get_project · get_soq · list_tenders · get_tender · list_contracts · get_contract · get_schedule · search · fetch

Write tools

add_soq_category · add_soq_job · add_soq_material · add_soq_labour · update_soq_job · update_soq_material · update_soq_labour · delete_soq_item · create_tender_draft · update_tender_draft · add_tender_draft_items · create_contract_draft · update_contract_draft

Ready to connect?

Open Connected apps Create a free account