// MCP TOKEN COST

The FavCRM MCP server costs 46,401 tokens before the first call.

Every request your agent makes carries every tool definition this server exposes — context your code, documents and conversation can't use, mostly for tools the agent never calls. You don't need them all in the window, and you don't have to pay for them.

QUICK ANSWER The FavCRM MCP server's 220 tool definitions consume 46,401 tokens — 23% of a 200k context window, and 22× the median MCP server (2,142 tokens). A scoped grant exposing only the tools you use cuts that roughly in proportion.

MEASURED FROM SCHEMAS tiktoken o200k_base · rank #25 of 5,402 measured servers · refreshed every build Method →

// CONTEXT WINDOW SHARE

What that costs before your agent starts working.

Tool definitions are overhead: they occupy context on every request and compete with your code, documents and conversation history for the same window.

200K WINDOW 23%

1M WINDOW 4.6%

Corpus context: FavCRM ranks #25 of 5,402 measured MCP servers by definition cost. The median is 2,142 tokens, p90 is 11,749, and the heaviest (Ainumbers Mcp Apps) is 161,750 — 81% of a 200k window on its own. New to this? See MCP token cost and context window in the glossary.

Token cost is one axis. See the risk picture across your whole stack →

// PER-TOOL BREAKDOWN

Where the 46,401 tokens go.

Each row is one tool definition as a tools/list entry — name, description and input schema — counted with o200k_base. Average: 211 tokens per tool.

