What can you do with this server?

This MCP server lets you query read-only data from the PersonalEasy / EasyDental / DentalKids dental clinic API. * List appointments: fetch appointments within a date range, optionally filtered by unit (personaleasy_get_agendamentos). * Get production KPIs: retrieve dashboard production metrics for a period, optionally filtered by unit and/or provider (personaleasy_get_kpi_producao). * Find provider by CPF: look up a provider's ID and name using their CPF in 999.999.999-99 format (personaleasy_get_prestador_por_cpf). * List active units: get the ID and name of all active service units (personaleasy_get_unidades). * All tools are read-only and safe to use for reporting and operational queries.

How do I use personaleasy-mcp-server?

1. Click on "Install Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@personaleasy-mcp-server show me appointments for next week at the main unit" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

de en es ja ko pt ru zh

personaleasy-mcp-server

by marqprochat

Overview Schema Source Related Servers Score Discussions Admin

TypeScript

Hybrid

personaleasy-mcp-server

MCP server for the PersonalEasy API | EasyDental Cloud | DentalKids.

Tools

Tool	Description	Parameters
`personaleasy_get_agendamentos`	Fetches appointments in the period	`dt_inicio`, `dt_termino` (YYYY-MM-DD), `nm_unidade` (optional)
`personaleasy_get_kpi_producao`	Production KPIs for dashboard	`dt_inicio`, `dt_termino`, `nm_unidade` (opt.), `nm_prestador` (opt.)
`personaleasy_get_prestador_por_cpf`	Provider ID and name by CPF	`cpf` (format 999.999.999-99)
`personaleasy_get_unidades`	Lists active service units	—

All tools are read-only (readOnlyHint: true).

Related MCP server: open-dental-mcp

Installation

npm install
npm run build

Credentials

Credentials are never kept in the code. Set them via environment variables:

PERSONALEASY_API_KEY — the api-key (header x-api-key)
PERSONALEASY_CLIENT_ID — the client ID
PERSONALEASY_BASE_URL — optional, defaults to https://prsrb.onrender.com/v1/rpc

For local testing, copy .env.example to .env and fill it in. The .env file is in .gitignore — do not version it or share it.

Configuration in Claude Code

claude mcp add personaleasy --env PERSONALEASY_API_KEY=SUA_KEY --env PERSONALEASY_CLIENT_ID=SEU_CLIENT_ID -- node D:/MCPS/personaleasy-mcp-server/dist/index.js

Configuration in Claude Desktop

In claude_desktop_config.json:

{
  "mcpServers": {
    "personaleasy": {
      "command": "node",
      "args": ["D:/MCPS/personaleasy-mcp-server/dist/index.js"],
      "env": {
        "PERSONALEASY_API_KEY": "SUA_KEY",
        "PERSONALEASY_CLIENT_ID": "SEU_CLIENT_ID"
      }
    }
  }
}

Deploy on Easypanel (Docker)

The project has two execution modes:

stdio (dist/index.js) — local use (Claude Code / Claude Desktop)
HTTP (dist/http.js) — remote use; this is the mode used by the Dockerfile

On Easypanel, create an App service pointing to this repository (build via Dockerfile) and configure the environment variables:

Variable	Required	Description
`PERSONALEASY_API_KEY`	yes	API api-key
`PERSONALEASY_CLIENT_ID`	yes	Client ID
`MCP_AUTH_TOKEN`	recommended	Bearer token required on the `/mcp` endpoint (generate a long random value)
`PORT`	no	defaults to 3000

Expose port 3000 on the service. Endpoints:

POST /mcp — MCP endpoint (Streamable HTTP, stateless)
GET /health — healthcheck

Production instance

Base URL: https://dk-projetos-mcps.nv8gf3.easypanel.host
Healthcheck: GET https://dk-projetos-mcps.nv8gf3.easypanel.host/health → {"status":"ok"}
MCP Endpoint: POST https://dk-projetos-mcps.nv8gf3.easypanel.host/mcp

To connect an MCP client to this instance:

claude mcp add --transport http personaleasy https://dk-projetos-mcps.nv8gf3.easypanel.host/mcp --header "Authorization: Bearer SEU_MCP_AUTH_TOKEN"

Replace SEU_MCP_AUTH_TOKEN with the value set in the MCP_AUTH_TOKEN variable of the Easypanel service.

Important: without MCP_AUTH_TOKEN configured in the service, anyone with this URL can query the clinic's data. Make sure the variable is set in production.

Underlying API

All calls go to a single RPC endpoint:

POST {BASE_URL}
Headers: x-api-key
Body: { "clientId": "...", "method": "RPCGet...", "params": { ... } }

Methods used: RPCGetAgendamentos, RPCGetKPIPrd, RPCGetPrestadorCPF, RPCGetUnidadeAtendimento.

Available Tools

4 tools

