mcp · handle support_agent_admin
StudioMeyer-CRM · job 79%hubspot_mcp · job 74%zapier · job 74%apideck_mcp · job 76%cavyro · job 73%agenticbi · job 74%prismmeta · job 73%Squad · job 78%scraperapi_skills · job 74%historis · job 73%superagnt · job 77%ZenSched · job 75%userport · job 75%revenue_control · job 77%Agentlair · job 74%capable · job 73%zoho · job 73%weav_mcp_server · job 79%Nex.Ai · job 75%Dealboard · job 79%salesnexus_mcp · job 76%Rube · job 73%monday · job 73%Noto CRM · job 73%singchat · job 78%dex · job 75%Admin Substitute · job 73%dynamics365 · job 80%iricrm · job 79%Salesforce Cloud MCP Server · job 76%plain · job 78%close · job 76%zendesk · job 76%method_crm_mcp · job 78%vendo_ai · job 80%onepagecrm · job 74%boondmanager_mcp · job 77%Overdrive · job 75%layrcake · job 77%Sales Prep and Follow-up · job 81%SalesOps Agent · job 77%Chief of Staff · job 73%Marketing Ops · job 77%GitHub Linear MCP · job 78%Demo CRM MCP Server · job 73%Percentages are graph-similarity metadata, not suitability scores. A graph edge answers “is it connected” — plan fit and comparable cost are checked below.
Pick the exact reference and alternative series. Each history is separate; gaps stay gaps.
This view calls the same get_evidence tool your agent would — chart, table and MCP response describe the same records. Watch the reference series