Tool	Category	Tokens	% of server
replace_post_block	Write	4,393	9.5%
create_post	Write	2,828	6.1%
update_post	Write	2,744	5.9%
append_post_block	Write	2,390	5.2%
preview_customer_import	Read	682	1.5%
list_notification_logs	Read	679	1.5%
commit_customer_import	Write	678	1.5%
create_post_type_field	Write	652	1.4%
update_post_type_field	Write	584	1.3%
create_service	Write	498	1.1%
report_agent_issue	Write	497	1.1%
update_account	Write	468	1.0%
search_members	Read	464	1.0%
update_booking_settings	Write	464	1.0%
update_segment	Write	450	1.0%
create_account	Write	444	1.0%
create_promotion	Write	435	0.9%
create_segment	Write	421	0.9%
update_service	Write	397	0.9%
preview_segment_count	Read	382	0.8%
create_campaign	Write	346	0.7%
create_team_member_invite	Write	345	0.7%
generate_post_cover	Write	340	0.7%
update_service_schedule	Write	339	0.7%
update_deal	Write	337	0.7%
register_organisation_request	Write	331	0.7%
create_service_schedule	Write	308	0.7%
generate_image	Write	307	0.7%
update_survey	Write	306	0.7%
update_service_package	Write	304	0.7%
create_template	Write	294	0.6%
create_outlet	Write	293	0.6%
list_audit_logs	Read	285	0.6%
create_post_type	Write	284	0.6%
create_service_package	Write	284	0.6%
create_deal	Write	282	0.6%
create_survey_invitation	Write	281	0.6%
create_survey	Write	280	0.6%
create_offer_rule	Write	271	0.6%
update_outlet	Write	263	0.6%
attach_post_cover_from_job	Write	260	0.6%
update_campaign	Write	258	0.6%
update_promotion	Write	256	0.6%
create_custom_field	Write	246	0.5%
create_subscription	Financial	241	0.5%
upsert_survey_workflow	Write	234	0.5%
request_send_approval	Write	233	0.5%
create_inbox_reply_suggestion	Write	227	0.5%
set_staff_availability	Write	227	0.5%
create_ticket	Write	225	0.5%
create_invoice	Write	224	0.5%
create_variation	Write	224	0.5%
update_post_type	Write	224	0.5%
set_resource_availability	Write	219	0.5%
post_workroom_message	Write	205	0.4%
create_booking	Write	204	0.4%
search_tools	Read	200	0.4%
create_plan_upgrade_link	Financial	197	0.4%
record_invoice_payment	Financial	197	0.4%
create_product	Write	196	0.4%
update_product	Write	194	0.4%
set_custom_field_values	Write	189	0.4%
list_bookings	Read	184	0.4%
update_custom_field	Write	180	0.4%
check_plan_operation	Read	179	0.4%
create_broadcast	Write	177	0.4%
earn_loyalty_points	Write	172	0.4%
update_task	Write	172	0.4%
create_task	Write	171	0.4%
list_tickets	Read	167	0.4%
list_invoices	Read	166	0.4%
validate_promotion	Read	163	0.4%
upload_post_cover_from_url	Write	159	0.3%
clone	Write	158	0.3%
query_favcrm_platform	Read	157	0.3%
accept_team_invite_verify	Write	157	0.3%
create_resource	Write	154	0.3%
query_company_knowledge	Read	152	0.3%
create_whatsapp_connect_link	Write	152	0.3%
find_or_create_workroom_thread	Write	151	0.3%
list_conversations	Read	149	0.3%
list_service_schedules	Read	147	0.3%
list_knowledge_documents	Read	144	0.3%
list_service_packages	Read	142	0.3%
enrol_membership	Financial	142	0.3%
list_deals	Read	136	0.3%
list_campaigns	Read	135	0.3%
search_audit_logs	Read	135	0.3%
get_attachment_text	Read	134	0.3%
add_knowledge_text	Write	134	0.3%
register_organisation_verify	Write	133	0.3%
delete_post_type_field	Destructive	132	0.3%
list_posts	Read	132	0.3%
execute_tool	Execute	131	0.3%
create_product_category	Write	129	0.3%
issue_rewards	Write	129	0.3%
create_category	Write	127	0.3%
scrape_knowledge_url	Write	126	0.3%
create_contact	Write	126	0.3%
create_note	Write	126	0.3%
get_available_slots	Read	124	0.3%
list_tasks	Read	123	0.3%
update_contact	Write	123	0.3%
reorder_post_blocks	Write	119	0.3%
update_category	Write	118	0.3%
list_products	Read	116	0.2%
list_notes	Read	114	0.2%
list_offer_rules	Read	113	0.2%
list_orders	Read	112	0.2%
accept_team_invite_request	Write	111	0.2%
reorder_post_type_fields	Write	110	0.2%
set_segment_members	Write	109	0.2%
revert_audit_action	Write	107	0.2%
update_order_status	Write	107	0.2%
get_custom_field_values	Read	106	0.2%
remove_post_block	Destructive	105	0.2%
get_conversation_messages	Read	103	0.2%
attach_tags	Write	102	0.2%
update_tag	Write	102	0.2%
list_promotions	Read	100	0.2%
create_service_category	Write	100	0.2%
list_surveys	Read	99	0.2%
switch_company	Execute	99	0.2%
list_services	Read	98	0.2%
list_subscriptions	Read	97	0.2%
list_templates	Read	97	0.2%
list_contacts	Read	96	0.2%
detach_tags	Write	96	0.2%
get_knowledge_document	Read	95	0.2%
update_deal_stage	Write	95	0.2%
update_ticket_status	Write	93	0.2%
list_custom_fields	Read	92	0.2%
assign_staff_to_service	Write	92	0.2%
list_post_type_fields	Read	91	0.2%
void_invoice	Destructive	88	0.2%
get_loyalty_balance	Read	87	0.2%
list_survey_invitations	Read	85	0.2%
create_tag	Write	85	0.2%
delete_post_type	Destructive	83	0.2%
mark_invoice_sent	Write	83	0.2%
restore_post_type_field	Write	83	0.2%
search_crm	Read	82	0.2%
get_segment_members	Read	80	0.2%
list_reward_schemes	Read	80	0.2%
delete_knowledge_document	Destructive	78	0.2%
link_resource_to_service	Write	78	0.2%
cancel_subscription	Financial	77	0.2%
delete_account	Destructive	77	0.2%
get_survey_responses	Read	77	0.2%
list_segments	Read	77	0.2%
cancel_booking	Destructive	76	0.2%
set_primary_contact	Write	76	0.2%
delete_invoice	Destructive	75	0.2%
validate_campaign	Read	75	0.2%
delete_contact	Destructive	74	0.2%
pause_subscription	Write	74	0.2%
get_audit_log	Read	73	0.2%
delete_category	Destructive	71	0.2%
mark_no_show	Write	71	0.2%
delete_campaign	Destructive	70	0.2%
delete_post	Destructive	70	0.2%
get_survey	Read	70	0.2%
list_image_models	Read	69	0.1%
get_service_detail	Read	68	0.1%
get_booking_detail	Read	67	0.1%
get_dashboard_stats	Read	67	0.1%
get_subscription	Read	67	0.1%
complete_booking	Write	67	0.1%
delete_tag	Destructive	66	0.1%
get_invoice	Read	66	0.1%
get_segment	Read	66	0.1%
get_service_package	Read	66	0.1%
delete_deal	Destructive	65	0.1%
get_post	Read	65	0.1%
archive_survey	Write	65	0.1%
delete_custom_field	Destructive	64	0.1%
get_member_profile	Read	64	0.1%
get_offer_rule	Read	64	0.1%
get_plan_status	Read	64	0.1%
get_product	Read	64	0.1%
get_survey_stats	Read	64	0.1%
get_whatsapp_connection_status	Read	64	0.1%
list_outlets	Read	64	0.1%
restore_service_package	Write	64	0.1%
get_membership_tier	Read	63	0.1%
get_promotion	Read	63	0.1%
restore_post_type	Write	63	0.1%
delete_promotion	Destructive	62	0.1%
delete_service_package	Destructive	62	0.1%
get_custom_field	Read	62	0.1%
list_survey_workflows	Read	62	0.1%
get_deal	Read	61	0.1%
restore_invoice	Write	61	0.1%
restore_knowledge_document	Write	61	0.1%
delete_task	Destructive	60	0.1%
get_order	Read	60	0.1%
list_my_companies	Read	60	0.1%
list_resources	Read	60	0.1%
delete_segment	Destructive	59	0.1%
get_contact	Read	59	0.1%
get_task	Read	59	0.1%
list_post_types	Read	59	0.1%
confirm_booking	Write	59	0.1%
restore_category	Write	59	0.1%
restore_post	Write	59	0.1%
resume_subscription	Write	59	0.1%
restore_promotion	Write	58	0.1%
list_plan_options	Read	57	0.1%
list_staff	Read	57	0.1%
restore_campaign	Write	57	0.1%
get_booking_settings	Read	56	0.1%
get_invoice_stats	Read	56	0.1%
list_service_categories	Read	54	0.1%
list_tags	Read	54	0.1%
get_booking_stats	Read	53	0.1%
list_tiers	Read	46	0.1%
list_shipping_methods	Read	45	0.1%
list_product_categories	Read	44	0.1%
get_ticket_stats	Read	43	0.1%
list_categories	Read	40	0.1%