personaleasy_get_agendamentosBuscar agendamentosA

Read-only

Retorna os agendamentos no período informado. Opcionalmente filtra por unidade de atendimento (use personaleasy_get_unidades para descobrir os nomes válidos).

ParametersJSON Schema

Name	Required	Description
`dt_inicio`	Yes	Data inicial do período, formato YYYY-MM-DD (ex.: 2026-01-01)
`dt_termino`	Yes	Data final do período, formato YYYY-MM-DD (ex.: 2026-01-31)
`nm_unidade`	No	Nome da unidade de atendimento para filtrar (ex.: 'Valinhos'). Vazio retorna todas.

TDQS

A3.8/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and openWorldHint=true, covering safety and completeness. The description adds that it returns appointments in a period, but does not disclose any additional behavioral traits (e.g., error handling, performance, or what happens with invalid dates). It does not contradict annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise: two sentences that cover purpose, optional filtering, and a cross-reference. Every word earns its place with no filler or redundant information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite the annotations covering read-only and open-world aspects, the description omits any information about the return value format (e.g., fields, structure). Since there is no output schema, the agent is left guessing what the response looks like. Additionally, it does not mention date range limits or error scenarios.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so baseline is 3. The description adds value by telling the agent that the nm_unidade parameter can be filled using personaleasy_get_unidades, providing a cross-reference beyond the schema's inline description. This helps the agent understand where to obtain valid values.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it returns appointments within a specified date period, with optional filtering by unit. The verb 'retorna' and resource 'agendamentos' are explicit. It distinguishes from sibling tools like personaleasy_get_kpi_producao (KPIs) and personaleasy_get_prestador_por_cpf (provider lookup) by focusing on schedule data.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides a helpful cross-reference to personaleasy_get_unidades for discovering valid unit names, but it does not give explicit guidance on when to use this tool versus alternatives (e.g., when to use personaleasy_get_prestador_por_cpf instead). No 'when not to use' or context for choosing among siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

personaleasy_get_kpi_producaoKPIs de produçãoA

Read-only

Retorna dados de produção (KPIs de dashboard) no período informado. Filtros opcionais por unidade e por prestador.

ParametersJSON Schema

Name	Required	Description
`dt_inicio`	Yes	Data inicial do período, formato YYYY-MM-DD
`dt_termino`	Yes	Data final do período, formato YYYY-MM-DD
`nm_unidade`	No	Nome da unidade para filtrar. Vazio retorna todas.
`nm_prestador`	No	Nome do prestador para filtrar. Vazio retorna todos.

TDQS

A3.9/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is clear. The description adds no behavioral contradictions and is consistent with annotations, which is sufficient. No additional behavioral details are needed beyond what annotations provide.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, concise sentence that efficiently conveys the core purpose and filter options. It is front-loaded with the main action ('Retorna dados de produção') and uses no unnecessary words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given that the tool has 4 parameters with complete schema descriptions, no output schema, and is a simple read-only KPI retrieval, the description adequately covers the tool's functionality. It does not need to explain return values explicitly since the dashboard KPI context is implied.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the input schema already documents all four parameters with descriptions, formats, and defaults. The description adds no new information about parameters beyond what the schema provides, meeting the baseline but not exceeding it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states that the tool returns production KPI (dashboard) data within a given period, mentioning optional filters for unit and provider. While it effectively describes the tool's purpose, it does not explicitly distinguish itself from sibling tools beyond implying it focuses on production KPIs.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description indicates when to use the tool (when production KPI data is needed) and notes optional filters, but it offers no guidance on when to NOT use it or how it compares to sibling tools (e.g., scheduling or provider lookups). Usage context is implied but not explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

personaleasy_get_prestador_por_cpfBuscar prestador por CPFA

Read-only

Retorna o ID e o Nome do prestador a partir do CPF.

ParametersJSON Schema

Name	Required	Description	Default
`cpf`	Yes	CPF do prestador no formato 999.999.999-99

TDQS

A3.5/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and openWorldHint=true, so the tool is known to be safe and side-effect-free. The description adds that it returns only ID and Nome, which is useful context. However, it does not explain what happens if the CPF is not found (likely empty or error? no indication).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, clear sentence with no unnecessary words. It immediately states the output fields and the input key. Perfectly concise for a simple lookup tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's low complexity (1 parameter, no output schema, simple lookup), the description is mostly adequate. However, it lacks mention of error handling (e.g., CPF not found) and does not specify if the result is guaranteed to be unique. Completeness is acceptable but not thorough.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% (only one parameter 'cpf' with format and description). The description does not add further meaning beyond what the schema already provides—it repeats the purpose. Baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Retorna o ID e o Nome do prestador a partir do CPF' clearly states the verb (retorna) and resource (prestador por CPF), specifying the key fields returned (ID, Nome). It distinguishes from sibling tools which handle appointments, KPIs, and units.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for searching a provider by CPF, but does not explicitly state when to use this tool versus alternatives, nor does it mention any prerequisites (e.g., need for exactly matching CPF). No guidance on when not to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

