Connect your own AI agent

dronelist.io speaks the Model Context Protocol (MCP). Connect Claude, ChatGPT, or Cursor, and that assistant can read your workspace directly — your clients, the people at them, your open opportunities, proposals, tasks, and your own prices. This is the same set of tools the in-app assistant uses, mounted over a standard protocol.

The endpoint

https://api.dronelist.io/mcp

Setting it up

Add the connector

In Claude or ChatGPT, add a custom connector and give it the address above. Cursor and other MCP clients take the same address.

You land on a dronelist page listing what the app will be able to see. Pick your workspace, untick anything you would rather keep back, and press Allow.

Ask it something

“Which of my proposals are still waiting on a reply?” is a good first question — it exercises the brief tool, which is the one worth starting from.

You can take the access back at any time under Settings → Connected apps. The app stops reading straight away.

Connecting with an API key instead

Some clients take a header rather than running a sign-in flow. Those can use an API key from Settings → API Keys — the same key the REST API uses:

{
  "mcpServers": {
    "dronelist": {
      "url": "https://api.dronelist.io/mcp",
      "headers": {
        "Authorization": "Bearer dl_live_your_key_here"
      }
    }
  }
}

The X-API-Key header works too, if your client prefers it.

What the agent can do

Everything over MCP is read-only. No tool that changes a record is mounted here. An MCP client has no way to show you an approval card, and every write in dronelist waits for your click — so writes stay in the app. This is also why the connect screen offers no write permission: it would be asking for something the server cannot act on.

Your records

Tool	What it returns
`getWeeklyBrief`	The four follow-through signals for the week: proposals with no reply, follow-ups due, repeat work coming round, clients gone quiet
`findClients` · `getClient`	Client companies, by name or in full
`findPeople` · `getPerson`	The people at those companies
`findOpportunities` · `getOpportunity`	Open work, by name or in full
`listProposals` · `getProposal`	Proposals, with open counts and the site pin
`listTasks`	Open and recently completed tasks
`getServices`	Your own prices and typical effort per job

Start with getWeeklyBrief for anything about who to contact or what needs attention.

Public lookups

These read no data of yours and need no scope, so a connection with none still reaches them:

Tool	What it returns
`getSiteWeather`	Forecast for a site on a given date
`getSiteAirspace`	Informational airspace class and nearest airport
`getSiteNearby`	Mapped features within 800 m, from OpenStreetMap
`lookupLegalEntity`	The client’s registered entity, from the Global LEI Index
`lookupBuyerNotices`	EU public procurement notices for a buyer, from TED

The site tools are a planning aid only. They are not an official aviation briefing and not permission to fly. Confirm airspace and authorisation with the official service before every flight.

Scopes

Scopes decide which tools the assistant can even see — the ones you tick when you connect it, or the ones on the API key. A tool outside them is not listed, rather than listed and refused.

Scope	Unlocks
`crm:read`	`findClients`, `getClient`, `findPeople`, `getPerson`, `findOpportunities`, `getOpportunity`
`proposal:read`	`listProposals`, `getProposal`
`task:read`	`listTasks`
`service:read`	`getServices`
`crm:read` + `proposal:read`	`getWeeklyBrief`

Grant only what you need. A connection meant to answer “who should I chase” needs crm:read and proposal:read and nothing else. Only read scopes are offered when you connect an app. The write scopes exist for API keys and the REST API; nothing reachable over MCP can use them.

Limits

The endpoint is stateless — a fresh server per request, nothing kept between calls.
The same rate limits apply as to the REST API: 100 requests a minute on the standard tier.
MCP calls do not spend dronelist credits. Your own AI client bills you for the model.

Notes

Disconnecting the app, or revoking the key, cuts the assistant off immediately.
The agent reads one workspace — yours. It cannot reach another account’s records.
If you want writes, use the in-app assistant. It asks before every change and shows you exactly what it will do.

Getting started

Core concepts

Guides

Endpoints

Connect your own AI agent

Connect your own AI agent

The endpoint

Setting it up

Connecting with an API key instead

What the agent can do

Your records

Public lookups

Scopes

Limits

Notes

​Connect your own AI agent

​The endpoint

​Setting it up

​Connecting with an API key instead

​What the agent can do

​Your records

​Public lookups

​Scopes

​Limits

​Notes

Connect your own AI agent

The endpoint

Setting it up

Connecting with an API key instead

What the agent can do

Your records

Public lookups

Scopes

Limits

Notes