RCM Centric LLC connector
Use your RCM Centric LLC workspace from Claude, ChatGPT and other AI apps that support the Model Context Protocol (MCP) — as yourself, with your role's permissions.
https://agentic.rcmcentric.com/mcp
What it does
The connector lets an AI app look things up in the CRM, help with your email and — with full access — do the work you would do in the app, when you ask it to: for example “Which deals are at risk?”, “Draft a reply to Sam offering Thursday at 2 pm”, “Add Bright Clinic as a lead and create a deal for 12,000” or “Record the 1,000 payment from Acme”.
- It acts as you. The AI app sees only what your role in the CRM can see, and only the mailboxes you see in the Inbox.
- You choose the access when you connect, and can change it later: Full access, Read and mailbox actions, or Read only.
- Full access lets the app create and change records the way you can in the CRM: leads, companies, deals, tasks, calendar events, invoices, payments, bills, expenses, tickets and more. Tools that send something to someone outside the CRM (an email, an invoice, a contract), or delete, void or post something, never act on their own: the app must describe what will happen and you must agree in the chat first.
- Mailbox actions write drafts and move or mark emails. Drafts wait in Inbox → Drafts with an AI badge until you review and send them yourself.
- It cannot send email, delete records, change settings, start campaigns or see anything your role cannot.
Who can use it
Anyone with an account in the RCM Centric LLC workspace at https://agentic.rcmcentric.com. Signing in uses the workspace's normal sign-in page (including two-step sign-in where it is required). If you do not have an account, ask your workspace administrator.
Connect Claude
- In Claude (web or desktop) open Settings → Connectors and choose Add custom connector.
- Enter a name (for example “RCM Centric LLC”) and the connector address https://agentic.rcmcentric.com/mcp.
- Authentication: Sign in now. OAuth client: Use Claude's published identity (or Register automatically). No client ID, secret or headers are needed.
- Click Add, then Connect. Sign in to RCM Centric LLC, choose the access and click Allow.
- In a chat, turn the connector on from the tools menu and ask away.
Claude Code:
claude mcp add --transport http crm https://agentic.rcmcentric.com/mcpThen run /mcp in Claude Code and sign in in the browser window that opens.
Connect ChatGPT
- In ChatGPT open Settings → Apps & Connectors. Custom connectors may need Developer mode and a plan that allows them; on business plans a workspace admin may need to allow them first.
- Create a connector with the address https://agentic.rcmcentric.com/mcp and choose OAuth as the authentication.
- Sign in to RCM Centric LLC when asked and click Allow.
Tools
Each tool is available only when your role allows it and the connection’s access includes it. Read tools never change anything; Action tools change records inside the CRM; Asks first tools reach someone outside or delete, void or post, and run only after you confirm in the chat.
| Tool | What it does | Kind |
|---|---|---|
whoami | Who you are signed in as in the CRM, your role, the workspace and what this connection may do. Call it first when unsure what you can access. | Read |
get_dashboard_summary | Key numbers for the last N days: new leads, emails sent, replies and reply rate, meetings, AI spend, hot leads, approvals and tasks waiting, the pipeline by stage and won value. | Read |
search_leads | Find leads (prospects and contacts). Filter by free text (name, email, company, phone), status, tier, state, specialty or minimum score. Returns up to 50 per page with the total. | Read |
get_lead | Everything about one lead: contact details, company, score and tier, status, tags, signals and notes. | Read |
search_companies | Find companies (organisations your leads belong to) by name, website or state, with their contacts, deals and open value. | Read |
get_company | One company with its contacts (leads), deals and recent activity. | Read |
list_deals | The deals pipeline: each deal with its stage, value and close date, plus totals (open value, weighted, won this month, win rate). | Read |
deals_at_risk | Open deals scored by risk (no recent activity, slipping close dates, no next step) with the reasons. | Read |
deal_forecast | Pipeline forecast by month: value and weighted value of open deals by expected close month, at-risk value and won by month. | Read |
list_campaigns | Outreach campaigns with their status, channel and results (enrolled, sent, replies). | Read |
get_campaign | One campaign: its settings, steps and performance so far. | Read |
list_proposals | Proposals with their status (draft, sent, opened, in negotiation, revised, accepted, declined, expired), client, value, views and expiry; plus pipeline totals. | Read |
get_proposal | One proposal: its lines and totals, scope, timeline, status, version and the conversation with the client (questions, change requests, counter-offers). | Read |
list_meetings | Upcoming (default) or past meetings with the lead, time, place or link and status. | Read |
list_tasks | Tasks for people and agents: open (default) or done; yours, ones you created, or everyone’s. | Read |
get_agent_briefs | The AI agents’ daily briefs: what each agent did, found and recommends for a day (today by default). | Read |
search_files | Search file names and the text inside documents on the workspace drives. | Read |
read_file | The text of one document (PDF, Word, text…) found with search_files. | Read |
search_knowledge | Approved company knowledge (services, policies, FAQs, playbooks) the agents use. | Read |
search_workspace | Search the whole workspace (leads, companies, deals, emails, proposals, tasks and more) at once. | Read |
list_mailboxes | The mailboxes you can use (yours and shared ones), with unread counts and the number of conversations in each folder. | Read |
list_emails | Email conversations in a folder (inbox by default; also unread, replies, starred, sent, archive, bounces, spam, trash, all), newest first. Filter by mailbox or text (subject, body, sender). Returns thread ids for read_email_thread. | Read |
read_email_thread | Every message in one email conversation (from, to, date, subject and the new text of each message), the related lead and campaign. Use the email ids for create_draft_reply. | Read |
list_drafts | Your saved email drafts (including draft replies made here), newest first. | Read |
finance_overview | Cash in the bank, what customers owe (and how much is overdue), what you owe, revenue and profit this month and this year, who owes most and bills to pay. From the ledger. | Read |
list_invoices | Invoices (or credit notes) with their status, dates, totals and what is still to pay. Filter by status (draft, pending_approval, open, overdue, paid, void), customer or text. | Read |
get_invoice | One invoice or credit note with its lines, tax, payments and credits applied, and its history. Amounts are in minor units (cents). | Read |
financial_report | A report from the ledger: profit-loss, balance-sheet, cash-flow, trial-balance, general-ledger, ar-aging, ap-aging or tax. Ranges use from/to; balance sheet, trial balance and aging use as_of. Amounts in minor units of the base currency. | Read |
list_contracts | Contracts with their customer, status, dates, renewal and value. Filter by status (draft, approved, sent, signed, active, suspended, expired, terminated) or text. | Read |
get_contract | One contract: terms, price schedule, signers and their status, versions and activity (the document text is shortened). | Read |
list_tickets | Support tickets with status, priority, assignee and SLA state. Filter by status (open, new, pending, on_hold, resolved, closed, breached), priority, customer or text. | Read |
get_ticket | One support ticket with its whole conversation (internal notes included, marked), SLA clocks and history. | Read |
customer_health | Every customer’s health score (0–100) and grade (healthy, watch, at risk) with the reasons, upcoming renewals, NPS and CSAT. | Read |
create_draft_reply | Write a reply to an email and save it as a DRAFT in the person’s Inbox → Drafts. It is never sent: the person reviews and sends it from the app, where it goes out as a reply in the same conversation (with their signature). Give email_id (from read_email_thread) or thread_id (replies to the latest received message). | Mailbox action |
update_draft | Replace the text or subject of one of your drafts (from list_drafts or create_draft_reply). It stays a draft — never sent. | Mailbox action |
move_emails | Move conversations to Inbox, Archive, Spam or Trash (Trash can be restored by moving back to Inbox). Only the copies in this app change; the mail server is not touched. | Mailbox action |
mark_emails | Mark conversations as read, unread, starred or not starred. | Mailbox action |
draft_ticket_reply | Save a suggested answer on a support ticket as an INTERNAL NOTE marked as a draft. The customer does not see it and nothing is sent: a person reads it, edits it and sends the reply from the ticket. | Mailbox action |
list_notifications | Your newest notifications (alerts, approvals waiting, replies, failures), unread first. | Read |
get_timeline | Everything that happened with a lead, a company or a deal, newest first: emails, calls, notes, meetings, deals, invoices, payments, tickets, contracts. | Read |
add_note | Add a note to a lead, a company or a deal (it shows on its timeline). | Action |
create_lead | Add a new lead (prospect). It is scored, checked for duplicates and enriched like any lead added in the app. | Action |
update_lead | Change a lead’s details or pipeline status (new, contacted, replied, meeting, won, lost, nurture…). Only the fields you give change. | Action |
rescore_leads | Recalculate the fit and intent score of every lead (after changing scoring rules or adding signals). | Action |
convert_lead_to_customer | Turn a won lead into a customer: its company becomes a customer with its billing details. | Action |
list_customers | Companies that are customers (or former customers), with contacts, open deals and value. | Read |
create_company | Add a company (organisation) with its primary contact person (first and last name, and an email or phone). The person becomes the company’s primary contact, not a lead. Leads, deals, invoices and tickets can then be linked to it. | Action |
update_company | Change a company’s details. Only the fields you give change. | Action |
set_customer_status | Mark a company as a customer, a former customer (give the reason) or back to a prospect. | Action |
update_customer_billing | Set a customer’s billing details: the email invoices go to, legal name, tax id, billing address, currency and payment terms (days). | Action |
list_contacts | The people at a company (customer or prospect) with their roles: billing, signer, decision maker, champion… | Read |
add_contact | Add a person at a company. roles: billing, signer, decision_maker, champion, technical, operations, other. | Action |
update_contact | Change a contact’s name, title, email, phone, department or roles. | Action |
customer_statement | A customer’s account statement: invoices, payments and credits, and the balance they owe. | Read |
rescore_customer_health | Recalculate one customer’s health score (0–100) now, with its reasons. | Action |
get_deal | One deal with its stage, value, probability, close date, company, contact and history. | Read |
deal_stages | The pipeline stages (their keys are used by move_deal and create_deal). | Read |
create_deal | Open a deal for a company or a lead, with its value, stage and expected close date. | Action |
update_deal | Change a deal’s name, value, probability, expected close date or description. | Action |
move_deal | Move a deal to another stage, or mark it won or lost (with the reason). | Action |
get_task | One task with its instructions, checklist, comments and history. | Read |
create_task | Create a task — for yourself, or (with permission) for a teammate or an AI agent. assignee is "user:<id>" or "agent:<key>"; empty means you. | Action |
update_task | Change a task’s title, instructions, priority, dates, status (open, in_progress, blocked) or assignee. | Action |
complete_task | Mark a task done (or not needed), with a short note of what happened. | Action |
comment_on_task | Add a comment to a task. | Action |
list_calendar | Everything on the calendar between two dates: meetings, events, tasks, reminders and connected calendars. Default: today and the next 7 days. | Read |
create_event | Add an event to the calendar (a block of time, a call, a reminder for the team). | Action |
update_event | Change an event’s title, times, place, link or description. | Action |
delete_event | Delete a calendar event. Needs confirm: true — ask the person first and send it only after they agree. | Asks first |
list_reminders | Your reminders (active and paused) with their next time. | Read |
create_reminder | Set a reminder for yourself at a date and time (it arrives as a notification). | Action |
complete_reminder | Mark a reminder done. | Action |
book_meeting | Book a meeting with a lead (the invitation is sent to them). Needs confirm: true — ask the person first and send it only after they agree. | Asks first |
cancel_meeting | Cancel a meeting. Needs confirm: true — ask the person first and send it only after they agree. | Asks first |
approve_proposal | Approve a proposal (or a counter-offer) that is waiting for approval. | Action |
send_proposal | Send a proposal to the client by email. Needs confirm: true — ask the person first and send it only after they agree. | Asks first |
contract_templates | The contract templates you can start a contract from, with the statuses. | Read |
create_contract | Draft a contract for a customer from a template (it stays a draft until it is submitted and sent). | Action |
submit_contract | Submit a draft contract for approval (or mark it approved when no approval is needed). | Action |
send_contract | Send an approved contract for e-signature. Without signers, the contract’s contact signs for the customer. Needs confirm: true — ask the person first and send it only after they agree. | Asks first |
list_payments | Payments received (and refunds), with customer, amount, method and what they paid. | Read |
list_bills | Bills from vendors with their status, dates, totals and what is still to pay (minor units). | Read |
list_vendors | Vendors (suppliers) with what you owe each. | Read |
list_expenses | Expenses (receipts and card spend) with status and amounts (minor units). | Read |
chart_of_accounts | The accounts of the ledger (code, name, type) with balances — the account_id values used by expenses and journal entries. | Read |
list_journal_entries | Journal entries of the ledger (drafts, waiting for approval, posted). | Read |
list_bank_accounts | Bank accounts with balances and how many transactions wait to be matched. | Read |
list_bank_transactions | Transactions of one bank account, newest first; unmatched ones still need reconciling. | Read |
business_report | Business reports: recurring (MRR/ARR and movements), retention (churn cohorts), ltv (lifetime value), profitability (by customer or contract), budget-vs-actual, forecast (12-month revenue and cash). | Read |
list_budgets | Budgets by year with their totals. | Read |
create_invoice | Draft an invoice for a customer with its lines (prices in normal units, e.g. 1250.50). It stays a draft until it is submitted; nothing is sent. | Action |
submit_invoice | Submit a draft invoice: it is issued (gets its ledger entry) or goes for approval when a rule needs it. Nothing is emailed — use send_invoice. | Action |
send_invoice | Email an issued invoice to the customer, with the PDF and the pay link. Needs confirm: true — ask the person first and send it only after they agree. | Asks first |
send_payment_reminder | Email a payment reminder for an unpaid invoice. Needs confirm: true — ask the person first and send it only after they agree. | Asks first |
void_invoice | Void an invoice nothing was paid on (give the reason). Needs confirm: true — ask the person first and send it only after they agree. | Asks first |
record_payment | Record money received from a customer (bank transfer, check, cash, card…). It is applied to their oldest open invoices unless you name the invoices. | Action |
create_vendor | Add a vendor (supplier) to record bills from. | Action |
create_bill | Record a bill from a vendor with its lines (prices in normal units). It stays a draft until submitted. | Action |
submit_bill | Submit a draft bill: it is approved (and booked) or goes for approval. | Action |
create_expense | Record an expense (a receipt or a card payment). With submit: true it is submitted at once. | Action |
create_journal_entry | Draft a manual journal entry (debits must equal credits; amounts in normal units). It is posted with post_journal_entry. | Action |
post_journal_entry | Post a draft journal entry to the ledger. Needs confirm: true — ask the person first and send it only after they agree. | Asks first |
create_ticket | Open a support ticket for a customer (nothing is emailed to them). | Action |
update_ticket | Change a ticket’s status (new, open, pending, on_hold, resolved, closed), priority, category or assignee ("user:<id>" or "agent:<key>"). | Action |
add_ticket_note | Add an internal note to a ticket (only your team sees it). | Action |
reply_to_ticket | Reply to the customer on a ticket (the reply is emailed and shows in their portal). Needs confirm: true — ask the person first and send it only after they agree. | Asks first |
list_onboarding | Customer onboardings in progress (or finished) with their progress and overdue steps. | Read |
get_onboarding | One onboarding with every step (who does it, due date, done or not) — the step ids used by update_onboarding_step. | Read |
start_onboarding | Start an onboarding checklist for a customer (team steps become tasks; customer steps show in their portal). | Action |
onboarding_checklists | The onboarding checklist templates (their ids are used by start_onboarding). | Read |
update_onboarding_step | Mark an onboarding step done (or not done), or skip it. | Action |
list_portal_accounts | People at your customers who have client portal accounts, with status and last sign-in. | Read |
invite_to_portal | Invite someone at a customer to the client portal (they get an email to set a password). Needs confirm: true — ask the person first and send it only after they agree. | Asks first |
list_approvals | What waits for a person’s approval: outgoing messages drafted by agents, and documents (invoices, bills, contracts, proposals, journal entries) held by approval rules. | Read |
approve_message | Approve an outgoing message drafted by an agent (it is then sent). Needs confirm: true — ask the person first and send it only after they agree. | Asks first |
reject_message | Reject an outgoing message drafted by an agent (it is not sent), with a note the agent learns from. | Action |
decide_document_approval | Approve or reject a document (invoice, bill, contract, proposal, journal entry) held by an approval rule. Only when your role is one of its approvers. Needs confirm: true — ask the person first and send it only after they agree. | Asks first |
send_draft | Send one of your saved email drafts (e.g. a reply drafted with create_draft_reply) and remove it from Drafts. Needs confirm: true — ask the person first and send it only after they agree. | Asks first |
send_email | Send a new email from one of your mailboxes (list_mailboxes gives their ids). Plain text; your signature is added. Needs confirm: true — ask the person first and send it only after they agree. | Asks first |
pause_campaign | Pause a running campaign (nothing more is sent until it is resumed). | Action |
resume_campaign | Resume a paused campaign, or launch a ready one (launch: true). Needs confirm: true — ask the person first and send it only after they agree. | Asks first |
enroll_in_campaign | Enroll leads in a campaign. Needs confirm: true — ask the person first and send it only after they agree. | Asks first |
list_automations | Workflow automations with their trigger, whether they are on, and recent results. | Read |
switch_automation | Turn a workflow automation on or off. | Action |
run_automation | Run a workflow automation now. Needs confirm: true — ask the person first and send it only after they agree. | Asks first |
list_agents | The AI agents with their role, whether they are on or paused, and what they did lately. | Read |
pause_agent | Pause an AI agent (it stops taking new work) or resume it. | Action |
add_knowledge | Add an entry to the knowledge base the agents use (a fact, FAQ, policy, pricing note or playbook). It waits for review unless approved: true. | Action |
list_services | The services you sell with their prices and billing (the catalog used by proposals and invoices). | Read |
list_chats | Website chat conversations: waiting for a person, with a person, with the AI, or closed. | Read |
get_chat | One chat conversation with every message and the visitor’s details. | Read |
reply_to_chat | Take over a website chat and reply to the visitor. Needs confirm: true — ask the person first and send it only after they agree. | Asks first |
get_enrichment | The enriched details of a lead or company with their source, confidence, whether they are verified and what other sources said (conflicts), plus the latest enrichment runs. | Read |
enrich_record | Look up a lead’s or company’s missing details now: the enrichment providers are asked in the workspace’s order (registries, Google Maps, Apollo, Hunter, BuiltWith…), results are compared and verified, and blank fields are filled. Paid providers use credits. | Action |
feedback_summary | NPS, CSAT and CES, the response rate, the sentiment split, the top themes (with how negative each is), the trend by week and the answers that need attention, over a period (default 90 days), optionally for one form or audience (lead, lost_lead, customer, former_customer, contact, ticket, public). | Read |
list_feedback | Answers to feedback forms with their score, sentiment, themes and summary — filter by form, sentiment (positive, neutral, negative, mixed), theme, audience, a lead or company, or words. | Read |
send_feedback | Email a feedback form (see list_feedback_forms) to leads, companies (their main contact), contacts or addresses. People asked recently, test records and unsubscribed addresses are skipped. Needs confirm: true — ask the person first and send it only after they agree. | Asks first |
list_feedback_forms | The feedback forms (NPS, CSAT, CES, lost-deal and custom ones) with their questions, public link and response figures. | Read |
list_calls | Calls from RingCentral, Aircall or logged by hand: direction, result (answered, missed, voicemail, no_answer), duration, who took it, the lead or company, outcome and notes. Filter by lead, company, result, direction, provider, period or words. | Read |
call_stats | Call figures over a period (default 30 days): calls, answer and connect rates, missed incoming calls, talk time, leads reached, per person and per phone system, outcomes and the busiest hours. | Read |
log_call | Record a call made outside the connected phone systems on a lead’s timeline, with its result, length, outcome and notes. | Action |
report_issue | Report a problem with the app or an idea (bug, ui, error, feature, other) — it goes to Administration → Issues. | Action |
list_issues | Issues reported with Report an issue (all of them with issues:read; otherwise yours), with status and the fix link. | Read |
update_issue | Change an issue’s status, add a developer note or link the PR / commit that fixed it. | Action |
Disconnecting and control
- You can disconnect any AI app at any time on the AI connectors page in RCM Centric LLC; access stops at once. You can also remove the connector in the AI app.
- Administrators can see and disconnect everyone's connections, turn the connector, full access or mailbox actions off for the whole workspace, and switch off single tools.
- Every tool an app uses is listed in the activity on the AI connectors page.
Security
- OAuth 2.1 with PKCE (S256), resource indicators and dynamic or metadata-document client registration. The AI app never sees your password.
- Access keys last one hour and are renewed with a refresh key that is replaced on every use; reusing an old one ends the connection. Keys are stored only as hashes and work only for the connector.
- All traffic uses HTTPS. Each connection is limited to 120 calls a minute. A deactivated account loses access immediately.
How data is handled is described in the privacy policy.
Troubleshooting
| What you see | What to do |
|---|---|
| The app cannot reach the server | Use the address exactly as above, ending in /mcp. |
| “AI connectors are switched off” | An administrator can turn them on in RCM Centric LLC → AI connectors. |
| The app cannot draft or move emails | You connected with Read only, your role cannot send email, or mailbox actions are switched off. Change the connection’s access on the AI connectors page, or ask an administrator. |
| The app says it cannot create or change records | The connection does not have Full access, your role does not allow that change, or full access is switched off for the workspace. Change the access on the AI connectors page (Connections). |
| A mailbox is missing | The app sees the mailboxes you see in the Inbox. Ask an administrator to assign the mailbox to you. |
| “Two-step sign-in must be set up” | Set up two-step sign-in from your profile menu in RCM Centric LLC, then connect again. |
| The app keeps asking to sign in | The connection was disconnected, not used for 30 days, or your account was deactivated. Connect again. |
Support
Questions or problems: support@rcmcentric.com.