Dataceen LogoDataceen Wordmark

Ask the demo yourself

The demo system publishes an MCP server. Point any agent that speaks MCP at the address below and ask questions in plain language. No account, no API key, nothing to install.

MCP server address

https://mcp.dataceen.com/mcp/demo/fieldserviceops/visitor

Open to everyone, read-only. Your agent signs in by itself — you will not be asked for anything.

In a chat app

Claude

  1. 1Open Settings, then Connectors.
  2. 2Click the plus, then Add custom connector.
  3. 3Paste the address above. Leave the advanced OAuth fields empty.
  4. 4Click Add. Claude runs the sign-in itself.
  5. 5In a chat, open the plus menu, choose Connectors, and switch it on.

Works in Claude Desktop and on the web, on every plan including Free. On Team and Enterprise an owner adds the connector once under Organization settings, then members connect to it.

ChatGPT

  1. 1Open Settings and turn on Developer mode. It sits under Security and login — in some builds under Apps & Connectors, Advanced settings.
  2. 2Go to Settings, then Apps & Connectors, and choose Create.
  3. 3Give it a name and a short description.
  4. 4Paste the address above and choose OAuth as the authentication method.
  5. 5In a conversation, enable it from the developer-mode tool in the composer.

Developer mode needs a paid plan — Plus, Pro, Business, Enterprise or Edu. It is not available on the free tier.

In your editor

GitHub Copilot in VS Code

  1. 1Open the Command Palette and run MCP: Add Server.
  2. 2Choose HTTP, paste the address above, and pick Global or Workspace.
  3. 3Open Copilot Chat in Agent mode — the tools appear in the tool picker.

Or commit this to .vscode/mcp.json:

{
  "servers": {
    "dataceen-demo": {
      "type": "http",
      "url": "https://mcp.dataceen.com/mcp/demo/fieldserviceops/visitor"
    }
  }
}

Claude Code

  1. 1Add the server with one command. Use --scope project to commit it to the repo, or --scope user to keep it to yourself.
  2. 2Start Claude Code and run /mcp to sign in. A browser window does the rest.

Run this:

claude mcp add --transport http dataceen-demo https://mcp.dataceen.com/mcp/demo/fieldserviceops/visitor

Cursor

  1. 1Add the server from the Customize page in the sidebar, or write the config file yourself.
  2. 2Open the Agent and the seven tools appear in its tool list.

In .cursor/mcp.json for one project, or ~/.cursor/mcp.json for all of them:

{
  "mcpServers": {
    "dataceen-demo": {
      "url": "https://mcp.dataceen.com/mcp/demo/fieldserviceops/visitor"
    }
  }
}

Any other MCP client

The address is the only thing any MCP client needs. Point it at the URL and pick OAuth if it asks how to authenticate — the sign-in details are discovered from the address itself.

What you can ask

The visitor scope exposes one search tool per entity in the model — seven in all. Each one searches, filters and aggregates, so an agent can answer counting and grouping questions without you writing a query.

CustomerSiteAssetService agreementWork orderTechnicianInvoice
  • Which of our elevators have certificates expiring this quarter — and where are they?
  • How many work orders are open per technician right now?
  • Show unpaid invoices for customers with an active service agreement.

This one is open. Yours will not be.

The demo runs on a visitor scope: seven read-only search tools and nothing else. There is no write tool to call, and every record in it is invented.

Your own system works the other way round. When you publish a model, its MCP server sits behind your own identity provider. Every agent signs in as itself, is given a scope, and sees only the entities, fields and operations that scope allows — the same permissions that apply to your people and your applications, from the same directory. An agent with no scope sees nothing at all.

And the data never moves: it stays in the storage you control.

Your own system starts with a free account.