personaleasy_get_unidadesListar unidades ativasA

Read-only

Retorna o ID e o Nome das unidades de atendimento ativas.

ParametersJSON Schema

Name	Required	Description	Default
No parameters

TDQS

A4/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint and openWorldHint, covering safety and data volatility. The description adds that it returns ID and Name of active units. No further behavioral traits (e.g., pagination, ordering, result limits) are disclosed, which would be useful but are not critical given the tool's simplicity.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single, front-loaded sentence that directly conveys the action, resource, and output fields. Every word is necessary and there is no fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a parameterless read-only listing tool with openWorldHint, the description covers the essential output (ID and Name of active units). The lack of output schema is compensated by the explicit mention of fields. It does not mention response structure or potential edge cases (e.g., empty list), but these are minor omissions given the tool's simplicity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has no parameters (100% coverage by definition). The description correctly implies no inputs are needed. With zero parameters, the baseline is 4; the description does not need to add parameter-level detail beyond stating the output.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Retorna' (returns) and the resource 'unidades de atendimento ativas' (active service units), specifying that ID and Name are provided. It distinguishes well from sibling tools, which cover appointments, KPI, and provider lookup.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage context is implied by the tool's purpose—use it to list active units. However, there is no explicit guidance on when to prefer this tool over alternatives, nor any prerequisites or caveats. For a simple parameterless tool, this is adequate but not exemplary.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

4 tool updatesv1.0.0Aug 18, 2026
- First observedpersonaleasy_get_agendamentos
- First observedpersonaleasy_get_kpi_producao
- First observedpersonaleasy_get_prestador_por_cpf
- First observedpersonaleasy_get_unidades

Install Server

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A3.8/5.0

Disambiguation5/5

Each tool targets a distinct resource: appointments (agendamentos), production KPIs, provider lookup by CPF, and units. There is no overlap in purpose, and the descriptions clearly differentiate them.

Naming Consistency4/5

All tools follow the pattern `personaleasy_get_<resource>`, using the same prefix and verb. The resource names are in Portuguese, which is consistent with the domain, though the prefix adds redundancy.

Tool Count4/5

Four tools is appropriate for a focused server that provides read-only access to core entities (appointments, KPIs, providers, units). It is not too few for the apparent scope, and each tool serves a clear purpose.

Completeness3/5

The tool set covers reading key entities, but there are obvious gaps: no filtering by provider for appointments, no tool for patients or procedures, and only a CPF-based lookup for providers. Write operations (create, update, delete) are absent, limiting the surface to querying.

Maintenance

ActivityMaintained

ResponsivenessNo issues

Resources

GitHub Repository

Need Help?

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

ProviderSignal: Dental Market Intelligence
com.providersignal
Read-only MCP: US dental intel, all-category Medicaid fee schedules, dentist lookup. Free tier.
Databases Search Health & Wellness
2
lacita A
app.lacita.api
MCP server for lacita - appointment management software
App Automation Customer Support Project Management
282
healthie A
io.usefulapi
Hosted MCP server for the Healthie EHR & telehealth API: patients, appointments, charting, tasks.
Biology & Medicine Calendar Management
162
classquill-mcp
io.github.EquateItAu
Read-only MCP server for ClassQuill, a tutoring-business-management platform.
Education & Learning Tools CRM
2

Related MCP Servers

datagate-mcp
Payments & Billing CRM
hyamie
A
license
B
quality
C
maintenance
MCP server for the DataGate billing platform API, providing read-only tools to manage customers, invoices, products, agreements, sites, and payments.
Updated 14 days ago (2026-08-25 02:30 UTC)
13
MIT
open-dental-mcp
Biology & Medicine
sanjibani
A
license
A
quality
B
maintenance
Enables interaction with Open Dental practice management software, allowing reading of patients, appointments, providers, procedures, and recalls, as well as writing communications back to patient charts via MCP clients.
Updated 2 months ago (2026-06-26 11:21 UTC)
14
5
MIT
Realm MinistryPlatform MCP
CRM Customer Data Platforms
sanjibani
A
license
A
quality
C
maintenance
MCP server for interacting with Realm MinistryPlatform data, enabling queries, record creation, and updates from any MCP client.
Updated a month ago (2026-07-25 08:02 UTC)
1
MIT
Healthpoint MCP Server
Biology & Medicine Location Services Search
edithatogo
A
license
A
quality
A
maintenance
Read-only MCP server for licensed Healthpoint HL7 FHIR API access.
Updated 4 days ago (2026-09-04 14:05 UTC)
10
1
Apache 2.0

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/marqprochat/mcpdentalkids'

If you have feedback or need assistance with the MCP directory API, please join our Discord server