well_get_design_tokens — Well MCP Tool
well_get_design_tokens
(well get design tokens) is one of 87 tools on the
Well
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call well_get_design_tokens from your client
- Claude Code Well well_get_design_tokens run in your project directory
- Claude Desktop Well well_get_design_tokens ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Well well_get_design_tokens ~/.cursor/mcp.json
- VS Code Well well_get_design_tokens .vscode/mcp.json
- Zed Well well_get_design_tokens ~/.config/zed/settings.json
- Windsurf Well well_get_design_tokens ~/.codeium/windsurf/mcp_config.json
- Cline Well well_get_design_tokens ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Well well_get_design_tokens ~/.gemini/settings.json
- Grok Well well_get_design_tokens .mcp.json (in your project root)
- ChatGPT Well well_get_design_tokens Settings → Connectors → Advanced → Developer mode
- Claude.ai Well well_get_design_tokens Settings → Connectors → Add custom connector
- LangChain Well well_get_design_tokens pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http well-mcp https://api.wellapp.ai/v1/mcpOther tools on this server
- well_get_schema
- well_query_records
- well_create_company
- well_create_person
- well_update_company
- well_update_person
- well_delete_company
- well_delete_person
- well_update_invoice
- well_delete_invoice
- well_add_contact_channel
- well_remove_contact_channel
- well_get_entity
- well_list_connector_tools
- well_invoke_connector_tool
- well_create_invoice_from_data
- well_list_workspaces
- well_list_connectors
- well_run_register_diff
- well_resolve_reconciliation_task
- well_resolve_register_diff_gap
- well_get_investment_holdings
- well_render_cost_structure
- well_create_invoice_document
- well_get_own_company
- well_list_missing_invoices
- well_list_periods
- well_preview_invoice_fetch
- well_switch_workspace
- well_list_counterparties
- well_wait_for_selection
- well_set_own_company
- well_create_statement_upload
- well_upsert_accounting_settings
- well_search_context
- well_get_statement_import_result
- well_upload_statement_content
- well_upload_statement_bytes
- well_assign_account
- well_list_uncategorized_window
- well_render_burn
- well_sum_transactions
- well_sum_invoices
- well_render_mrr
- well_list_account_balances
- well_render_cash_position
- well_list_cash_scope
- well_render_runway
- well_render_cash_forecast
- well_render_cash_flow_bridge
- well_list_burn_exemptions
- well_list_recurring_contexts
- well_list_member_candidates
- well_invite_members
- well_enqueue_invoice_fetch
- well_list_missing_invoice_owners
- well_assign_missing_invoice_owners
- well_get_skill
- well_search_skill
- well_set_transaction_category
- well_list_accounts_needing_company
- well_list_unposted_transactions
- well_set_transaction_ledger_account
- well_show_records
- well_get_worklist_status
- well_get_connector_coverage
- well_show_workspace_picker
- well_get_session_digest
- well_propose_next_steps
- well_search_company_registry
- well_create_company_candidate
- well_create_company_workspace
- well_show_company_candidates
- well_get_accounting_settings
- well_show_accounting_settings
- well_list_retargetable_connectors
- well_show_retargetable_connectors
- well_retarget_connectors
- well_upload_document
- well_get_customer_einvoicing_details
- well_claim_statement_draft
- well_get_graph
- well_set_counterparty_default_category
- well_list_unposted_journals
- well_repost_journals
- well_list_ledger_accounts
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.