Centrex MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CENTREX_ACCOUNT_ID | No | Lock to a specific account/org ID | |
| CENTREX_ACCESS_TOKEN | Yes | Bearer token from Centrex → Settings → API | |
| CENTREX_ALLOW_DESTRUCTIVE_OPERATIONS | No | Set true to allow DELETE operations (default false) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| centrex_list_contactsB | Search and list contacts in Centrex CRM. Supports filtering by name, email, phone, status, and more. |
| centrex_get_contactA | Get a single contact by ID including all CRM fields, notes, and metadata. |
| centrex_create_contactB | Create a new contact/lead in Centrex CRM. |
| centrex_update_contactC | Update an existing contact in Centrex CRM. Only provided fields are updated. |
| centrex_delete_contactA | Delete a contact from Centrex CRM. Requires CENTREX_ALLOW_DESTRUCTIVE_OPERATIONS=true. |
| centrex_get_contact_notesB | Get all notes for a contact. |
| centrex_create_contact_noteB | Add a note to a contact record. |
| centrex_send_communicationC | Send an email or SMS to a contact. |
| centrex_list_advancesB | List all loan/advance records in Centrex. |
| centrex_create_advanceC | Create a new loan/advance record in Centrex. |
| centrex_list_documentsC | List documents in Centrex, optionally filtered by contact. |
| centrex_get_documentB | Get metadata and download URL for a specific document. |
| centrex_list_alertsC | List alerts/notifications in Centrex. |
| centrex_create_alertB | Create a new alert/reminder in Centrex. |
| centrex_list_usersB | List users/agents in the Centrex account. |
| centrex_get_userA | Get a specific user by ID. |
| centrex_list_teamsB | List teams in the Centrex account. |
| centrex_list_submissionsB | List lender submission records in Centrex. |
| centrex_get_submissionB | Get details and status of a specific lender submission. |
| centrex_requestA | Make a raw authenticated request to any Centrex API endpoint. Use this for endpoints not covered by dedicated tools. DELETE and destructive POST paths require CENTREX_ALLOW_DESTRUCTIVE_OPERATIONS=true. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 20 tools
Each tool targets a distinct resource and action (e.g., list_contacts, get_contact, create_contact), with no overlapping purposes. The raw request tool is a catch-all that does not conflict with dedicated tools.
All tools use the consistent 'centrex_' prefix and snake_case, with most following a verb_noun pattern (e.g., list_contacts, create_contact). The only minor inconsistency is 'centrex_request', which lacks a verb (compared to e.g., 'send_communication').
20 tools is slightly above the typical 3-15 range but still appropriate for a CRM covering multiple domains (contacts, users, teams, advances, documents, alerts, submissions). Each tool serves a clear purpose, and the raw request endpoint justifies a larger surface.
Contacts have full CRUD and notes, but other resources are incomplete: users only have list/get, advances only list/create, documents only list/get, alerts only list/create, submissions only list/get. Missing update/delete for these resources are notable gaps that may require the raw request tool.