List your agent

Well

MCP serverHostedv0.2.1

Connect your AI to your Well financial data - invoices, companies, contacts

What you can do with it

Share of each task's required capabilities it covers

Prefer a ready-made agent?

An MCP server is a connector for your own assistant. These finished products do the job for you: send and chase invoices.
All AI agents to send and chase invoices, ranked →

Similar tools

Listed for the same task: send and chase invoices

Reviews

No review yet. Used Well? Be the first to help others choose.

What it does

Well is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.

From the publisher's description, Electra Index matched it to one capability: invoicing. That makes it a candidate for tasks such as send and chase invoices.

Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.

At a glance

Hosted (remote)YES
Local installNO
Version0.2.1
PriceNot in the registry
First seen26 Sept 2026
Last checked6d ago

How to connect

As declared in the Official MCP Registry · not tested by Electra Index

Hosted endpoint

  • https://api.wellapp.ai/v1/mcp streamable-http

In Claude Code: claude mcp add --transport http well https://api.wellapp.ai/v1/mcp

MCP settings (Claude Desktop, Cursor and other MCP clients)

{
  "mcpServers": {
    "well": {
      "url": "https://api.wellapp.ai/v1/mcp"
    }
  }
}

Live check

Electra Index connected to the hosted endpoint 1d ago

REACHABLE The endpoint answered but asks for an API key or a sign-in before connecting. Electra Index never sends credentials, so the tool list is not visible here.

492 tools offered to AI assistants

  • well_create_ledger_account · Create one native chart-of-accounts entry in the current workspace. Supply account_number, name and either account_type or a resolvable account_class. Duplicate live account numbers are refused. This defines an account without assigning it
  • well_update_ledger_account · Change the name, description or active state of one native ledger-account definition. Use ledger_account_id from well_query_records on ledger_accounts. An explicit null description clears it. Connector-owned accounts must change at the sour
  • well_delete_ledger_account · Soft-delete one unused native ledger account. Use ledger_account_id from well_query_records on ledger_accounts. Connector-owned accounts and accounts referenced by journal lines cannot be deleted. Ask for confirmation before deleting the de
  • well_create_payslip_line_rubric · Propose one user-authored payroll-line rubric in pending status. Supply source_label, effective_from, line_side and a postable credit_role, plus any classification fields the person specifies. This saves a rubric definition without activati
  • well_update_payslip_line_rubric · Correct one payroll-line rubric or request a permitted status transition. Use payslip_line_rubric_id from well_query_records on payslip_line_rubrics. Supply only fields to change. Explicit activation relinks matching lines and reposts affec
  • well_delete_payslip_line_rubric · Soft-delete one pending payroll-line rubric with no referenced payslip lines. Use payslip_line_rubric_id from well_query_records on payslip_line_rubrics. Active rubrics must be superseded through update; active, referenced and superseded ro
  • well_create_shipment · Create one native shipment in the current workspace. Supply the tracking_number and any known carrier_company_id, invoice_id, recipient_person_id (the person who receives a gift), shipped_at or delivered_at. Related IDs must belong to the s
  • well_update_shipment · Change one native shipment's carrier, tracking number, invoice, recipient person (who receives a gift) or shipment/delivery dates. Use shipment_id from well_query_records on shipments and supply only fields to change. Null clears a nullable
  • well_delete_shipment · Soft-delete one native shipment by shipment_id from well_query_records on shipments. Connected-source shipments cannot be deleted. Confirm the selected shipment before deleting it; its immutable timeline is retained.
  • well_create_journal · Create one journal. Only an owner or administrator can manage journals. Connector-owned and system journals stay protected; entries and posting mappings prevent deletion or a type change.
  • well_update_journal · Update one journal. Only an owner or administrator can manage journals. Connector-owned and system journals stay protected; entries and posting mappings prevent deletion or a type change. Use journal_id from well_query_records on journals.
  • well_delete_journal · Delete one journal. Only an owner or administrator can manage journals. Connector-owned and system journals stay protected; entries and posting mappings prevent deletion or a type change. Use journal_id from well_query_records on journals.
