# Clevra [Health: Active]

**Category:** 🎧 Support & Service Management  
**Repository:** https://clevra.ai/mcp  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/clevra

## Description
Field service management for trades: clients, jobs, estimates, invoices, schedule and reports.

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: medium). Install path inferred — verify against the README before running it. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "clevra": {
    "url": "https://clevra.ai/mcp"
  }
}
```

## Documentation

## What Clevra MCP server does

Clevra MCP server is intended for field service management in trade businesses. Its documented scope covers the operational records and workflows commonly used to coordinate service work: clients, jobs, estimates, invoices, schedules, and reports. This makes it relevant to teams that need an AI agent to work with trade-service information through an MCP connection.

The listing does not describe a narrower trade specialization, such as plumbing, electrical work, or construction. It is therefore best understood as a general field-service system for trades rather than a tool limited to one type of contractor. The available information also does not identify whether the server reads data, creates records, updates records, or supports all of those operations.

## Tools and capabilities

The Clevra MCP server covers these functional areas:

- Client information
- Job management
- Estimate management
- Invoicing
- Scheduling
- Reporting

These areas can help an agent work with the business information behind field-service operations. For example, the stated scope is relevant to workflows involving a customer, a service job, an estimate, an invoice, an appointment schedule, or a report. The source material does not provide the names of individual MCP tools, their parameters, return formats, or relationships between these areas.

For developers evaluating the Clevra MCP server, the key fit question is whether the required workflow falls within those six listed domains. If the agent needs capabilities outside client, job, estimate, invoice, schedule, or report management, the available description does not confirm that Clevra supports them.

## Limitations and notes

The available source material is limited to a short product description. It does not document installation commands, required environment variables, authentication, transport options, permissions, client compatibility, rate limits, or error behavior. Those details should be verified with the provider before implementation.

No individual operation is confirmed beyond the named management areas. In particular, the listing does not establish whether the server can create, modify, delete, search, or only retrieve records. It also does not specify reporting formats or scheduling features such as recurring appointments, availability rules, or reminders.

Clevra belongs in the Support & Service Management category because its documented focus is field-service work for trades. Treat that classification as a guide to its domain, not as confirmation of features beyond the listed scope. A production evaluation should confirm the exact tools and access model for the workflows the agent will perform.

_Full upstream README: https://allmcps.com/mcp/clevra/readme_