// CUT THE COST

Your agent uses a handful of these tools. It pays for all 220.

You don't need all 220 of those definitions in the window. PolicyLayer is an MCP gateway that sits in front of FavCRM: only the tools you grant are exposed to the agent, the rest never load. A smaller window means a sharper agent — less noise when it picks a tool — and every request costs less:

Grant scope	Definition cost	Reduction
All 220 tools (no gateway)	46,401 tokens	—
3 granted tools	~633 tokens	−99%
5 granted tools	~1,055 tokens	−98%
10 granted tools	~2,109 tokens	−95%

The risk dividend: 24 of these 220 tools are critical-risk (destructive or financial) and cost 2,291 tokens (5% of the definition load). Block them — the recommended starter policy — and you reclaim that context before tuning anything else.

Create a free account and register FavCRM — nothing to install.
Grant only the tools you use — ungranted definitions never enter the context window.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CUT FAVCRM TOKEN COST →

Instant setup, no code required.

Model your own stack in the token-cost calculator, or see the FavCRM policy for what a sensible grant looks like.

//FAQ

FavCRM token-cost questions.

How many tokens does the FavCRM MCP server use?+

Its 220 tool definitions total 46,401 tokens — 23% of a 200k context window — measured with tiktoken o200k_base over the serialised tools/list payload. Exact counts vary slightly by client and model.

Why does FavCRM consume tokens before I send a message?+

MCP clients load every connected server's tool definitions — name, description, and input schema — into the model's context so it knows what it can call. That payload is charged against your context window on every request, whether or not a tool is used.

How do I reduce FavCRM's token usage?+

Expose fewer tools. A PolicyLayer grant scopes FavCRM to only the tools you allow — ungranted definitions are filtered out of the tool list, so they never enter the context window. A grant of 3 typical tools costs roughly 633 tokens, a 99% reduction.

Does deferred tool loading fix this?+

Partially, in some clients. Claude Code defers MCP tool schemas behind a tool-search step by default, and VS Code has experimental grouping — but you still pay tokens per search and reload, and Cursor, Windsurf and Gemini CLI load definitions upfront. Reducing the exposed tool set cuts the cost in every client.

// METHOD & REVIEW

How these numbers were measured.

01

Serialisation

Each tool is serialised as a tools/list entry — name, description, input schema — from the schemas in the PolicyLayer scan database. Clients differ slightly in framing, so treat counts as close estimates.

02

Tokeniser

tiktoken o200k_base (GPT-4o/o-series). Anthropic's current tokeniser isn't published, so Claude's exact counts will differ; for English text and JSON schemas the totals are close enough to treat these as estimates.

03

Deferred loading

Some clients now defer schema loading (Claude Code's tool search; VS Code experimental grouping). You still pay per search and reload — and Cursor, Windsurf and Gemini CLI load everything upfront.

Computed 23-07-2026 from the PolicyLayer scan database over all 220 catalogued FavCRM tools. Counts refresh with every site build.