Show 88 more
  • well_create_workspace_category · Create one workspace tag. Only an owner or administrator can manage workspace tags. This never edits a shared company or transaction catalog. Linked tags must be detached before renaming or deletion; child tags must be removed first.
  • well_update_workspace_category · Update one workspace tag. Only an owner or administrator can manage workspace tags. This never edits a shared company or transaction catalog. Linked tags must be detached before renaming or deletion; child tags must be removed first. Use ca
  • well_delete_workspace_category · Delete one workspace tag. Only an owner or administrator can manage workspace tags. This never edits a shared company or transaction catalog. Linked tags must be detached before renaming or deletion; child tags must be removed first. Use ca
  • well_create_workspace_category_override · Create one category override. Only an owner or administrator can change a workspace category override. Hide, relabel or reorder a shared company or transaction category for this workspace. Set at least one override value: a create with none
  • well_update_workspace_category_override · Update one category override. Only an owner or administrator can change a workspace category override. Hide, relabel or reorder a shared company or transaction category for this workspace. A change that would clear every override value is r
  • well_delete_workspace_category_override · Delete one category override. Only an owner or administrator can change a workspace category override. Hide, relabel or reorder a shared company or transaction category for this workspace. The delete removes the override, so the catalog def
  • well_create_chat_conversation · Create one empty conversation owned by the current member. An optional title names it. This saves the conversation without sending a message or running an assistant turn.
  • well_update_chat_conversation · Change the title or saved tabs of one conversation the current member owns. Use thread_id from the chat_conversations records. An active_tab_key must name a tab in the saved list; null clears the selection. Conversation history and routing
  • well_delete_chat_conversation · Soft-delete one conversation owned by the current member after confirmation. Use thread_id from chat_conversations records. Other members' owned conversations and foreign workspace records are refused; legacy ownerless conversations keep th
  • well_delete_canvas · Soft-delete one board after confirmation. Use canvas_view_id from well_show_canvas or the canvas_views records. Only its author or a workspace owner or administrator can delete it. The same transaction revokes the board's share links.
  • well_create_skill · Save one skill in this workspace, without executing it. A reference or action skill takes its name, full body and skill_kind. A layout skill takes its name, skill_kind layout and source_board_id, and saves the blocks of that board with no f
  • well_update_activity · Change the day or duration_seconds of one manually logged work activity. Use activity_id from well_query_records on activities. The activity must have one resolved participant. Source-owned, approved and billed values keep their existing lo
  • well_delete_activity · Delete one manually entered activity and its participation rows by activity_id. Source-owned, approved or billed activity is refused. This does not cancel a calendar meeting; use the calendar-event tool for that gesture.
  • well_update_activity_participant · Change one participant of an activity. Supply activity_id and exactly one selector: person_id or email. Change duration_seconds, response_status or is_optional. Numeric row keys are not accepted. Source-owned and approved rows, and billed d
  • well_create_workspace_view · Save one records view with its root, name, columns, filters, sort and layout, for example to keep a list the person was shown as a named view. Read the root's field schema first. This saves a reusable view without changing its source record
  • well_update_workspace_view · Change one saved records view by view_id. Supply only the fields to change. A default view's filters, sort and grouping are protected: create a separate working view for those changes. This changes the saved view without changing its source
  • well_delete_workspace_view · Delete one saved records view by view_id. This removes the saved view and keeps its source records.
  • well_update_skill · Change one saved skill's name, description, body or visibility. Find its skill_id with well_query_records on skills. Supply only the fields to change; null clears the description. The skill kind is immutable. This changes the saved definiti
  • well_delete_skill · Soft-delete one saved reference or action skill from this workspace after confirmation. Find its skill_id with well_query_records on skills. Foreign and deleted records are refused. This removes the saved skill without executing its body.
  • well_get_schema · Discover available data types and fields. USAGE: - well_get_schema() → List ALL available roots, including the accounting graph (ledger_accounts, journals, journal_entries) plus account_balances, tax_rates, exchange_rates — query these for
  • well_query_records · Read records from Well's context graph FOR YOUR OWN WORK. This draws nothing on the user's screen. Use it for every read whose answer is yours rather than the reader's: a gate checking whether a window holds transactions, a `totalCount` an
  • well_create_company · Create a new company in the current workspace. Use this tool when the user asks to create, add, or register a new company. REQUIRED: name OPTIONAL: description, domain, is_company, registry_ref Pass domain when the person gives the company'
  • well_record_writing_feedback · Record a writing preference for the caller. Use it when the caller gives feedback about their own writing style. Feedback must contain 1 to 300 characters. The result says whether the feedback was saved and names the scope it was saved to:
  • well_create_writing_style_training · Start learning the caller's writing style from their recent sent emails, in the background. When the person mentions their writing style or tone, offer to learn it; call this tool only when they ask for it or agree. The status means: "start
  • well_create_person · Create a new person (contact) in the current workspace. Use this tool when the user asks to add, create, or register a new contact, employee, or person. REQUIRED: first_name OPTIONAL: last_name, job_title, email, phone, company_id, address,
  • well_update_company · Update an existing company in the current workspace. Use this tool when the user asks to change, fix, rename, or edit a company's fields. REQUIRED: company_id OPTIONAL (only include fields the user wants changed): name, description, domain,
  • well_update_person · Update an existing person (contact) in the current workspace. Use this tool when the user asks to change, fix, rename, or edit a person's fields. REQUIRED: person_id OPTIONAL (only include fields the user wants changed): first_name, last_na
  • well_delete_company · Delete a company from the current workspace (soft delete). Use this tool when the user asks to delete, remove, or archive a company. When the user says the company is a duplicate of another one, use well_merge_company instead: a merge moves
  • well_delete_person · Delete a person (contact) from the current workspace (soft delete). Use this tool when the user asks to delete, remove, or archive a contact. REQUIRED: person_id This soft-deletes the person and its company_person relationships. Linked comp
  • well_update_invoice · Update an existing invoice in Well. Call well_get_schema("invoices") to discover all available fields. REQUIRED: invoice_id OPTIONAL (only pass fields you want changed): - reference_number, issue_date (ISO date), due_date (ISO date) - statu
  • well_set_subscription_quantity · Set the seat count of one subscription in the current workspace. Use this tool when the user states how many seats a subscription covers. Find the subscription_id first. The count replaces the stored count: it is never added to it. A count
  • well_delete_invoice · Delete an invoice from Well (soft delete). REQUIRED: invoice_id Needs the invoice right (owner, admin, or a member who keeps it). Soft-deletes the invoice. Linked line items and payment_means rows are NOT cascade-deleted — they remain in th
  • well_add_contact_channel · Add a contact channel to a company or person. Wraps the resource-scoped REST endpoints (POST /v1/{companies,people}/:id/{emails,phones,web-links,locations}). channel + the matching value field: - email → value.email - phone → value.e164_num
  • well_remove_contact_channel · Remove a contact channel from a company or person. Wraps the resource-scoped DELETE endpoints (DELETE /v1/{companies,people}/:id/{emails,phones,web-links,locations}/:channelId). Pass channel_id = the UUID of the specific channel row to remo
  • well_update_web_link · Change one web link (a website, LinkedIn, X/Twitter, GitHub or other profile URL) of a company or a person in the current workspace. Use this tool when the user asks to fix, replace or edit a link the record already has. To add a new link u
  • well_get_entity · Read ONE entity with its sub-resources nested in a single call. Convenience over well_get_schema + well_query_records: resolves the field paths for you and returns the single record with its related data expanded. depth (relation-nesting BO
  • well_list_connector_tools · Discover the actions a connected provider exposes (e.g. "what can I do with Attio?"). WORKFLOW: 1. well_list_connectors() → pick the connected provider (connection_status "enabled" or "processing": a connection whose sync was started still
  • well_invoke_connector_tool · Run one tool on a connected provider's own MCP server, on behalf of this workspace's connection: an action the user asked to take there (create a record in Attio), or a read of content Well does not sync (a page in a docs tool, a note in a
  • well_create_invoice_from_data · Load the draft-invoice skill with well_get_skill before you call this. Create an invoice in Well from data you extracted by reading an invoice (your own OCR) — you send the structured fields, not the file. Never call it to add a product or
  • well_create_invoice_time_entries · Add logged time entries to one existing Well invoice draft. Pass public activity_id and person_id pairs in `participants` for an explicit selection, or `unbilled` to draft one line per project from the draft's own customer's billable hours
  • well_issue_invoice · Issue a draft invoice: it becomes a full invoice. The invoice takes the workspace's next invoice number and, from then on, can no longer be edited or deleted. To correct an issued invoice, create a credit note that refers to it. REQUIRED: i
  • well_create_invoice_from_quote · Turn an accepted sales quote (type 310) into an invoice draft (type 380) with the quote's customer, currency, lines and payment account. The draft is then issued with well_issue_invoice like any draft, and takes the invoice number. Refused
  • well_list_workspaces · List the workspaces this connection is authorized to access. This draws nothing on the user's screen. Use this FIRST when a single token may cover more than one workspace, and settle on your OWN every case you can: exactly one workspace, a
  • well_list_connectors · List the connectors a workspace can install AND everything it has already connected, each with a one-click install deep link. The result DRAWS THE CONNECT CARD the user clicks in. It is also the answer to "which connectors can bring this pr
  • well_run_register_diff · Diff a workspace's bank transactions against its accounting-register transactions (e.g. QuickBooks), and persist the result. - Every match — hard evidence (structured reference, IBAN, tax ID) or inference-only (memo/payee reading) — is rais
  • well_run_reconciliation · Start a reconciliation run for the workspace now: Well matches the open bank lines, invoices and payments, then sends the member the list of what it linked. Call it when the member asks Well to reconcile or match their transactions now. Run
  • well_resolve_reconciliation_task · Approve or reject one or more reconciliation review tasks (from well_run_register_diff or the in-app review queue). - approve: confirms the match — the link is flipped to active. - reject: dismisses the match — the candidate does not silent
  • well_resolve_register_diff_gap · Post a well_run_register_diff gap (one of missing_in_register_ids' review tasks) into QuickBooks as a Purchase or Deposit. Requires the exact ledger_account_id (a UUID, not a name) for both: - bank_ledger_account_id: the bank/cash account t
  • well_get_investment_holdings · Get the live holdings/positions (what's currently held and its value) for a connected Plaid investment account — brokerage, IRA, 401k, etc. WORKFLOW: 1. well_list_connectors() → pick the ENABLED Plaid connector (connection_status: "enabled"
  • well_render_cost_structure · Put a cost breakdown YOU computed onto the cost-structure card. **This tool measures nothing.** It takes the slices and the method behind them as input and returns them for rendering. Call it only after you have computed the breakdown yours
  • well_get_own_company · Get which company the workspace itself is: the confirmed own-company anchor (`anchor`) and the detected companies not yet confirmed as it (`candidates`). Call this directly, with no workspace call first: both come from the workspace this ca
  • well_list_missing_invoices · List the supplier invoices a past period is still missing — the settled spend whose invoice has not been collected, one row per counterparty, exactly as the Well app's expense-invoices card shows them. Use it for "which invoices am I missin
  • well_sum_missing_invoices · The missing supplier invoices of one ISO week, or of up to 3 calendar months, as one total: how many suppliers still miss an invoice, how many transactions they cover, and the spend they cover, in the currency of the lines and converted to
  • well_list_periods · List the recent accounting months of the workspace, with each month's close status, its invoice-retrieval state, and the counts that describe how much work it holds. Use this to ask the user WHICH month or months to work on before any close
  • well_preview_invoice_fetch · Preview which vendors a past period is still missing supplier invoices from, where each one's invoices are, and which route would obtain them. Use it for "what would happen if I fetched <month>'s missing invoices?" before anything runs. Nam
  • well_switch_workspace · Write this conversation's context: the one place its standing choices live. This is the tool the widget cards call when the user CLICKS them: the workspace pin and queue, the selected months, the selected counterparties, and the step acknow
  • well_list_counterparties · List the workspace's counterparty companies and how each one is CATEGORIZED — the company-level industry labels a counterparty carries. Use it for "which suppliers have no category?", "what industries are my counterparties in?", and before
  • well_wait_for_selection · Read the user's card click, holding the turn open until it lands. Call it in the SAME turn, right after the tool whose card asks the user to click: well_list_workspaces (kind "workspace"), well_list_periods (kind "periods"), well_list_missi
  • well_wait_for_process · Waits up to 5 seconds for one background process of the workspace and returns where it stands. Before each call, announce it with the sentence for its kind, and nothing else, unless the skill says to make that call with no announce sentence
  • well_set_own_company · Open the workspace's "Confirm your company" task for a company, or point to the one already open. This tool never anchors the company itself: a person confirms the company in Well, and only that confirmation writes it. The result carries co
  • well_get_design_tokens · Get Well's colours, shape and type vocabulary, so a view you compose for Well data looks like Well rather than a generic page. Call this ONLY when you are about to render something yourself — an HTML artifact, a report, a chart you are draw
  • well_create_statement_upload · Mint a one-time, short-lived upload slot for a bank-statement file. Use this when the user has a statement file (PDF, or a large CSV/XML) to import; the file's bytes do not travel through the model. It returns a single-use upload URL + toke
  • well_upsert_accounting_settings · Set the workspace's accounting settings: fiscal year start month, first fiscal year start date, country, base currency, accounting framework, chart-of-accounts confirmation, the next invoice number (typed, Well's preset first number saved o
  • well_search_context · Search the workspace's recorded notes and context (meeting notes, tickets, imported documents, and the caller's own imported emails) for a query. Returns compact snippets — each result's "snippets" is an array of one or more matched passage
  • well_search_mailbox_for_receipt · Search the caller's own live Gmail and Outlook mailboxes for one supplier's messages in a date window. It checks up to 3 grants per provider, from `from` to `to` inclusive, and returns up to `max_results` messages from each mailbox, newest
  • well_get_memory · Read what Well remembers about this workspace and about the user: standing decisions (how a supplier's transactions are categorised, which company the workspace is), stated preferences (currency, report format), facts saved from chats, sett
  • well_remember · Keep lines in Well's memory, so its assistant uses them in later conversations. Call it when the user states a fact or a like about themselves or a contact, when the user asks you to remember or save something, and for a measured line or a
  • well_forget_memory · Forget memory lines, when the user asks to forget or correct something Well remembers. In Well chat, use all: true to forget every line; for one line, use well_delete_memory_line. Over MCP, name a line with the ids well_get_memory returns,
  • well_get_statement_import_result · Read the outcome of a bank-statement upload started with well_create_statement_upload, by the document_id that tool returned. well_create_statement_upload already renders a card from its own result — this tool does not create or redraw it.
  • well_upload_statement_content · Upload a bank statement's TEXT CONTENT (a .csv, .txt, or .xml file) directly, as an alternative to well_create_statement_upload's out-of-band file POST. Use it when the user's statement is a small text file whose contents are verbatim in th
  • well_upload_statement_bytes · Upload a bank statement file's BINARY CONTENT (PDF or image) as base64, so the file's real bytes reach Well without any out-of-band HTTP call. Use it for PDF and image statements up to 5 MiB decoded (the base64 text may be roughly a third l
  • well_assign_account · Attach a bank account to a company, and say whether the workspace owns it. Use this when an account carries no company, or when its ownership is still `unknown` — the two states a figure that walks account ownership cannot be computed over.
  • well_list_uncategorized_window · List the transactions in a date window that carry no category, so a figure that depends on categorization can say exactly what is missing before it is computed. `from` is inclusive and `to` is EXCLUSIVE — for whole months, pass the first da
  • well_render_burn · Put a burn figure YOU computed onto the burn card. **This tool measures nothing.** It takes the figure and its method as input and returns them for rendering. Call it only after you have computed the burn yourself and can state every field
  • well_sum_transactions · Sum a workspace's transactions over a date window, grouped how you ask. Arithmetic only — this tool holds no definition of burn, spend, or runway, and returns no figure the app renders. Use it when you are computing a figure whose RULES you
  • well_list_possible_double_debits · Find the pairs of outgoing bank movements that may be one charge taken twice, and say how many movements were scanned to find them. Use it for "was I charged twice?", "double debit", "prélevé deux fois" or "doublon de prélèvement" about a s
  • well_measure_subscriptions · Measure the workspace's subscriptions from its bank and credit card outflows: which suppliers it pays on a regular cadence, what each costs per month and per year, and how the spend moved month by month. It draws no card. Call it when the u
  • well_list_subscription_rows · Read the active typed subscription rows on one side of this workspace's own company. Use side=sold for subscriptions the workspace sells to clients, or side=buy for subscriptions it buys from suppliers. This read applies the server's exact
  • well_measure_category_trend · Measure ONE spending category for one month against its usual month: the month total, the usual amount, and the difference. It draws no card. Call it when the person asks how much they spent on one category in a month, or how a month compar
  • well_measure_recurring_inflows · Measure who pays the workspace on a regular cadence, from its bank and credit card inflows: each recurring payer, its cadence, what it brings in per month, and the total per currency. It draws no card. Call it when a cash forecast should co
  • well_measure_days_to_pay · Measure how many days the workspace's customers take to pay: the median and the mean days from a sale invoice's issue date to the day it was paid, over the paid sale invoices settled between `from` (inclusive) and `to` (exclusive), both as
  • well_measure_month_to_date_spend · Measure the spend so far this month against the same number of days last month, in a personal space: one comparison per currency, with both figures and their difference. Quote `month_to_date_spend`, `same_days_last_month_spend` and `differe
  • well_list_upcoming_payments · List the payments still to come in a personal space, from its bank and credit card history: each recurring debit with its next day and amount, a running total, and the next recurring inflows (payday among them) with what is left before each
  • well_render_category_trend · Put a month-by-month trend with one line per category onto the category-trend card. **This tool measures nothing.** Pass a trend another tool measured, as it is: for subscriptions, one `category_trends` entry of `well_measure_subscriptions`
  • well_render_monthly_pivot · Put a table of amounts per company and per month onto the monthly-pivot card: one row per company with its logo and name, an optional category column, then one column per month. The running month is drawn apart, at the end, marked as in pro
  • well_sum_invoices · Sum a workspace's billed amounts over a window of whole months, grouped by month, currency and billing context. Arithmetic only — this tool holds no definition of MRR or recurrence, and returns no figure the app renders. Use it when you are
  • well_sum_receivables · What the workspace's customers still owe it: the outstanding receivables, one figure per currency, with the overdue part and an aging breakdown. It draws nothing. Use it for any total of what customers owe: "who owes us money", "how much ar
  • well_sum_payslips · The payroll total of a window of whole months, summed on the server from the payslips: gross pay, net pay, employee deductions, employer charges and the payslip cost, one group per currency, and per month when `axes` holds "month". It draws

The first 100 are shown.

What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method

Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.

Facts & evidence

Each fact shows where it was seen and when.
FactValueEvidenceSourceLast confirmed
Hosted endpointhttps://api.wellapp.ai/v1/mcpDECLAREDSRC-001 Official MCP Registry6d ago
Local install (package)noDECLAREDSRC-001 Official MCP Registry6d ago
Remote access (hosted)yesDECLAREDSRC-001 Official MCP Registry6d ago
Websitehttps://docs.wellapp.ai/mcp/introductionDECLAREDSRC-001 Official MCP Registry6d ago
Repositoryhttps://github.com/WellApp-ai/well-mcpDECLAREDSRC-001 Official MCP Registry6d ago
Registry statusactiveDECLAREDSRC-001 Official MCP Registry6d ago
Version0.2.1DECLAREDSRC-001 Official MCP Registry6d ago
MCP serveryesDECLAREDSRC-001 Official MCP Registry6d ago

Change history

Baseline
No change detected yet. History builds up as the robots revisit this server.

Is this page accurate?

Flag it and our robot re-checks the official source. Reports never change a score.

Do you run Well? Know when it stops answering

For publishers · optional

Its hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.

Monitor WellLaunch offer $39.99 once, for life instead of $9.99/month · All plans

Monitoring never changes a score or a rank.

Are you the publisher of Well?

Free · show your listing

An independent listing builds trust with your buyers. Announce it, and add the badge to your website or README.

Announce it on LinkedIn
Listed on Electra IndexListed on Electra Index
<a href="https://electraindex.com/mcp/well?utm_source=badge&utm_medium=share&utm_campaign=listing"><img src="https://electraindex.com/api/badge/well/card" width="260" height="72" alt="Listed on Electra Index"></a>

Questions about Well

How do I connect Well?

Use the hosted endpoint https://api.wellapp.ai/v1/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.

What tools does Well offer?

When Electra Index connected on 13 Nov 2026, it listed 492 tools: well_create_ledger_account, well_update_ledger_account, well_delete_ledger_account, well_create_payslip_line_rubric, well_update_payslip_line_rubric, well_delete_payslip_line_rubric, well_create_shipment, well_update_shipment and more. The full list is in "Live check" above.

What can I use Well for?

Based on its description, it is most relevant to: send and chase invoices.