Cretia

app.cretiaPublished by cretia.appOfficial publisherv1.0.0Updated Nov 1, 2026

Field service, invoicing and CRM for pest control and facility services businesses.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Cretia is a remote MCP endpoint for a field service, invoicing and CRM platform aimed at pest control and facility services businesses.

What you can do
  • The registry entry describes Cretia as field service, invoicing and CRM software for pest control and facility services businesses.
  • No tools are listed in the manifest, so the specific operations an assistant can perform are not documented here.
  • The server is reached as a remote streamable HTTP endpoint at the provider's API host.
  • Connecting requires OAuth authentication.
When to use it
Worth considering if you already run your pest control or facility services business on Cretia and want an assistant to work with that business data. Without a published tool list, check the provider's documentation first to confirm what the assistant can actually do.
Requirements
A remote streamable HTTP endpoint provided by Cretia; no local package or runtime is needed. An OAuth sign-in with a Cretia account is required. No environment variables or headers are declared.
Before you install
The server handles business records such as customers, jobs and invoices, so an assistant may be able to read or change operational and financial data; confirm the granted scopes before connecting. No tool list is published, so the exact write capabilities are unknown. Business data is sent to the provider's remote endpoint.

Installation

In SourceWeft

  1. Open Cretia in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/app.cretia%2Fcretia/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "cretia": {
      "type": "http",
      "url": "https://api.cretia.app/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestNov 1, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.